c264 en T c40 Global

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

C264/EN T/C40 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 AREVA T&D EAI PRODUCTS 12

C264/EN SA/C40 Safety & Handling
BLANK PAGE
1. INTRODUCTION
This document is a chapter of the MiCOM C264/C264C documentation binder. 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 AREVA T&D Safety Guide: SFTY/4L M/F11
(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 AREVA T&D Energy Automation & Information 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.
AREVA T&D Energy Automation & Information 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 AREVA T&D EAI 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.
AREVA T&D EAI will, at its option, repair or replace software media that do not execute
programming instructions if AREVA T&D EAI receive notice of such defects during the
guaranty period. AREVA T&D EAI 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. AREVA T&D
EAI will pay the shipping costs of returning to the owner parts, which are covered by
warranty.
AREVA T&D EAI 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, AREVA T&D EAI reserves the right to make changes to
subsequent editions of this document without prior notice to holders of this edition. The
reader should consult AREVA T&D EAI if errors are suspected. In no event shall AREVA
T&D EAI be liable for any damages arising out of or related to this document or the
information contained in it.
Expect as specified herein, AREVA T&D EAI 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 AREVA
T&D EAI shall be limited to the amount therefore paid by the customer. AREVA T&D EAI 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 AREVA T&D EAI will apply regardless of the form of action, whether in contract or tort,
including negligence. Any action against AREVA T&D EAI must be brought within one year
after the cause of action accrues. AREVA T&D EAI 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 AREVA T&D EAI 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
AREVA T&D EAI.
8.2 Trademarks
PACiS, PACiS SCE, PACiS ES, PACiS CMT, PACiS SMT, PACiS PS, PACiS SCE, AREVA
T&D EAI, pacis.biz and pacis.com - are trademarks of AREVA T&D EAI. Product and
company names mentioned herein are trademarks or trade names of their respective
companies.
9. WARNINGS REGARDING USE OF AREVA T&D EAI PRODUCTS

AREVA T&D EAI 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 AREVA T&D EAI testing platforms but also a user or
application designer may use AREVA T&D EAI products in combination with other products.
These actions cannot be evaluated or contemplated by AREVA T&D EAI; Thus, the user or
application designer is ultimately responsible for verifying and validating the suitability of
AREVA T&D EAI 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 Lexical (LX) 5
2.1.15 Chapter Applications (AP) 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/C40 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 AREVA T&D Energy
Automation & Information.
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.areva-td.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 guidesare 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 Lexical (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.2 Operation guide
This binder contains the following chapters:
SA, IT, TD, FT, HW, CO, HI, AP, LX.
2.3 Technical guide
This binder contains the following chapters:
SA, IT, TD, FT, HW, CO, IN, ST, CT, CM, RS, MF, LX.
3. INTRODUCTION TO MiCOM APPLICATIONS

AREVA 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, AREVA 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 – RTU, DATA CONCENTRATOR APPLICATION

The figures show some typical cases that can be mixed to face specific constraint. Two
examples can illustrate this case:
• The system application on “figure 1” uses several C264 with several communication
links to SCADA (one per voltage level for example).
• RTU application can use several C264 linked together on SBUS Ethernet. One of the
C264 RTUs is in charge of the concentration of data and of the communication with
the remote SCADA.
BLANK PAGE
Technical Data C264/EN TD/C40
MiCOM C264/C264C
TECHNICAL DATA
CONTENT
1. SCOPE OF THE DOCUMENT 3
2. CONFORMITY 4
3. GENERAL DATA 5
3.1 Design 5
3.2 Installation Position 5
3.3 Degree of Protection 5
3.4 Weight 5
3.5 Dimensions and Connections 5
3.6 Terminals 5
3.7 Creepage Distances and Clearances 6
4. RATINGS 7
4.1 Auxiliary Voltage 7
4.2 Digital inputs 7
4.2.1 DIU200 7
4.2.2 DIU210 8
4.2.3 DIU220 9
4.2.4 CCU200 10
4.2.5 Digital outputs 10
4.2.6 DOU200 10
4.2.7 CCU200 11
4.2.8 BIU241 11
4.3 Analogue inputs 11
4.3.1 AIU201 11
4.3.2 AIU210 12
4.3.3 AIU211 13
4.4 CT/VT inputs 13
4.4.1 TMU200/TMU220 - Currents 13
4.4.2 TMU200/TMU220 Voltages 14
4.4.3 TMU200/TMU220 - A/D converter 14
4.4.4 ECU200/ECU201 14
5. BURDENS 15
5.1 Auxiliary Voltage 15
5.2 Power supply 15
5.3 CPU boards 15
C264/EN TD/C40 Technical Data
5.4 Digital inputs 15

5.4.1 DIU200 15
5.4.2 DIU210 15
5.4.3 DIU220 16
5.4.4 CCU200 16
5.5 Digital outputs 17
5.5.1 DOU200 17
5.5.2 CCU200 17
5.6 Analogue inputs 17
5.7 Ethernet Switches 17
5.8 CT/VT inputs 17
5.9 Front panels 17
6. ACCURACY 18
6.1 Reference Conditions 18
6.2 Measurement Accuracy 18
7. TYPE TESTS 19
7.1 Dielectric Withstand 19
7.2 Mechanical Test 19
7.3 Atmospheric Test 20
7.4 “DC” Auxiliary Supply Test 20
7.5 “AC” Auxiliary Supply Test 21
7.6 EMC 21
1. SCOPE OF THE DOCUMENT

This document is a chapter of MiCOM C264 documentation binders, describing 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
Per DIN VDE 0470 and EN 60255-27:2006 or 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 way
terminal block is mounted (for TMU200 ,TMU210 and TMU220 boards).
3.4 Weight
Case 40 TE: approx. 4 kg
Case 80 TE: approx. 8 kg
3.5 Dimensions and Connections
See dimensional drawings (Hardware description section – C264_EN_HW) and terminal
connection diagrams (C264_EN_CO).
3.6 Terminals
PC Interface:
DIN 41652 connector, type female D-Sub, 9-pin on the front panel.
A direct wired cable is required.
Ethernet LAN (in the rear panel through the CPU260 board):
RJ-45 female connector, 8-pin for the 10/100Base-T self-negotiation.
ST female connector for the 100Base-F.
IRIG-B Input (optional, in the rear panel through the CPU260 board):
BNC plug.
Conventional communication links:
M3 threaded terminal ends, self-centring 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 on the CPU260 board in the rear panel.
Optical fibres trough ECU200 (external RS232/optical converter): optical plastic fibre
connection per IEC 874-2 or DIN 47258 or ST ® glass fibre optic connection (ST ® is a
registered trademark of AT&T Lightguide Cable Connectors).
Inputs /Outputs or power supply modules:
from 0.2 to 2.5 mm² for DIU200, DIU210, DIU220, DOU200, CCU200, AIU201, AIU210,
AIU211 and BIU241 boards.
The I/O boards and BIU241 are equipped with a 24-way 5.08 mm pitch male connector.
Current-measuring and Voltage-measuring inputs:

between 2.5 and 4 mm² for TMU200 Transducerless (4CT+4VT) board.
The TMU200 (4CT+4VT) board is equipped with a “MiCOM: ASSEMBLY CONNECTEUR
BLOCKL GJ104” connector.
3.7 Creepage Distances and Clearances
Per 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
MiCOM C264/C264C computers are available in four auxiliary voltage versions, specified in
the table below:
Version Nominal ranges Operative DC range Operative AC range

A01 24 VDC 19.2 – 28.8 V -
A02 48 to 60 VDC 38.4 – 72 V -
A03 110 to 125 VDC 88 – 150 V -
A04 220 VDC and 230 VAC 176 – 264 V 176 – 264 V
The nominal frequency (Fn) for the AC auxiliary voltage is dual rated at 50/60Hz, the operate
range is 45Hz to 65Hz.
The main characteristics of the BIU241 board are:
• Power supply: 40 W
• Nominal output voltage: + 5V
• Supply monitoring
• Power loss withstands capacity: 50 ms
• Protection against polarity reversal
• Insulation resistance: >100 MΩ ( CM) at 500 VDC
• Dielectric withstand: 2 kV (CM) – 50 Hz for 1minute

4.2 Digital inputs
4.2.1 DIU200
The DIU200 board is available in four nominal voltage versions that characteristics are
specified in the table below.
The DIU200 board has 16 digital inputs.
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 to 60 VDC if V >17.4 VDC Input status is set
if V < 13.5 VDC Input status is reset
A03 110 to 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
The DIU200 board is designed to allow 2 inputs serially connected. This answers to the
following need:
Un
IN1 IN2
C264
0 VDC C0124ENa
If R is open then IN1 and IN2 are set.

If R is closed then IN1 is set, IN2 is reset.
With this scheme, when IN1 is reset, this means that there is a problem into the external
wiring.
The input current at nominal voltage is detailed in chapter 5.4.
There are at maximum 15 DIU boards (including DIU200 and DIU210) inside a C264 rack.
4.2.2 DIU210
The DIU210 board works for all voltages between 48 VDC and 220 VDC (+/- 20%).
Whichever voltage, the triggering threshold is 19VDC
The maximum number of DIU210 board in one C264 rack depends on the rack type and on
the voltage level of inputs.
Please refer to the following table:
Maximum Maximum
DIU210 boards in 40TE racks DIU210 boards in 80TE racks
24V 2 8
48V 6 15
110-125V 3 10
220V 1 5
The DIU210 board is designed to allow 2 inputs serially connected. This answers to the
following need:
Un
IN1 IN2
C264
0 VDC C0124ENa
If R is open then IN1 and IN2 are set.

If R is closed then IN1 is set, IN2 is reset.
With this scheme, when IN1 is reset, this means that there is a problem into the external
wiring.
The input current at nominal voltage is detailed in chapter 5.4.
There are at maximum 15 DIU boards (including DIU200 and DIU210) inside a C264 rack.
4.2.3 DIU220
The DIU210 board works for voltages 48/60 VDC and 110/125 VDC (+/- 20%).
For voltage 48/60 VDC the triggering threshold is from 13.8 VDC to 17.9 VDC
For voltage 110/125 VDC the triggering threshold is from 35.8 VDC to 52.3 VDC
The maximum number of DIU220 board in one C264 rack depends on the rack type and on
the voltage level of inputs.
Please refer to the following table:
Maximum Maximum
DIU220 boards in 40TE racks DIU220 boards in 80TE racks
48/60V 6 15
110/125V 3 10
4.2.4 CCU200
For versions A1 to A4 of the CCU200 board the characteristics of the eight inputs are the
same as the DIU200 board.
For version A7 of the CCU board the characteristics of the eight inputs are:
• nominal voltage ( +/- 20%): 110-125 Vcc with
• triggering threshold: if Vinput > 86 VDC input status is set
• triggering threshold: if Vinput < 67 VDC input status is reset

Maximum number of CCU200 boards to be installed in the C264 racks:
• 15 in the C264 racks (80TE) not equiped with a TMUxxx board
• 14 in the C264 racks(80TE) equiped with a TMUxxx board (CCU is not to be installed
in Slot P)
• 6 in the C264C racks (40TE) not equiped with a TMUxxx board
• 3 in the C264C racks (40TE) equiped with a TMUxxx board (CCU is not to be installed
in slot F)
4.2.5 Digital outputs
4.2.6 DOU200
The characteristics of the Output Relay Contacts of the DOU200 board are specified in the
table below:
Features Values
Nominal operating voltage range 24V to 250 VDC / 230 VAC
Make 2.5A
Carry 2.5A continuous
30 A for 500 ms or 250 A for 30 ms
Break DC: 50 W resistive, 15 W inductive (L/R = 20 ms)
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.
Operating time Break < 7 ms
8 simple pole contacts Normally open
2 double pole contacts 1 Normally open +1 Normally close
• Isolation: 2 kV (CM)– 50 Hz-for 1 min.
• The board is designed and monitored to avoid inadvertent controls.
• There are at maximum 15 DOU200 boards inside a C264 rack.

4.2.7 CCU200
The characteristics of the 4 Output Relay Contacts of the CCU200 board are specified in the
table below:
Each relay of the CCU board has double pole contacts. To get the characteristics described
below, the two output contacts of each relay are to be wired in serial.
Features Values
Nominal operating voltage range 24 to 250 VDC / 230 VAC
Make 5A
Carry 5A continuous
30 A for 500 ms or 250 A for 30 ms
Break DC: 100 W resistive, 30 W inductive (L/R = 40 ms)
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
Operating time Break < 7 ms
Double pole contacts Normally open
• Isolation: 2 kV(CM) – 50 Hz for 1 min.
• The board is designed and monitored to avoid inadvertent controls.
• There are at maximum 15 CCU200 boards inside a C264 rack.

4.2.8 BIU241
The characteristics of the Watchdog Relay Contacts of the BIU241 board are the same as
the contacts “NO+NC” contacts of the DOU200 board.
The characteristics of the two output relays used for C264 redundancy are the same as the
single pole one on the DOU200 board.
4.3 Analogue inputs
4.3.1 AIU201
The AIU201 board provides 4 independent analogue inputs. Each AI can be configured in
voltage or current range individually as specified in the table below:
Type Ranges
Current input range ±1mA
±5 mA
±10 mA
±20 mA
4-20 mA
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)
Type Ranges
Common mode rejection ratio (CMMR) > 100dB
Serial mode rejection ratio (SMMR) > 40dB
gains range (user-selectable) 1, 2, 4, 10
Input impedance for voltage inputs 11 KΩ
Input impedance for current inputs 75 Ω
Temperature derive: up to 30ppm/°C.

The ranges are defined during the configuration phase.
The current/voltage selection is done by choosing the input number of the connector.
There are at maximum 6 AIU boards (including AIU201 and AIU210) inside a C264 rack.
4.3.2 AIU210
The AIU210 board provides 8 analogue inputs (1 common point for two inputs). Each AI can
be configured in the current range as specified in the table below:
Type Ranges
±5 mA
±10 mA
±20 mA
4-20 mA
AD conversion 16 bits (15 bits+sign)

The ranges are configured during the configuration phase.
The current selection is done by choosing the input number of the connector.
A maximum of 6 AIU boards (including AIU201,,AIU210 and AIU211) can be installed inside
a C264 rack.
4.3.3 AIU211
The AIU211 board provides 8 analogue inputs (1 common point for two inputs). Each AI can
be configured in the current range as specified in the table below:
Type Ranges
±5 mA
±10 mA
±20 mA
4-20mA
AD conversion 16 bits (15 bits+sign)

The ranges are configured during the configuration phase.
The current selection is done by choosing the input number of the connector.
A maximum of 6 AIU boards (including AIU201,,AIU210 and AIU211) can be installed inside
a C264 rack.
4.4 CT/VT inputs

The TMU200 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.
4.4.1 TMU200/TMU220 - Currents
There are two available nominal currents with two different allocations on the terminal block.
The four measurement Current Transformers (4 CT) inputs have the following
characteristics:
Operating range
Features
1A 5A
Nominal AC current (IN) 1 Arms 5 Arms
Minimum measurable current with same 0.2 Arms 0.2 Arms
accuracy
Maximum measurable current 4 Arms (4*In) 20 Arms (4*In)
Frequency 50 or 60 Hz ± 10% 50 or 60 Hz ± 10%
CT load rating:
Withstand
Duration
1A 5A
3 second (not measurable, without destruction) 6 Arms (6*In) 30 Arms (6*In)
1 second (not measurable, without destruction) 20 Arms (20*In) 100 Arms (20*In)
4.4.2 TMU200/TMU220 Voltages

The measurement Voltage Transformers ( or 5VT) inputs have the following characteristics:
Features Operating range

Nominal AC voltage (VN) range 57.73 Vrms to 500 Vrms.
Minimum measurable voltage 7 Vrms
Maximum measurable voltage 577 Vrms
Frequency operating range 50 or 60 Hz ± 10%
VT load rating:
Duration Withstand
10 second without destruction 880 Vrms
4.4.3 TMU200/TMU220 - A/D converter

The A/D converter of the TMU200/TMU220 boards has the following characteristics:
Features Values
Width 16 bits
Conversion period < 30 µs
Scanning period 64 samples/period
Linearity error ± 2 LSB
SINAD ratio up to 1kHz 0db
Low passed filter at 1khz -40db/decade
4.4.4 ECU200/ECU201
Dielectric withstands:
Type Test description Type Test Standard Conditions
Insulation Resistance IEC 60255-5 (2000) 100 MΩ at 500 Vdc (CM & DM)
(between groups)
5. BURDENS
5.1 Auxiliary Voltage
The MiCOM C264/C264C computer burdens are specified in the table below:
Version Nominal Maximum

C264C 15W 22W
C264 20W 40W
5.2 Power supply

The BIU241 board burden on the internal 5V bus is 1,25W. This takes into account
watchdog, redundancy relays and communication ports.
The efficiency of the power supply is 78%.
5.3 CPU boards
The CPU260 board (also named CPU type 2 or CPU2) burden on the internal 5V and 12V
bus is 3,3W.
The CPU270 board (also named CPU type 3 or CPU3) burden on the internal 12V bus is
2,7W.
5.4 Digital inputs
5.4.1 DIU200
The DIU200 inputs burdens are specified in the table below:
Version Nominal voltage Current at Un (mA)

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

5.4.2 DIU210
Nominal voltage Current at Un (mA)

24 VDC >25
48 to 60 VDC 3.8
110 to 125 VDC 4
220 VDC 4.1
The DIU210 board burden on the internal 5V bus is 75mW.

Power consumption per input:
Un = 24VDC to 110V DC: 0,5W ± 30% per input
Un > 110VDC: 5mA ± 30%
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. See the
peak current response curve.
WARNING: FOR THE 24V VOLTAGE, THERE IS NO SHORT PEAK CURRENT

BECAUSE OF THE PERMANENT HIGH CONSUMPTION ON INPUTS
>25mA.
The current peak response curve.
35
30
25
Current (mA)
20
15
10
0
0 50 100 150 200 250 300
Tension (V)
C0159ENa
5.4.3 DIU220
Nominal voltage Current at Un (mA)

48 to 60 VDC 5.22
110 to 125 VDC 2.6
The DIU220 board burden on the internal 5V bus is 75mW.

Power consumption per input:
Un = 48/60VDC: 0,66W ± 30% per input
Un = 110/125VDC: 0.62 W ± 30% per input
5.4.4 CCU200
The CCU200 inputs consumption is specified in the table below:
Version Nominal voltage Current at Un (mA)

A01 24 VDC 3.5
A02 48 to 60 VDC 5 for 48 VDC
6.8 for 60 VDC
A03 110 to 125 VDC 2.5 for 110 VDC
3 for 125 VDC
A04 220 VDC 2
A07 110 to 125 VDC 3.4 for 110VDC
5.4 for 132VDC
5.5 Digital outputs

5.5.1 DOU200
The DOU200 board burden on the internal 5V bus is 250mW plus 200mW per activated
relay.
5.5.2 CCU200
The CCU200 board burden on the internal 5V bus is 400mW plus 200mW per activated
relay.
5.6 Analogue inputs
The AIU201 and the AIU210 boards burden on the internal 5V bus is 1 W.
5.7 Ethernet Switches
The SWU20x board burden on the internal 5V bus is 3,85W with 2 optical ports.
The SWR20x board burden on the internal 5V bus is 4 W.
The SWD202/SWD204 board burden on the internal 5V bus is 4W.
5.8 CT/VT inputs
The TMU200/TMU220 burdens on the internal transformers are specified in the table below:
CT burden (at nominal current – IN) Nominal consumption (VA)

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

TMU200 TMU220
Vn = 130 Veff <0.1 < 0.01
The TMU200 board burden on the internal 5V bus is 600mW.

The TMU220 board burden on the internal 5V bus is 300mW.
5.9 Front panels
The GHU200 and GHU210 board burden on the internal 5V bus is 600mW when the LCD
screen is not back-lighted and 3W when the LCD screen is back-lighted.
The GHU201 and GHU211 board burden on the internal 5V bus is 600mW.
The GHU202 and GHU212 board burden on the internal 5V bus is <1mW.
6. ACCURACY
For all specified accuracy, the repeatability is ± 2.5% unless otherwise specified.
If no range is specified for the validity of the accuracy, then the specified accuracy shall be
valid over the full setting range.
6.1 Reference Conditions
Quantity Reference conditions Test tolerance

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

The TMU200 board has the following characteristics:
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 15H
7. TYPE TESTS
7.1 Dielectric Withstand
Type Test Name Type Test Standard Conditions

Insulation Resistance IEC 60255-5 (2000) 100 MΩ at 500 Vdc (CM & DM)
Dielectric Withstand IEC60255-5 (2000) 50 Hz for 1mn, 2kV (CM), 1kV (DM)
IEEE C37.90 (1989)
High Voltage Impulse IEC 60255-5 (2000) 5 kV CM & 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 (Packaging 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 axe H
Acceleration: 1g
Displacement: 3.5mm upon axe 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 / 96h
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 / 96h
Powered On at +70°C
Enclosure Protection IEC 60529 (1989) + A1 Front: IP=52
(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
withstand)
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 up to Vn within 1 minute
From 0 up 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 withstand N/A 2 Vn during 10 ms (for information)
7.6 EMC

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% de H2 à 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)
MiCOM C264/C264C
FUNCTIONAL DESCRIPTION
TABLE OF CONTENTS

1.1 Software features 7
2. MiCOM C264/C264C MANAGEMENT 9

2.1 Operating mode management 9
2.1.1 Definitions 9
2.1.2 Initialisation mode 9
2.1.3 Operational mode 10
2.1.4 Maintenance mode 11
2.1.5 Test mode 11
2.1.6 Faulty mode 12
2.1.7 Halt mode 12
2.2 Database management 13
2.3 Time management 15
2.3.1 External clock 16
2.3.2 Clock message from a SCADA gateway 17
2.3.3 System master clock 17
2.3.4 Time set by an operator 17
2.3.5 Local clock update 18
2.4 SNTP server 19
2.5 Redundancy Management 20
3. COMMUNICATIONS 22
3.1 Telecontrol bus 22
3.2 Legacy bus 23
3.3 Station bus 23
3.3.1 Exchanges 24
3.3.2 Supported Common Data Classes 24
3.3.3 Controls 24
4. DIRECT PROCESS ACCESS 25

4.1 Input check 25
4.2 Output check 25
4.3 Time tagging 25
4.4 Digital input acquisition (DI) 25
4.4.1 Acquisition 25
4.4.2 Debouncing and filtering 26
4.4.3 Toggling 26
C264/EN FT/C40 Functional Description
4.5 Counters acquisition (CT) 27

4.5.1 Single counter (SCT) 27
4.5.2 Double counter (DCT) 27
4.6 Digital measurement (DM) 28
4.6.1 Acquisition without Read Inhibit signal 28
4.6.2 Acquisition with Read Inhibit signal 29
4.6.3 Encoding 30
4.7 Analogue input acquisition (AI) 31
4.7.1 Input ranges 31
4.7.2 Acquisition cycle 31
4.8 Digital outputs (DO) 31
4.9 Digital Setpoints 31
4.9.1 Encoding 32
4.9.2 Read Inhibit 32
5. DATA PROCESSING 33
5.1 Binary Input processing 33
5.1.1 Binary Input definition 33
5.1.2 Processing of Single Point Status 34
5.1.3 Processing of Double Point Status 36
5.1.4 Processing of Multiple Point Status 40
5.1.5 System Inputs 41
5.1.6 IED inputs 42
5.1.7 Group processing 42
5.1.8 SBMC Mode Processing 43
5.1.9 BI sent to automatism features 43
5.2 Measurement Input Processing 44
5.2.1 Open circuit management 44
5.2.2 Scaling 44
5.2.3 Zero value suppression 45
5.2.4 Thresholds detection 45
5.2.5 Manual suppression 46
5.2.6 Substitution 46
5.2.7 Forcing an invalid measurement 46
5.2.8 Measurement resulting states 46
5.2.9 Transmission 47
5.2.10 CT/VT additional processing 48
5.2.11 Digital Measurement Processing 52
5.3 Tap Position Indication processing 53
5.3.1 Acquisition from Digital Inputs 53
5.3.2 Acquisition from Analogue Inputs 53
5.3.3 Manual suppression 53
5.3.4 Substitution 53
5.3.5 Forcing an invalid TPI 53
5.3.6 TPI resulting states 54
5.3.7 Transmission 54
5.4 Accumulator Input Processing 54
5.5 Energy counting 55
5.6 Basic Data Manipulation 56
5.6.1 Test Mode enhancements 56
5.6.2 Device order running 56
5.6.3 Controls management from PSL 56
6. CONTROL SEQUENCES 58
6.1 Generic description 58
6.1.1 Generalities 58
6.1.2 Control sequence phase management 59
6.1.3 Direct Execution mode 62
6.1.4 SBO once mode 63
6.1.5 SBO many mode 66
6.1.6 Generic selection checks 68
6.1.7 Selection behaviour 72
6.1.8 Generic execution checks 73
6.1.9 Execution behaviour 73
6.1.10 Controls time sequencing 74
6.2 Control of non synchronised breakers 77
6.2.1 Non synchronised circuit breakers features 77
6.2.2 Control sequence of non-synchronised circuit breakers 77
6.3 Control of synchronised breakers 78
6.3.1 Circuit breakers features 78
6.3.2 Circuit breakers with external synchrocheck 79
6.3.3 Circuit breakers with internal synchrocheck 84
6.4 Control of disconnectors 88
6.4.1 Disconnectors features 88
6.4.2 Control sequence of disconnectors 88
6.5 Control of transformers 89
6.5.1 Transformers features 89
6.5.2 Control sequence of transformers 89
6.6 Control of ancillary devices 92
6.7 Control of Intelligent Electrical Devices (IED) 93
6.7.1 Control to IEDs 93
6.7.2 IED controls 93
6.7.3 Digital setting point (SP) 93
6.8 System controls 93
6.9 Kind of control sequence 94

6.10 Control sequences checks 94
6.10.1 Mode Management 94
6.10.2 IED connected 94
6.10.3 Control mode 94
6.10.4 Uniqueness of control 95
6.10.5 Inter-control delay 95
6.10.6 Status of the device 95
6.10.7 Lock device 95
6.10.8 Running Automation 95
6.10.9 Interlocking 95
6.11 HV Control Sequences 95
6.11.1 Circuit breaker 95
6.11.2 Disconnector 95
6.11.3 Transformer 95
6.12 Fast Load Shedding ( FLS ) 96
7. AUTOMATIONS 97
7.1 Built-in Automation functions 97
7.1.1 Synchrocheck 97
7.1.2 Auto-Recloser (AR) 99
7.1.3 Trip Circuit Supervision 105
7.1.4 Automatic Voltage Regulation (AVR) 107
7.2 Interlocking: logical equations 121
7.2.1 Inputs 121
7.2.2 Outputs 121
7.2.3 Control 121
7.2.4 Behaviour 122
7.2.5 Limits and performance 124
7.3 Slow automation: Programmable Logic Control (PLC) 125
7.3.1 Inputs 126
7.3.2 Outputs 126
7.3.3 Control 126
7.3.4 Behaviour 127
7.3.5 Limits and performances 127
7.4 Fast automation: Programmable Scheme Logic (PSL) 128
8. USER INTERFACE 129
9. RECORDS 130
9.1 Permanent records storage 130
9.1.1 Data storage 130
9.1.2 Waveform Recording 130
9.1.3 Events 132

9.2 Non-permanent data storage 132
9.2.1 Alarms 132
BLANK PAGE

This document is a chapter of MiCOM C264/C264C documentation binders. It is the
functional description of this computer. The hardware description is defined in HW chapter
and all connection diagrams in CO chapter. The technical data of the computer (capabilities,
performances, environmental limits) are grouped in TD chapter.
1.1 Software features

The MiCOM C264/C264C computer belongs to the new range of modular product at
hardware, software and functional levels. All functionalities are fully configurable following
customer needs and requirements. MiCOM C264/C264C computers assume:
• Direct process interface through Digital Inputs (DI), Digital Outputs (DO), Analogue
Inputs (AI), and CT/VT boards
• Direct operator interface
• Embedded parameterised control of all common plant or device
• High communication abilities to IED, Ethernet, and RTU
• User configurable automation modules
• Events, alarms, measurement display, printing and archiving
• Enhanced inner management with databases handling, self-test controls and

synchronisation means
RTU, SCADA PACiS system, IEC 61850 IEDs
T-BUS S-BUS
Telecontrol
Interface IEC 61850
Synchronsation
Time tagging
Computer Kernel
RTC
SOE Printing
Alarms
Archives Human
CT, Disturb Interface
(LCD)
Embedded Automation
(basic+AR, Synchrocheck+AVR)
Configurable Automation
(Fast PSL / Sequential PLC)
Legacy Gateway I/O boards
L-Bus
DI DO AI CT/VT
IED
C0003ENb
FIGURE 1: SOFTWARE FEATURES

The components of the software management are:
• Inputs/Outputs board (DI, DO, AI)
• Analogue Inputs (AI, from CT/VT board - optional)
• Automatic functions (Built-in, PLC, PSL)
• Communications with Telecontrol Bus, Station Bus and Legacy Bus (see chapter
Communication)
• RTC (Real Time Clock), time management; synchronisation, time tagging (see Time
management chapter)
• Communication with peripherals such as:
− Local Operator Interface (LCD, front panel)

− Local Printer (local sequence of events - SOE)
2. MiCOM C264/C264C MANAGEMENT
2.1 Operating mode management
2.1.1 Definitions
The terms defined below are used in this whole section 2.
• Anomaly: an anomaly is a fault causing a downgraded behaviour of the computer.

There are hardware and/or software anomalies:
− Board failure
− Loss of synchronisation
− Loss of communication
• Software fault: A software fault results of a major software error. In this case the
computers enters the Faulty mode.
• Vital hardware fault: a vital hardware fault is a fault causing a software halt. This kind
of fault causes the computer to stop the application software.
− CPU fault
− Power supply fault
− Bus fault
− Permanent Interruption fault
2.1.2 Initialisation mode

After power on or manual reset the computer enters the initialisation mode and performs
different types of checks:
• Vital hardware tests

Non-volatile memory test: in case of a problem the computer tries to repair this non-volatile
memory. If a vital hardware test fails, the initialisation is stopped and the computer enters the
Halt mode.
• Non vital hardware tests

Non-vital hardware tests are only performed on present boards:
− Inputs and outputs boards:
⇒ To determinate the number and the type of the present input and output
boards
⇒ To check the presence of the previously input and output boards and to be
informed if a board is absent
⇒ To check the good working order of the present input and output boards and
to be informed if a board is out of order
− Communication boards: this test is performed within the communication protocol.
− Display (LCD, LED’s): the single test that can be done is the presence of the HMI
board.
− Peripheral devices (printer, external clock ..). Check of the presence of the devices
by use of timeouts.
If any of these non-vital hardware tests fails the computer enters the
operational/downgraded mode depending on the type of the fault.
• Software tests (database coherency tests)

These tests are performed at each restart of the computer. The checks of the database
guarantees that the database is compatible with the hardware and the software of the
computer and that it does not contain incoherent data of configuration. The following checks
are performed:
• Check of the presence of a database
• Check of the DB/ software compatibility

This control makes it possible to check that the software and the database are
coherent. The computer contains in its static data a version and a revision number
indicating which structure of database it is able to interpret. The database must have
the same version to be accepted.
• Check of the DB/ equipment compatibility

This control makes it possible to check that the database is intended for the
equipment on which it was downloaded. To check it, the type and the number of
equipment contained in the heading of the database are compared with the type and
the number of equipment contained in the static data of the software.
• Check of the validity of the data of the database

This control checks that the configured inputs and outputs are present and that the
number of objects (bays, digital inputs …) remains within acceptable limits.
If any of these checks fails, the computer enters the Maintenance mode.
The initialisation of the computer does not exceed one minute.
2.1.3 Operational mode

This mode can be divided into 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 watchdog relay
is activated and all the functionalities of the computer are available. Nevertheless, detection
of an error can lead to the Downgraded mode, to the Faulty mode or to the Halt mode,
depending on the nature and the gravity of the failure.
From this mode a transition to the Maintenance mode can be requested by an operator from
local HMI or upper level (maintenance request).
From this mode a transition to the Test mode can be requested by an operator from local
HMI or upper level (simulation request).
In this mode, the operations that can be done on databases are the following:
• Download a standby database
• Swap the databases: then the computer automatically restarts
• Modify a database
• Display database information

This mode is transmitted to local HMI and upper level (RCP).
2.1.3.2 Downgraded mode

This mode is entered in case of an anomaly. In this mode the general working of the
computer is not very disturbed because it involves the degradation of only few functions. The
watchdog relay is activated.
The downgraded mode depends on the hardware configuration of the computer. But we can
define the different kinds of downgraded modes that can happen:
• 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 previous items

When the cause(s) of the transition into Downgraded mode disappear(s), the computer
returns to the Normal mode.
2.1.4 Maintenance mode

In Maintenance mode, communication on the station bus is operational in order to manage
the database. This mode is displayed on local HMI (led and LCD) and on upper level.
The watchdog relay is de-activated.
In this mode the operator can manage the database:
• Download a database
• Swap the databases
• Modify a database
• Display database information

From this mode a transition to the operational mode can be requested by an operator from
local HMI or upper level (active request).
2.1.5 Test mode

In Test mode, the computer works normally but output relays are not activated. This mode is
entered on operator request in order to simulate the functioning of distributed automatisms
such as interlocking. Instead of activating the output relays, the computer sends a “test OK”
message to the SCP if the command is valid otherwise a “test NOK” message.
NOTE: to realise the tests, the operator has to manually create the testing
conditions by forcing BI or Measurements on different computers.
Once the conditions are realised, he can generate a command and
see at the SCP level (HMI) if the result corresponds to the expected
one.
This mode is displayed on local HMI (led and LCD) and on upper level.
From this mode a transition to the operational mode can be requested by an operator from
local HMI or upper level (end of simulation).
2.1.6 Faulty mode

The Faulty mode is entered when a fault, that prevents the exploitation, happens. This mode
can be entered from any mode described above.
This mode is also entered when a failure is detected on DO boards and if the configuration
allows this mode on DO faults.
The only way to leave this mode is an automatic reset or a transition to the Halt mode. Each
time the computer enters this mode, an internal counter is incremented. As long as the value
of this counter is lower than Max_Fault (parameter defined during the configuration step) the
Initialisation mode is entered. The value of this counter is automatically reset when the
lasted time since the last incrementation of the counter reaches the value
Fault_Detection_Lasting (parameter defined during the configuration step). When the value
of this counter reaches Max_Fault the computer enters the Halt mode.
2.1.7 Halt mode

In this mode the computer doesn’t operate anymore. The watchdog relay and all the outputs
relays are deactivated. The only way to get out of this mode is to operate a manual reset.
The following figure summarises the different operating modes of the computer and the
transitions.
DB/software compatibility not OK

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

end of simulation active request
vital
vital hardware
hardware vital hardware fault fault
fault
vital hardware fault
HALT
Counter of faults = Max_Fault
C0307ENa
FIGURE 2: OPERATING MODES OF THE COMPUTER

2.2 Database management

The MiCOM C264/C264C uses structured databases for data management. A database
(DB) is a file which contains the description of the whole of the electric process, as of the
whole of the equipment which the computer is likely to dialogue with (IED, HMI ,etc.). It
contains also some parameter settings of the software and of the transmission. Databases
are generated and versioned by an independent equipment: the System Configuration Editor
(SCE). Each database file has an associated Vdbs (System Baseline Version) A database is
downloaded into the non-volatile memory of the computer via the IEC61850 station bus with
the System Management Tool (SMT) or directly over Ethernet with the Computer
Maintenance Tool (CMT).
The computer stores at any moment up to two DBs in its non-volatile memory. The two DBs
(and these associated Vdbs) are called thereafter DB1 and DB2 (and these associated Vdbs1
and Vdbs2).
Each database (DB1 and DB2) of the computer can take one of the following states:
• Missing: the DB is not present in non-volatile memory of the computer;
• Standby: the DB was downloaded in non volatile memory of the computer; however,
this version is not taken into account by the software;
• Current: the downloaded DB is taken into account by the software;
• Current Modified: the DB, currently taken into account by the software, underwent a
parameter setting;
• Standby Modified: the DB underwent a parameter setting, but it is not taken any
more into account by the software.
The following diagram represents the life cycle of the databases in the computer:
Absent
Downloading
Switching
Standby Current
Parameter setting
Parameter setting
Standby Current
Modified Modified
Switching
C0308ENa
FIGURE 3: THE DIFFERENT STATUS OF A DATABASE

At any moment, there is only one Current or Current Modified database. In the same way,
there is only one Standby or Standby Modified database.
A file descriptor (DB context) stored in non-volatile memory contains the configuration of the
DB present on the equipment. This file, containing the state of each of the two databases
(DB1 and DB2) and the Vdbs (Vdbs1 and Vdbs2) of each one, makes it possible to know the
configuration of the databases at the moment of the boot, and to start again with the current
database (if it exists). DB Context is updated by the sub-functions "Download a database",
"Switch the databases", "Check a database", "Modify a Database".
• To download a database ( via Ethernet)

The downloading of a database is usually performed with SMT tool via the station bus.
The first downloading of a database (and its associated Vdbs) can be performed only
when the computer is in maintenance mode.
The downloading of a standby database (and its associated Vdbs) can be performed
when the computer, running with the current database, is either in operational mode or
in maintenance mode.
The sequencing is:
− To work out and transmit to the calling equipment a response to the request: the
request can be refused if another request on database is already in progress;
− To carry out the transfer of the DB file (and associated Vdbs) and to check its
integrity (calculation of checksum and control of the database);
− In case of fault, to announce to the calling equipment the failure of the transfer;
− In case of successful transfer, to control the database compatibility;
− In case of invalid DB, to announce to the calling equipment the failure of the
installation;
− In case of valid DB, to assign to the downloaded database (and associated Vdbs)
the state standby by removing a possible standby database (and associated
Vdbs) present in the computer; to signal to the calling equipment the success of
the installation;
− To update the file descriptor (Context database) in non-volatile memory.
• To switch the databases

This function answers to a request of DB switching coming from the station bus. This
request specifies the Version of the standby DB (Vdbs) to become current. After
a DB switch the computer automatically reboots and goes into active Mode if the DB is
coherent with the software.
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 4: DATABASES SWITCHING

• To check the database
This function is carried out at each reboot. (refer to 3.2.1 Initialisation mode)
• To modify the database

The parameter setting of database consists in modifying some values of configuration
present in the database. A parameter setting can be carried out only on the current
database (Current or Current Modified). Following a parameter setting, file database is
modified: the new value taken by the data is memorised there. The index of parameter
setting of the database is incremented, and the checksum of the file is recomputed.
The database then takes the Current Modified state. Only certain data are settable.
This is performed from the local HMI.
− To carry out a parameter setting of data

This function treats the requests of parameter setting:
⇒ To check the coherence of the request: known object (the object is really
present in the database), settable data, value of parameter setting compatible
with the type of data conveyed (value belonging to the range of acceptable
variation),
⇒ If the request is incoherent, to emit a negative report to the emitter of the

request,
⇒ To write in database file the current value of the data,
⇒ To write in database file the date of modification of the data,
⇒ To compute the checksum and to write it in data base file,
⇒ To assign the state Current Modified to it,
⇒ To emit a positive report with the emitting equipment of the request,
⇒ To update the file descriptor (Context database) in non-volatile memory.
• To consult a settable data

This function treats the requests of consultation of parameter issued from the Operator
Station:
− To check the coherence of the request: known object (the object is quite present in
the database), settable data and current DB
− If the request is incoherent, to emit a negative response to the transmitter of the

request
− To work out the response to the transmitter of the request by giving the current
value of the data
For C264 in standalone applications, C264 offers possibility to store locally (in flash memory)
the database source, in the limit of 20 MB database source size.
In this case, the upload of the source database is done with the CMT Tool (Computer
Maintenance Tool).
2.3 Time management

The main purposes of the time management are:
• Synchronisation of the computer by:
− The external clock
− Station/legacy bus
− Operator
• Updating of the internal clock
• Synchronisation of other equipments via station bus
Time synchronisation of a computer can be done by four means:

• External clock (IRIG-B signal
• Clock message from a SCADA gateway (T-Bus)
• Clock message from the system master clock (S-Bus)
• Time set by an operator
Concerning these four external time references, there is a priority rule: if the external clock is
operating, modifications on the computer clock are not possible by other ways (for example
from SCADA gateway, system master clock or operator). In case of external clock is
disconnected or not operating, there is a priority order: clock message from a SCADA
gateway or from the system master clock takes priority over operator.
When the computer is master of legacy bus, it synchronises the IED according to the
synchronisation procedure of the protocol. The synchronisation is done just after the
computer has been synchronised by external clock or station bus or RCP. If the computer is
not synchronised, it synchronises periodically the IED all the same.
When the computer is synchronised all events and measurements have a time tag with
synchronised attribute. If synchronisation is lost, or has never been received attributes
indicates that time tag is not synchronised.
The time management organisation is based on the following scheme:
Synchronisation signal
External clock SCADA
Which Which synchronises

synchronises through SCADA bus
SystemMaster
Clock
Which synchronises Operator

through station bus time setting
IEC
equipment
Which synchronises
through legacy bus
IEDs
C0004ENc
FIGURE 5: TIME MANAGEMENT
2.3.1 External clock

A computer gets functionality of system master clock: it is the architecture equipment which
receives periodically, from an external IRIG-B clock reference, messages containing the date
and the hour.
The external clock device receives the synchronisation signal through several possible
protocols (GPS, DCF77, etc…) and then sends it periodically to the dedicated IRIG-B input
of the MiCOM C264/C264C.
The external clock transmits to the computer the hour and date that itself receives.
In case of loss of the radio signal by the external clock two cases have to be considered:
1. Some external clocks can synchronise the computer for 8 hours after loss of radio
signal because they have an oscillator with a very good accuracy. The external clock
indicates via the protocol two informations: “no radio received” and “loss radio
signal since more 8 hours”. The computer remains synchronised until the indicator
"loss radio signal since more 8 hours" is activated. Then the status of internal clock
becomes “not-synchronised”.
2. Some external clocks haven't internal accuracy circuit to back up the radio signal. In
this case, the status of internal clock of computer becomes “not-synchronised” after
confirmation of “loss radio signal” (few minutes).
If the computer is master clock for the other equipment of the substation then it sends the
synchronisation message to the other equipment even if it is not synchronised. In this same,
it stays synchronised even if it loses the external clock communication. A dedicated binary
input is associated to the external clock status.
2.3.2 Clock message from a SCADA gateway

SCADA clock acquisition is a SCADA gateway specification. The purpose of this part is to
detail acquisition of clock message from SCADA gateway.
SCADA clock synchronisation depends on the protocol. The synchronisation message is
directly acquired by the MiCOM C264/C264C through the SCADA link.
The clock message from SCADA gateway is in UTC time.
The SCADA clock is transmitted to the “local clock update” function. This clock is
transmitted after acquired frame from the SCADA gateway has been checked and its control
fields removed.
When the acquisition of clock message from SCADA gateway is operating (depending on the
priority), the computer receives a clock synchronisation message from the SCADA. An
interruption is related to the frame arrival and clock message from SCADA gateway can be
acquired. The delay transmission from SCADA gateway is compensated.
Whatever the protocol, clock message from SCADA gateway must contain:
Day / month / year / hour / minutes / seconds / milliseconds
The update of computer internal clock upon the clock message from SCADA gateway is
managed as specified in “local clock update” function.
2.3.3 System master clock
On an IEC61850 network, time synchronisation is based on SNTP ( Simple Network Time
Protocol). In a PACiS system up to two computers can be defined as System Master Clock
and so are SNTP servers. All others IEC61850 equipment are SNTP clients. In case of
failure of one SNTP server ( computer lost) or external clock failure, the SNTP clients will
automatically reconnect to the second server.
2.3.4 Time set by an operator
The user may set time and date directly using the MiCOM C264/C264C local Operator
Interface or the Computer Maintenance Tool (CMT)
If the computer does not receive synchronisation messages from external clock, from
SCADA gateway or from system master clock, an operator is allowed to set its time
manually.
In case of external time reference is operating (external clock, SCADA clock or system
master clock), the time set by an operator is not possible.
Time set by an operator is allowed and activated only if external clock, SCADA gateway and
System Master clock are faulty.
Normally, only the system master clock should be manually time set by an operator. The
device used by the operator to perform this operation depends on which equipment is the
system master clock. Any other equipment in a PACiS system architecture can not be time
set by an operator while it is synchronised by the system master clock. However, it can be
time set if the system master clock can not synchronise it anymore (system master clock
faulty or connection lost).
Then, the computer is time set via the HMI in front panel or by maintenance laptop computer
(CMT). Functionally, time is set by operator thanks to both modifying commands: one for the
date and one for the hour (in practice, another command could be reserved to check the
date and the hour values). Therefore, operator might have two menus available: one menu
to change the date (year/month/day) and another to change the time
(hour/minutes/seconds).
When operator sets time, the internal clock of the computer is suggested to the operator at
the display.
Furthermore, a manual time set indication must be raised and the operator action is logged.
2.3.5 Local clock update
Each computer has its internal clock (local clock) with its own drift. Therefore, this internal
clock must be updated according to external time reference.
So, the purpose of this specification is then to describe the local clock update method from
external time reference.
As this function is based on the acquisition of external time reference, it is the one which
deals with the loss of external time reference clock and manages the synchronisation status
of the computer.
Time information, it includes:
• Loss of external clock, SCADA gateway clock message or system master clock.
• Indication that time has been roughly updated. Consequently, this indication allows
detecting any difference between internal and received clock greater than the fixed
value (∆threshold = 20 millisecond). This time discrepancy is signaled: printed and archived
event.
• Indication that time was set by an operator. This “manual time set” indication is
required in order to time-tag events occurring.
The internal time format is GMT. The time difference between GMT and local time is a
parameter set at configuration time.
Internal clock of the computer deals automatically with all dates including leap years up to
2037. Computer clock deals also automatically with seasonal time changes by using
indications given in the DST information in TZTAB file. If DST rules change computer can be
set with new rules.
The computer manages milliseconds itself with its quartz.
At initialisation, the synchronisation upon external clock is declared not-synchronised. This
status remains the same till a control has been made upon driver initialisation which role is to
receive external synchronisation frames. 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.
Once synchronisation upon external clock validated, the synchronisation upon external clock
could come back in invalidity: the computer has not received external synchronisation
message for N minute(s) (external clock failure). The value of this timing is 300 seconds. The
internal clock keeps the frequency it had before the external clock failure.
In case of external clock failure (disconnection or message contains invalid data), an internal
signaling or an alarm must be activated by internal generation and the system master clock
is declared invalid. In this case, the events must be marked by a non-synchronisation
indication as long as the default is present.
When a station bus equipment has not received synchronisation messages for 180 seconds
it raises an alarm. Events processed by this equipment are time tagged with a local fault
indication and stops the IEDs synchronisation.
So, this function manages the synchronisation status of the computer as following:
• 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.
2.3.5.1 Management of loss of external time reference
As the local clock update function receives external time reference, it manages the loss of
external time reference.
So:
• if external clock is lost then local clock update points out loss of external clock
• if clock message from SCADA gateway is lost then local clock update points out loss
of SCADA gateway clock message
• if system master clock is lost then local clock update points out loss of system master
clock
2.3.5.2 Update method
When the external clock acquisition is validated, the synchronisation of internal system
master clock on the external time reference is managed as following:
If a difference between the internal clock value and the external time reference value
transmitted exists, |Cinternal – Cexternal| ≠ 0:
If |Cinternal – Cexternal| < 1 ms, the internal clock is not modified
If |Cinternal – Cexternal| > 1ms, two different cases are processed:
1. if |Cinternal – Cexternal| ≤ ∆threshold (20 ms), the value of internal clock is progressively corrected
(reduced or increased). This compensation is performed in a set time (t1=60 s).
2. if |Cinternal – Cexternal| ≥ ∆threshold (20 ms), the internal hour is updated roughly.
In case of external clock is received from time setting by an operator, local clock must be
directly updated roughly.
2.3.5.3 Limits an performances

The quartz drift (i.e. deviation of the internal oscillator of the computer) is lower than 0,5
s/day (i.e. ≤ 5,8 µs/s). This quartz drift is assured on all the operating temperature range.
2.4 SNTP server
The SCE allows to configure a third-party SNTP server, which could be redundant, i.e. 2 IP
addresses are defined. These IP addresses must be in the same address range than the
C264 of the Ethernet network.
In this case, no C264 will be Master Clock: all C264 are SNTP clients.
The synchronization performance of the system depends on the third-party SNTP server
accuracy.
Redondancy for SNTP server is possible with a second C264-SNTP server.
2.5 Redundancy Management

Equipment redundancy is managed using two identical computers with same hardware and
database.
The two redundant computers are the main computer and backup computer. The computer
that performs the bay(s) management is the active computer; the other one is the standby
computer. So, a redundant computer can be main/active, main/standby, backup/active
and backup/standby. During the boot time, the main computer will be the active one (if
both computers are fully operational).
The two computers perform simultaneously the same functions (inputs acquisition and
processing, archiving, automation), but at a given time, only the active computer sends
controls to the electrical process or on the Station Bus. A PACiS IEC-61850 client
receives information from the two computers: so, a dedicated mechanism allows to process
only information received from the active computer. Only the active computer manages
communication with IED or SCADA.
This switchover from the active to the standby (and vice-versa) is performed automatically
according to following features.
Station Bus
MAIN BACKUP
COMPUTER COMPUTER
DI2 DO2 DI1 DO1 DI1 DO1 DI2 DO2
Active State Control/Indication
IEC 61850 client state Control/Indication

C0125ENb
FIGURE 6: REDUNDANCY MANAGEMENT

The two computers exchange information using:
• The Station Bus, to give their internal status (IS)
• 2 couples 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 case 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 is the one with 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 is described in the table below.
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 computer, marked in configuration, 30 seconds for the Backup one).
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 / /
launching ≠ go to state 4 ≠ go to state 4
≠ go to state 1
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
3. COMMUNICATIONS
MiCOM C264/C264C computer ensures up to three different types of communications:
• Telecontrol Bus (T-Bus),
• Station Bus (S-Bus),
• Legacy Bus (L-Bus).

Main characteristics are given below.
RTU, SCADA PACiS system, IEC 61850 IEDs
T-BUS S-BUS
Telecontrol
Interface IEC 61850
Computer Kernel
Legacy Gateway I/O boards
L-Bus
IED
C0005ENc
FIGURE 7: COMMUNICATIONS
3.1 Telecontrol bus
The available slave protocols are:
• IEC 60870-5-101 (T101)
• IEC 60870-5-104 (T104)
• DNP3.0
• DNP3 over IP
• MODBUS
MiCOM C264/C264C computer behaves as a slave into master/slave protocol (DNP3.0,
T101, DNP3 over IP, MODBUS) or balanced protocol (T101, T104).
The connection with SCADA is direct or via modem.
Physical layer:
• T101, DNP3.0, MODBUS: RS232, RS485
• T104, DNP3 over IP: Ethernet 10 or 100 Mb/s: RJ45 connector or optical fibre
(multimode or monomode)
Up to two protocols can be configured, same protocol or not, with or without redundant
channels. The C264 computers have up to four serial ports. Be careful, for the CPU, the
baudrate must be the same on both serial ports.
The redundancy is not available for T104, DNP3 over IP and MODBUS.
3.2 Legacy bus

MiCOM C264/C264C computer behaves as a master.
Protocols:
• IEC 60870-5-103 (T103)
• IEC 60870-5-101 (T101)
• ModBus
• DNP3
Devices connected to: IEDs
Physical layer:
• RS232, RS485
• Optical fibre
Four serial ports are available to make four networks with different protocols or not.
For T103 and Modbus, a tunnelling mode is available. This allows a setting software running
on a personal computer to access the IEDs through the MiCOM C264/C264C.
3.3 Station bus
The S-BUS Protocol is used for PACiS subsystems communication but it is also available for
other equipment.
A MiCOM C264/C264C computer behaves mainly as a server but it can be also a client of
other MiCOM C264/C264C computers (distributed automations) or IEC 61850 IED.
Protocol:
• IEC 61850
Devices connected to:
• PACiS devices (OI, SMT, PACiS Gateway)
• Other MiCOM C264/C264C computers
• IEC 61850 IEDs

Link layer: Ethernet 10 or 100 Mb/s
Physical support:
• Copper twisted pair (RJ45 connector)
• Optical fibber (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
MiCOM C264/C264C computer acquires and sends data on IEC-61850 network using two
mechanisms:
• REPORT
• GOOSE
The REPORT is specific between a server and one client, it provides:
• data value
• data state or quality attribute (validity and several kind of invalid state)
• time tag of last data value change
• time tag quality attribute (server synchronised or not when event has occured)
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
MiCOM C264/C264C 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)
Measurand 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)
TABLEAU 1: DATA MANAGEMENT

3.3.3 Controls
MiCOM C264/C264C supports Common Data Classes control expressed with SPC, DPC,
INC and APC configured as Direct Execute or SBO.
4. DIRECT PROCESS ACCESS

Several kinds of boards can be used in MiCOM C264/C264C. Digital Input & Outputs,
Measurement acquisitions are checked to validate information/action and time tagged on any
change of state or value.
The MiCOM C264/C264C computer acquires digital and analogue inputs, counters, digital
measurements, and analogue measurements from CT/VT. 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/C264C 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-20mA with current value under 4mA)
• Undefined (Digital Measurement or Counter with invalid DI coding)
4.2 Output check

Output boards are periodically checked at their logical level. In the event of a logical circuit
test fails 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 with a 1ms accuracy. All internal logic data are time
stamped with a 1ms accuracy.
Analogue 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 is time tagged by IED itself if it has this facility otherwise it is
performed at computer level when receiving the data.
4.4 Digital input acquisition (DI)
4.4.1 Acquisition
Acquisition of binary information is done via DIU200/DIU210 (16 DIs) or CCU200 (8 DIs + 4
DOs) boards:
Digital Input (DI) can take one among two values: 1 or 0. The value 1 is associated with the
presence of an external voltage; the value 0 is associated with the absence of the voltage.
The values, 1 or 0 are written by the hardware when the external voltage is above (or below
a threshold). The value of the threshold is given in the hardware specification document.
A transition from 0 to 1 or 1 to 0 is generally followed by a succession of transitions
(bounces) before the value stabilises. It is necessary that the software filters 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 8: DIGITAL INPUT PROCESSING
4.4.2 Debouncing and filtering

A filtering is applied on digital inputs as follow:
Filtering time
Debouncing
time
t0 t1 t2
C0127ENa
FIGURE 9: 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 has remained stable from t1 to 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 couple of delays (debouncing / filtering) are defined:
• one for all DI which will be used as BI
• one for all DI which will be used as DM
• one for all DI which 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 C264/C264C 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);
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.
4.5.1 Single counter (SCT)
A 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 5ms: the chosen
value must be coherent with the pulse frequency (i.e. 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 10: 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 complementary states for transitions to be
detected and validated. The counter is invalid if there exists a non-complementarity between
the 2 contacts during a delay Tdef. This delay is defined for the whole system (i.e. 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 11: 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. The maximum number of digital inputs can be used for a digital
measurement is 64.
DM are used to process measurements and tap position indications.
A DM can be associated to a Read Inhibit (RI) signal. The acquisition process is different
depending on the presence of this RI signal.
4.6.1 Acquisition without Read Inhibit signal
The DM is calculated at each change of state of one of its inputs.
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 12: 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 13: 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 14: 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 4999
(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
One supplementary bit can be used 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 to 64 0 to 2
to 0 to 64
4.7 Analogue input acquisition (AI)

Acquisition of AC voltages and currents coming from the electrical network is done via
TMU200 (4CT + 4 VT) board.
Acquisition of DC voltages or currents signals is done via AIU201 (4 AIs) or AIU210 (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).
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 into MiCOM C264/C264C:
• 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

Digital setpoints are digital values coded on multiple outputs. Each output represents a bit of
the value. Digital setpoints are used to send instruction values to the process or to auxiliary
devices. The maximum number of outputs that can be used for a digital setpoint is 48.
Digital Setpoints are processed on the same boards as the Digital Outputs. The Digital
Outputs characteristics described above apply on Digital Setpoints. Nevertheless, only
standard DO boards with single pole N/O relays can be used.
4.9.1 Encoding
The following codes 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
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,
1 among 10 for the units)
32 0 to 4999
(1 bit among 4 for the thousands,
48 0 to 299,999
(bit among 2 for the tens 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
Moreover a supplementary bit can be used for the sign ( 0 indicates a positive value, 1
indicates a negative value).
4.9.2 Read Inhibit
A dedicated binary output can be used to allow or forbid the reading of the value by the
external device.
There is one (or none) Read Inhibit (RI) output per value.
If the RI output is a logical one (external polarity applied), the reading is allowed.
The procedure used to output a value with a RI output is:
• Reset the RI output to a logical 0: read forbidden.
• Wait for N ms
• Output the value
• Wait for N ms
• Set the RI output to a logical 1: reading is allowed.
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.
5. DATA PROCESSING
MiCOM C264/C264C treatment entries can be Binary Inputs or Analogue Inputs. They are
issued from
• IOs boards
• MiCOM C264/C264C internal information (System Input, automation)
• Communication acquisition (IED or other computer from LBUS or SBUS)
5.1 Binary Input processing
5.1.1 Binary Input definition

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

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

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

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

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

For some SP, a transition must be confirmed on a certain period of time. If the opposite
transition occurs before this delay, both transitions are discarded.
Two time-out values can be associated with each SP:
• TS: delay for the SET state confirmation
• TR: delay for the RESET state confirmation

Both delays are in the range 0 to 120 s by step of 100 ms. A value of 0 means that no filter is
applied.
The time tag is user-selectable:
• Mode 1: the status is stamped with the time of the transition.
• Mode 2: the status is stamped at the end of the persistent filtering.

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

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

The aim of this automation is to create a direct association between a Single Point and a
Digital Output: a state change on the input produces the opening of the closure of the output.
The relation between the state and the order is defined during the configuration phase.
5.1.3 Processing of Double Point Status

A DP is derived from two Digital Inputs. One is called the Closed contact, the other one is the
Open contact.
Close DI/DO
contact association
From Toggle
acquisition filtering Group
processing
Open Persistance
Manual
contact Toggle filtering
suppression
From filtering Motion
acquisition filtering
Substitution
Transmission – To RCP
Report based To HMI
From IED IED Forcing
To Printer
inputs To Archive
System
Inputs
Transmission –
GOOSE based To
automation
C0134ENa
FIGURE 17: DOUBLE POINT STATUS PROCESSING

DPS are commonly used for all switchgears position. From board valid acquisition the two
contacts are Close and Open (set by configuration when voltage is present). The position of
the switch is:
Close Contact Open Contact DPS State

0 0 Below motion delay, the state is valid motion. For
REPORT no transmission of the transitory state.
After Motion filtering, state is invalid JAMMED
0 1 OPEN
1 0 CLOSE
1 1 UNDEFINED after a permanent filtering
Preliminary treatment (filtering) for some DPs is applied to filter the MOTION state during a
certain period of time. This avoids the transmission of this (normally) transient state.
This treatment is 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 case of confirmed
MOTION00 state) or UNDEFINED (in case of confirmed MOTION11 state). In this case, the
following valid state (OPEN or CLOSE) is always time-stamped with the time of this valid
transition (depending on the persistence filtering feature).
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 case of confirmed
MOTION00 state) or UNDEFINED (in case of confirmed MOTION11 state). In this case, the
following valid state (OPEN or CLOSE) is always time-stamped with the time of this valid
transition (depending on the persistence filtering feature).
OPEN
T00 T00 T11 T11
CLOSE
t0 t1 t2 t3 t4 t5 t6 t7 t8
• t0 : MOTION00 transition
• t1 : MOTION00 state not confirmed, CLOSE state time-stamped t0 if mode 1, t1 if mode 2
(if no persistence filtering applies)
• t3 : MOTION00 state confirmed, state JAMMED time-stamped t2
• t4 : OPEN transition, time-stamped t4 whatever was the mode (if no persistence filtering applies)
• t6 : MOTION11 state not confirmed
• t8 : MOTION11 state confirmed, state UNDEFINED time-stamped t8 C0311ENa
FIGURE 18: MOTION FILTERING

5.1.3.2 DP persistence filtering

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

applied.
• Mode 1: the status is stamped with the time of the transition
• Mode 2: the status is stamped at the end of the delay.

NOTE: If a persistence filtering is applied, the OPEN or CLOSE state cannot
be time-stamped from the beginning of non-complementarity (i.e.
mode 1 of motion filtering cannot apply).
TO TO
OPEN
TC TC
CLOSE
t0 t1 t2 t3 t4 t5 t6 t7
• t0 : CLOSE transition
• t1 : CLOSE state not confirmed
• t2 : CLOSE transition
• t3 : CLOSE state confirmed (stamped t2 if mode 1, stamped t3 if mode 2)
• t4 : OPEN transition
• t5 : OPEN state not confirmed
• t6 : OPEN transition
• t7 : OPEN state confirmed (stamped t6 if mode 1, stamped t7 if mode 2)
C0312ENa
FIGURE 19: DP PERSISTENCE FILTERING

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.4 Processing of Multiple Point Status

A Multiple Point (MP) is derived from N Digital Inputs. It could be also called “1 among N”
BIs. Transient filtering is also added on acquisition for the cases where no Digital Inputs is
SET or more than one Digital Inputs are SET. After this delay, the MP becomes
UNDEFINED.
N is fixed by MiCOM C264/C264C configuration from 2 to 32. There is no GOOSE
transmission mechanism.
A MP can be used in two ways:
• as a status (MPS): in this case, N is up to 16
• as a value, only for TPI: in this case, N is up to 64
contact 1
Toggle
From
filtering
acquisition
contact N Manual
Toggle suppression
From
filtering
acquisition Transmission –
Substitution MP filtering Report based
Forcing
System
Inputs
C0135ENa
FIGURE 20: MULTI POINT STATUS PROCESSING

5.1.4.1 Multiple Point resulting states

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

MP is not being considered in the UNDEFINED state if the position has changed by more
than one step.
MP is UNDEFINED after a user selectable time filtering (from 0 to 60 seconds, step 100 ms)
when no DI is in the SET state (all RESET) or if more than one are in the SET state:
Time-out Time-out
undefined
MP before
filtering
valid
undefined
MP after
filtering valid
C0313ENa
FIGURE 21: MULTIPLE POINT FILTERING

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

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

acquisition through DI or through serial communication) but which must be managed
by the MiCOM computer: the status of these information are saved in non-volatile
memory.
A SI is of SP, DP or MP type and can belong to any type of group.
The processing of 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
which has modified the group status.
A group is calculated with filtered BIs (persistent filtering or motion filtering if configured).
Other computer BIs coming from reports.
The binary inputs states are taken into account as follows:
Single Point Status treated in a group as

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

CLOSE, FORCED CLOSE, SET
SUBSTITUTED CLOSE
OPEN, FORCED OPEN, RESET
SUBSTITUTED OPEN
JAMMED, FORCED JAMMED, INVALID
SUBSTITUTED JAMMED,
UNDEFINED, SELFCHECK
FAULTY, TOGGLING, UNKNOWN
OR SET RESET INVALID SUPPRESSED

SET SET SET SET SET
RESET SET RESET INVALID RESET
INVALID SET INVALID INVALID INVALID
SUPPRESSED SET RESET INVALID SUPPRESSED
AND SET RESET INVALID SUPPRESSED

SET SET RESET INVALID SET
RESET RESET RESET RESET RESET
INVALID INVALID RESET INVALID INVALID
SUPPRESSED SET RESET INVALID SUPPRESSED
NOT
SET RESET
RESET SET
INVALID INVALID
SP and SI from different hierarchical levels can be mixed, for instance a group at substation
computer level can be composed of SP acquired at bay computer level or at substation
computer level.
A group is time stamped with the date / time of the last datapoint which has modified the
group status.
5.1.8 SBMC Mode Processing
When a Bay is in SBMC mode (Site Based Maintenance Control), the status of the Binary
Inputs (associated to this Bay and defined as “SBMC dependant”), takes the forced state
defined in the configuration.
This forced information is delivered to the Remote Control Point (RCP) as long as the SBMC
mode is active on the Bay.
For a group a special feature is implemented: a BI belonging to a group, which is dependent
of SBMC bay state, is not taken into account in group computation if the bay is set in SBMC
mode. If all the BI of a group belong to one or more bays, which are all in SBMC mode, the
group is then in the suppressed state. At the end of a bay SBMC mode, all groups owning BI
of this bay are re-computed.
5.1.9 BI sent to automatism features
In case of automatism running on a client computer, with BI information coming from a
server computer, BI are generally transmitted in the GOOSE based mode. In some cases
where the GOOSE based mode is not used, BI information received by IEC61850 reports
must be used in automatism features.
In any cases where GOOSE based mode and report based mode are used at the same time,
the BI information used is the one receive by GOOSE ( faster transmission than reports).
5.2 Measurement Input Processing

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

acquisition Scaling
management suppression
from digital Threshold

Scaling
acquisition detection
Manual
suppression
from CT/VT CT/VT
Substitution
acquisition calculations
Forcing
Transmission
to:
RCP
HMI
Printer
Archive
Automation
C0136ENb
FIGURE 22: ANALOGUE PROCESSING
5.2.1 Open circuit management

For 4-20 mA transducers, a special feature is implemented to avoid fleeting values around
4 mA:
• in the range [0 .. 3 mA[, the measurement value is set to 0 and the status is set to
OPEN CIRCUIT,
• in the range [3 .. 4 mA], the analogue input is considered to be equal to 0 mA.
5.2.2 Scaling
The real value represented by the measurement can be computed by a linear or a quadratic
transformation:
• Linear, single slope

Value = A*X + B
• Linear, multisegments
Value = Ai*X + Bi with Xi≤X<Xi+1 .

Up to 20 configurable segments [Xi .. Xi+1]
• Quadratic
Value = A X +B or
Value = AX + B
Transformation law and A / B coefficients are defined in configuration.
5.2.3 Zero value suppression

The function Y=f( X) representative of this processing is defined as follows:
− if X∈[ -deadband/2, +deadband/2] ⇒ Y=0 and state = VALID
− if X∉[ -deadband/2, +deadband/2] ⇒ Y=X and state = VALID

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

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

5.2.5 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 e.g. display, alarm, transmission. The measurement takes the
SUPPRESSED state. When the operator "un-suppresses" the measurement, this one takes
its actual state.
5.2.6 Substitution
The value of a measurement can be substituted by an operator (state “SUBSTITUTED”,
value defined by the operator). The measurement stays in this state until he 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.7 Forcing an invalid measurement

When a measurement is invalid (i.e. SELFCHECK FAULTY, UNDEFINED, OPEN CIRCUIT,
SATURATED or UNKNOWN), it can be manually forced by a user (state “FORCED”, value
defined by the operator). This feature is similar to the substitution but the information is
automatically updated when valid information is available again.
The forcing could also be automatic: in this case, the invalid information takes automatically
the FORCED state and the value defined in configuration.
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.8 Measurement resulting states
The Measurement resulting states, following the various filters, which can be applied, are:
State Meaning
VALID Not in one of the following states
SELFCHECK FAULTY AI, DI board fault
SUBSTITUTED Operator action set MV value as valid state
FORCED Automatic valid state and configured value when AI is invalid
SUPPRESSED Operator set MV in this invalid state
UNKNOWN MV is acquired via a transmission link, and the link is
disconnected
SATURATED MV is beyond its nominal input range
UNDEFINED MV is Digital Measurement with invalid coding or computation on
analogue leads to error
OPEN CIRCUIT MV is DC 4-20 mA with input value under 4mA
OVERSHOOT[1..3] One of the 3 overshoot values has been crossed
UNDERSHOOT[1..3] One of the 3 undershoot values has been crossed
5.2.9 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.
During a loss of communication between a client and a server, all server measurements are
set to UNKNOWN on the client.
The measurement information transmitted in a report are:
• the real value (i.e. after scaling)
• the resulting state (mapped on the quality field on IEC-61850)
• the time stamping (in GMT time) and time quality
• the reason for change, which could be one of the below values:
− change of quality (set if the measurement resulting state has changed)
− cyclic change (set if the measurement value has changed, without modification of
the resulting state)
A Measurement value can be transmitted periodically or upon variation (% of nominal), and
anyway on state change.
5.2.9.1 Periodic Transmission

Two periods are defined in database, on a per MiCOM computer basis:
• a short period from 0,1 to 60 seconds (step 0,1 second)
• a long period, from 0,5 to 60 seconds (step 0,5 second)

Each measurement is associated to one of the two periods. All measurements of one period
are transmitted at the beginning of each cycle.
All measurements values transmitted within one transmission cycle are the latest acquired
values.
5.2.9.2 Transmission upon variation
Measurements can be transmitted upon variation: a value is sent if the acquired value (Vacq)
is different from more than a specified amount ∆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.9.3 Transmission upon trigger

One or more measurements can be associated to a single or double BI “trigger”. When the
BI goes to the state SET / CLOSED (or FORCED SET, SUBSTITUTED SET, FORCED
CLOSED / SUBSTITUTED CLOSED) all associated measurements are transmitted
immediately. The same behaviour if the BI is in this state at the initialisation of the computer.
As much the BI is in this state the associated measurements are transmitted after change of
state or according to the configuration (periodically, upon variation, threshold variation)
5.2.10 CT/VT additional processing

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

5.2.10.2 Outputs
The CT/VT calculation functionality provides:
• RMS values, for currents and voltages
• Frequency of the network
• Active power (total and on a per phase basis)
• Reactive power (total and on a per phase basis)
• Apparent power (total and on a per phase basis)
• Power factor (total and on a per phase basis)
• Phase angles
• Sequence components (Id, Ii, I0, Vd, Vi, V0)
• Ratio of harmonics (up to the 15th harmonic)
• Total Harmonic Distorsion (THD) and Total Demand Distorsion (TDD). Harmonics are
evaluated up to the 15th order.
With the additional synchrocheck option, following values are computed:
• Slip frequency
• Amplitude
• Phase difference
• Synchrocheck voltage
5.2.10.3 Behaviour
5.2.10.3.1 Principle
The use of power electronics distorts what would ideally be a perfect sine wave. These
distortions are called harmonics. Each individual harmonic has a sine wave shape. The order
of the harmonic is defined by the frequency of the harmonic divided by basic frequency (50 /
60 Hz). The total harmonic distortion 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.
5.2.10.3.2 Calculation of measurements
Let N be the number of samples recovered for one period of the signal (i.e. 64 samples per
period whatever the network frequency).
All these samples must be gathered in a revolving list stored in active memory. There is thus
in memory an active list of k.N elements. k is the number of sample channels.
Types
The following primary measurements shall be derived directly from sample values:
• RMS Current and Voltage
• Active Power (Watts)
• Vars (Using Active Power calculation method with the voltage samples retarded by
90°)
The following measurements shall be obtained from the Fourier of sample values or the
Fourier values of the above-derived measurements.
• Sequence Components (Id, Ii, I0, Vd, Vi, V0).
• Magnitudes
• Phase angles
• Power Factor
• VA
• THD and TDD
• Specials (for products with check-sync.)

Algorithms
Frequency
The frequency is directly computed through the timer frequency.
Fast Fourier Transform
At each period, the FFT (Fast Fourier Transform) is performed. This gives (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
1 63
Active power: P = ∑ Vi I i
64 i =0
1 63
Reactive power: Q = ∑ Vi I i−16
64 i =0
NOTE: The reactive power is computed by taking the values of the current a
quarter of period before (sin(x) = cos (x – pi/2)
Apparent power: S = P² + Q²
P
Power factor: cos(ϕ ) =
S
Q
Angle: ϕ = tan −1 ( )
P
Harmonics
Harmonic values are directly issued from the FFT.
Sequence components
The sequence component computation is based on the fundamental values of phase and
magnitude (from the FFT), i.e. its imaginar and real part.
• Direct component
Re(direct ) = × (Re( A) + Re( B ) × cos(120) − Im(B) × sin(120) + Re(C ) × cos(120) + Im(C ) × sin(120) )
1
3
Im(direct ) = × (Im( A) + Im(B) × cos(120) + Re( B) × sin(120) + Im(C ) × cos(120) − Re(C ) × sin(120) )
1
3
Inverse component
Re(direct ) = × (Re( A) + Re( B) × cos(120) + Im(B) × sin(120) + Re(C ) × cos(120) − Im(C ) × sin(120) )
1
3
Im(direct ) = × (Im( A) + Im(B ) × cos(120) − Re( B ) × sin(120) + Im(C ) × cos(120) + Re(C ) × sin(120) )
1
3
• Homopolar component
Re( direct ) = × (Re( A) + Re( B ) + Re(C ) )

1
3
Im( direct ) = × (Im( A) + Im(B ) + Im(C ) )
1
3
Check synchronising
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.
System synchronising
In opposite to the check synchronising, the system synchronising mode is entered when a
close control is received by the CT-VT module and if the ∆F value is under a user defined
threshold.
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.
Notice that CT-VT module should exit the system synchronising mode after a user defined
tmporisation.
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 / ∆ϕ
5.2.10.4 Limits and performances

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

5.2.11 Digital Measurement Processing

A Digital Measurement is derived from a Digital input. Digital Measurements are used for
process measures or Tap indications.
The DM is UNDEFINED in the followings conditions:
• The value is not stable.
• BCD: a quartet is more than 9
• Decimal: no bit is set or more than one for tens or unit

Two others bits can be used:
• For read inhibit: in this case, the DM is acquired when the Read Inhibit bit is set.
• For the sign

5.3 Tap Position Indication processing

5.3.1 Acquisition from Digital Inputs
The tap position is acquired on digital input boards . It could be:
• A Multiple Point , if so, the resulting states are considered as values
• A digital measurement using one of the following encoding:
− Decimal
− Gray
− BCD
5.3.2 Acquisition from Analogue Inputs
The tap position is acquired by measuring a current input.
A minimum value Imin (mA) corresponds to the lowest position 1 of the tap , and a maximum
value Imax corresponds to the highest value N.
The input current should take only discrete values: Ik =Imin + (K -1)(Imax_Imin)/(N-1) , with
K the position of the tap.
However the tap is considered in the position K if the current is in the range [Ik-∆I/2 ..
Ik+∆I/2], with ∆I = N% of (Imax – Imin). The N percentage is defined in configuration.
The tap position is considered UNDEFINED outside of this range.
5.3.3 Manual suppression

A TPI can be suppressed by an order issued from an operator. No subsequent change of
value or state on a suppressed TPI can trigger any action e.g. display, alarm, transmission.
The TPI takes the “SUPPRESSED” state. When the operator unsuppresses the TPI, this one
takes its actual state.
5.3.4 Substitution
The value of a TPI can be substitute by an operator (state “SUBSTITUTED”, value defined
by the operator). The TPI stays in this state until he unsubstitutes it.
When a TPI is substituted, no changesof 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 (i.e. SELFCHECK FAULTY, UNDEFINED or UNKNOWN), it can be
manually forced by a user (state “FORCED”, value defined by the operator). This feature is
similar to the substitution but the information is automatically updated when valid information
is available again.
The automatic forcing function is not provided for TPI.
5.3.6 TPI resulting states

The state of a tap position can be:
State Comment
VALID not in one of the below states
SELFCHECK FAULTY Due to an AI board fault or a DI board fault
SUBSTITUTED See § 4.4
FORCED
SUPPRESSED
UNKNOWN If the tap position is acquired via a transmission link, the
information is unknown when the link is disconnected.
UNDEFINED Due to a wrong encoding for a digital acquisition, or a saturation,
an open-circuit or an out-of-range value for an analogue
acquisition
OVERSHOOT[1..3] It exists 3 “Overshoot” states, one for each upper threshold
violation. Only one could be set at one time
UNDERSHOOT[1..3] It exists 3 “Undershoot” states, one for each lower threshold
violation. Only one could be set at one time
5.3.7 Transmission
The TPI are transmitted on a client-server basis on the IEC-61850 network using the report
mechanism.
During a loss of communication between a client and a server, all server TPI are set to
UNKNOWN on the client.
The TPI is transmitted as soon as a value change or a status change is detected. The TPI
information transmitted in a report are:
• the TPI value
• the resulting state (mapped on the quality field on IEC 61850)
• the time stamping (in GMT time) and time quality
• the reason for change, which could be one of the below values:
− change of data (set if the value has changed)
− change of quality (set if the quality has changed)
− change due to control (set if the state or quality change is due to a control)
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 which count complementary states.
At processing level special persistent and complementary filters eliminate non-stable pulses.
The integer counter (also transmitted) can be scaled (among of energy of valid pulse).
5.5 Energy counting

The energy counting function aims to calculate exported and imported active energy
(in kWh) and exported and imported reactive energy (in kVarh) from active and reactive
power issued from CT/VT calculation, digital, analogue boards measurements or IEDs
measurements..
Calculation of the energy is done periodically. The period is defined either by an external
pulsed applied on a digital input, or by the internal clock of the computer. The choice of the
origin of the periodic signal is defined during the configuration phase on a per computer
basis.
Whatever is the origin of an integrated measurement, the integration is done after scaling
with a step of one second.
The integration method used is the trapezium one:
E = ∑ Ei
⎛ ( M 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.
WARNING: THE ENERGY COUNTER VALUES ARE NOT TO BE USED FOR BILLING
APPLICATION.
5.6 Basic Data Manipulation

5.6.1 Test Mode enhancements
The existing C264 Test Mode allows to deactivate the DOU/CCU relays output in case of
control sequence.
The enhancements allow to:
1. manage the Test Mode in case 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 case of computer redundancy, the Test Mode activation is performed independently for
each C264 (Main and Backup) 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 associated to a datapoint (i.e. 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 responsability of controls performed during the Test
Mode, and before leaving the Test Mode, he owns all responsability to restore the system. In
Test Mode, all controls performed may impact Isagraf programs or PSL automatisms.
NOTE 1: Digital Setpoint with measurement feedback are not managed in Test
Mode (i.e. 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, which is
send to another computer - which is not in test mode - or 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 case of Direct Execute control, this SPS is:
• SET as soon as the C264 accepts the control (i.e. after the control checks)
• RESET when the final control acknowledgement is sent

In case of SBO control, this SPS is:
• SET as soon as the C264 accepts the control selection (i.e. after the selection checks)
• RESET when the final control acknowledgement is sent

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 case, 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 case, the new control is refused).
It exists 3 cases to manage (PSL means PSL or DI/DO association – Operator means from
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 case « Control 1 from Operator and Control 2 from Operator » is already managed: in
this case, the control 2 is rejected.
Cases – 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”
Cases – 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”
6. CONTROL SEQUENCES
6.1 Generic 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 Generalities
The MiCOM C264/C264C 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
The following control types 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
case 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 case 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.
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 (e.g. Auto-recloser ON/OFF), change operating modes etc.
• 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:

1. execution phase: If the execution phase ends normally the computer generates
a positive acknowledgement and the control sequence ends. In case 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:

1. 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).
a positive acknowledgement and the control sequence ends. In case of abnormal
termination, the control sequence is aborted and the computer generates a
negative acknowledgement.
• three phases – “SBO many” mode:

1. selection phase: ditto “SBO once” mode
a positive acknowledgement and waits a new execution request. In case of
abnormal termination, the control sequence is aborted and the computer
generates a negative acknowledgement.
3. unselection phase: The computer proceeds to the deselection of the device and
ends control sequence sending positive acknowledgement. In case of fail
deselecting the device the computer sends a negative acknowledgement.
Direct execute Execution via
mode I/O boards
or
Page 60/138
Execution Execution via

checks IED
C264/EN FT/C40
or
System
controls
execution phase
Select Before Operate

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

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

I/O boards
Selection Hardware Execution Hardware
or
checks selection checks Deselection
Execution via
IED
C0314ENa
selection phase execution phase
Functional Description
MiCOM C264/C264C
Execution via
Select Before Operate mode many
I/O boards
Execution or
checks
Execution via
IED
Device
Device
Selection
unselect
checks
Execution via
MiCOM C264/C264C
I/O boards
Functional Description
Execution
or
checks
Execution via
IED
selection phase execution phase (1) unselection phase
Select Before Operate mode many Execution via

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

I/O boards
Execution
or
checks
Execution via
IED
selection phase execution phase (1) unselection phase
(1) An execution phase with two execution requests is given as an example, it may have more or less
C0315ENa
C264/EN FT/C40
Page 61/138
6.1.3 Direct Execution mode

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

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

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

6.1.4 SBO once mode
6.1.4.1 Selection phase in “SBO once” mode

During the selection phase initialised by a selection request of the control, the computer
performs selection checks in order to verify if the device is selectable or not.
If no fail occurs during these checks, the device is selected and positive acknowledgement is
sent. Otherwise the selection request is refused and a negative acknowledgement is sent
giving fails cause. If the selection of the device is accepted the computer starts a delay in
which it waits:
• An execution request (open/close, low/raise)
• A cancel of the selection request

After 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 following diagram shows the selection phase of a device configured in SBO once mode.
Unselected
device
Selection request
no
Device selectable ?
yes
Device Already
selected
Perform Selection
no checks
All checks OK
Device selection
no
Device selection OK
Set “device selected”
send positive
acknowledge
Selection Time-out
launching
Wait new request

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

6.1.4.2 Execution phase in “SBO once” mode

The execution phase can start only after reception of an execution request and if the device
has been selected before.
In this phase, the computer performs the execution checks, and if no fail, it proceeds to the
execution according to the configuration, via the IO boards or IED communication.
If the execution ends normally, a positive acknowledgement is sent, and the control
sequence ends. In case of fail the control sequence is aborted and the computer sends a
During this phase a “cancel” request is not guaranteed except for synchronised circuit
breakers devices (refer to specifics treatments for synchronised circuit breakers below).
EXECUTION PHASE IN SBO ONCE MODE Execution request –SBO

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

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

6.1.5 SBO many mode

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

The selection phase is identical to the “SBO once” mode selection phase.
6.1.5.2 Execution phase in SBO many mode

The difference with the SBO once mode is that after having performed an “execution
request”, the computer stays in execution phase waiting a new execution order or an
“unselect” request. The execution phase ends only after an “unselect” request or “cancel”
request by the initiator.
Upon reception of an “unselect” request the computer ends the execution phase and goes
to the selection phase.
Execution Phase SBO many Execution phase- device

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

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

6.1.5.3 Unselection phase in SBO many mode

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

Set « device
deselected »
End of sequence
C0320ENa
FIGURE 31: UNSELECTION PHASE IN SBO MANY MODE
6.1.6 Generic selection checks

Checks performed during the selection phase are:
• 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 case of fail, the initiator of the request may bypass the following checks:
• Uniqueness
Next diagram schematises controls and bypass according the description of the device.
Selection checks for SBO device Unselected device
Inter-control delay Not configured

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

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

6.1.6.1 Inter-control delay

A user-selectable delay can be defined in 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
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 case 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 case an automatism is
active for device monitoring (e.g. ATCC).
In this case 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 bypass this control in the
selection request.
In case 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 (case of circuit breakers). Its behaviour can be chosen ( during
the configuration step) among one of the four following cases:It is given by a binary input or
computed using more than one binary input (case 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 case, if the request is refused, a negative acknowledgement is sent back
6.1.6.9 Uniqueness
It is possible by configuration to prevent to have more than one control at a time.
• For the whole substation
• Inside a bay
The following figure describes the algorithm used between computers.
A
Uniqueness does not be checked for
this device or uniqueness is bypass
Uniqueness must be checked for this
device and there is no bypass
→ Goose is sent to other bays

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

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

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

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

C0322ENa
FIGURE 33: CHECK OF UNIQUENESS

If a device is under control and another control is sent on this device, the second one is
ignored.
In case 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 follow:
• 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 case 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 case 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
case 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 case 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
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 feedbackuntil 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 case, the input information of the device status must be configured.
Digital Setpoints
A control sequence via Digital Setpoints has particular treatments during the control request
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 intelligent devices, 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 etc.
• Output control type: permanent , pulse
• Destination: I/O board, IED
• Time-out delays: selection phase time-out, selection Feedback delays, open/close

Feedback delay etc.
6.1.10.1 Direct execute time sequencing

The following chronogram shows an example of normal termination on Direct Execute
sequence.
DPC open
(resp. close)
DPS open/ resp close
(close/ resp open)
Feedback Delay
CO Pulse Delay
0-60s
0-5s
3 4 5
1 execution request C0323ENa
FIGURE 34: NORMAL TERMINATION OF DIRECT EXECUTE SEQUENCE

The following chronogram shows an abnormal termination of Direct Execute sequence. The
device hasn’t taken the expected position in the given delay.
DPC open
(resp. close)
SPS close
(resp. open)
SPS open
(resp. close)
Feedback Delay
CO Pulse Delay
0-60s
0-5s
3 4 5
FIGURE 35: ABNORMAL TERMINATION OF DIRECT EXECUTE SEQUENCE

6.1.10.2 SBO Once time sequencing
The configurations below are given as examples
Device Configuration A: the optional selection control and Selection position information
are configured
The following chronogram shows a normal termination of the control sequence.
Selection of the
device
Selection position
input
Device output control
Device status
Open/Close Selection
Selection
Feedback Feedback
Feedback
Selection time-out Delay Delay
Delay
0-60s
0-1 s 1-10mn 0-1 s
2 5
1 3 4
Selection phase Execution phase
C0325ENa
FIGURE 36: NORMAL TERMINATION OF THE CONTROL SEQUENCE
• Stage 1: device selection (closing the associated output control)
• Stage 2: the selection is confirmed by the associated input information in the feedback
delay (0 – 1-sec user selectable)
• Stage 3: close the device before the end of the selection timeout delay (0 – 10 MN
user selectable)
• Stage 4: the device has taken the expected position (close) in the feedback delay (0–
60 sec user selectable). The computer deselect the device (open selection output
control)
• Stage 5: confirmation of the deselecting of the device in the same given delay than
stage 2.
The following chronogram shows controls sequence which is aborted after time-out of the
selection delay.
Selection of the
device
Selection position
input
Device output
control
Device status
Input information
Selection Selection
Feedback Feedback Delay
Delay Selection time-out
0-1 s 1-10mn 0-1 s
1 2 3 4
Selection phase
C0326ENa
FIGURE 37: ABORTED CONTROL SEQUENCE
• Stage 2: the selection is confirmed by the associated input information in the feedback
delay.
• Stage 3: timeout of the delay - the device is deselected
• Stage 4: confirmation of the deselecting of the device

Device Configuration B: the optional selection control is configured and Selection position
information is not configured
The following chronogram shows a normal termination of the control sequence.
Selection of the
device
Output Control Of
The Device
Device status
Open/Close
Feedback
Selection time-out Delay
0-60s
1-10mn
1 2 3
Execution phase
Selection phase
C0327ENa
FIGURE 38: NORMAL TERMINATION OF THE CONTROL SEQUENCE
• Stage 2: close the device before the end of the selection timeout delay (0 – 10 MN
user selectable)
• Stage 3: The device has taken the expected position (close) in the feedback delay (0–
1-sec user selectable). The computer deselect the device (open selection output
control)
6.1.10.3 SBO many time sequencing
SBO many mode is exclusively used for control of transformers. Refer to associated section.
6.2 Control of non synchronised breakers

6.2.1 Non synchronised circuit breakers features
The following table gives inputs and outputs circuit breaker’s features 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 Circuit breakers features
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.
(5) 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 39: CLOSE CB BY EXTERNAL SYNCHROCHECK WITH AUTOMATIC SET ON

The “close” control sequence performed on the MiCOM C264/C264C is done as follows:
Selection phase:
1. Set on synchrocheck module (if the control is configured)
2. Verify synchrocheck on/off information associated to the output (if is configured)
3. Close device selection output to select the device (if is configured)
4. Verify selection device input information associated to the output (if is configured)
5. Wait the execution request or timeout selection
In case of fail to 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 following chronogram 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 40: CHRONOGRAM OF A SUCCESSFUL "CLOSE WITH SYNCHROCHECK"

The following chronogram 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 41: 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:
1. a “Direct Execute” sequence to put in service the external synchrocheck module
2. a SBO once sequence to close the CB by the synchrocheck module and put out of
service the synchrocheck module
Three sequences:
1. a “Direct Execute” sequence to put in service the external synchrocheck module
2. a SBO once sequence to close the CB by the synchrocheck module
3. a “direct execute” sequence to put out service the external synchrocheck module
The following scheme shows a close control request in which the external synchrocheck
module is managed manually from the OI or gateway.
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 42: 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 case of fail to one of these operation the sequence ends with a negative
acknowledgement
Second sequence (SBO ONCE): close the device with synchrocheck”
Selection phase:
2. Verify selection device input information associated to the output (if is
configured)
4. In case of fail to 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
6. Verify the device position become close in the given delay
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 following chronogram shows a successful control sequence ”close with synchrocheck”
performed in three sequences. In case 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 43: 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 following chronogram 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 44: ”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 following chronogram 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 45: CANCEL CLOSE REQUEST

6.3.3 Circuit breakers with internal synchrocheck

On this configuration synchrocheck is assumed by an internal computer automatism, which
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 which are 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 the execution close request or timeout selection
In case of fail to 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
Case 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

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

delay
• Send a negative acknowledgement

Case 3: time-out of the given delay without synchrocheck response
• stop the synchrocheck automatism

Case 4: reception of cancel request awaiting synchrocheck response

The following chronogram 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 following chronogram 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 case of fail to one of these operations the controls sequence is stopped with
a negative acknowledgement
Execution phase:
5. Ask to the internal automatism to close the device
6. Verify the device position become close in the given delay
7. Set off the synchrocheck automatism if is configured to be set off automatically
Third sequence (DIRECT EXECUTE): set off the internal synchrocheck automatism
This sequence takes place 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 its is configured)
NOTE: During SBO sequence after step 5 the initiator of the request may
force the closing of the device.
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

MiCOM C264/C264C computers manage all types of disconnecting switches such as:
• disconnectors
• earthing switch
• quick break switch
DISCONNECTORS SWITHES
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 Transformers 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 (1)
(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
increase 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

The control of transformer can be performed in the three modes “Direct Execute”, “SBO
once” and “SBO many”.
Additionally of 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 case 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 which 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 the execution request (low/raise) or timeout selection
In case of fail to one of these operations, the device is deselected, the controls
sequence is aborted with a negative acknowledgement.
Execution phase:
4. According the request “raise or lower” and the type of device, execute the
associate control
5. Wait the TCIP information and TIP value to confirm execution. Two cases:
• Case 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).
• Case 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 new execution request or unselection request to deselect the device
• In case of new request the computer repeat the steps 4 and 5.
• In case of unselection request the computer deselects the device (if it

was previously selected), and ends the sequence with a positive
acknowledgement
The following chronogram 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
(1) the TPI value must take the expected value at least at the end of TCIP disappearance
The following chronogram shows an abnormal termination of tap changer control sequence
due to absence TCIP confirmation. In this case 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 case the TCIP input information is not configured the selection and execution phase are
performed as follows:
Selection phase:
1. Close device selection output to select the device (if configured)
2. Verify selection device input information associated to the output (if configured)
3. Wait the execution close request or timeout selection
In case of fail to one of these operations, the device is deselected, the controls
sequence is aborted with a negative acknowledgement.
Execution phase:
4. According the request “raise or lower” and the type of device, execute the
associate control
5. Wait the TPI information and compare with the previous value. The difference
must confirm the “low” or “raise” execution. Two cases:
• Case 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.
• Case 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 new execution request or unselection request to deselect the device
• In case of new request the computer repeat the steps 4 and 5.

• In case of unselection request the computer deselects the device (if it
was previously selected), and ends the sequence with a positive
acknowledgement.
The following chronogram 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 following chronogram 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 case of suppress or substitution of TPI value the control sequence is aborted with
negative Acknowledgement. In case 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 case 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 having performed 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
Ditto execution phase of “Direct Execute” mode.
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 to end the sequence within the computer, is
not sent to 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, which gives the state of the controlled function (e.g. 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,
which may a SPS or DPS. System inputs generated by system outputs are stored in non-
volatile memory. In case of computer’s initialisation they are restored.
6.9 Kind of control sequence

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

Receiving control, the control sequence executes configured checks:
Operational conditions
• MiCOM C264/C264C 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, …),
• 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),
• MiCOM C264/C264C Local Control Display,
• MiCOM C264/C264C 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.
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

It is possible by configuration to prevent control if the status of the device is not valid.
6.10.7 Lock device

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

Controls are not allowed on a device if there is an associated automation in running.
For example controls issued from PACiS OI or gateway are not allowed on a transformer
controlled by voltage regulation.
6.10.9 Interlocking
The operating of a switching device (Circuit breakers, Traditional disconnecting switches,
Disconnecting switches with abrupt rupture, Ground disconnecting switches) is directly
related on its nature and its environment.
To operate these devices some conditions have to be respected. These conditions, called
interlocking, are managed by logical equations within the MiCOM C264/C264C.
The goal of the function of interlocking is to prohibit control sequence that may violate device
operating condition (e.g. break capability, isolation…) 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).
Transformer is the only device supporting 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.
6.12 Fast Load Shedding ( FLS )

The Fast Load Shedding (FLS) automation function description and implementation is part of
a distinct Application Chapter (AP).
7. AUTOMATIONS
MiCOM C264/C264C provides three different ways to perform automation functions:
• Built-in applications
• Programmable Scheme Logic
• Programmable Logic Controller

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

Within the MiCOM C264/C264C some built-in automation functions are available and can be
set directly by the user:
• Synchrocheck
• Auto-Recloser
• Trip Circuit Supervision
• Automatic Voltage regulation
7.1.1 Synchrocheck
MiCOM C264/C264C synchrocheck functionality is designed to measure two voltages with
respect to phase angle, frequency and magnitude to safeguard against the interconnection
of two unsynchronised systems.
The voltage measurements come from the CT/VTs board (TMU200).
The synchrocheck functionality can work in the following schemes:
• Automatic and manual network locking on live line / live bar in locking or coupling
mode
• Automatic and manual network connection on live line / dead bar
• Automatic and manual network connection on dead line / live bar
• Automatic and manual network connection on dead line / dead bar

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 46: CHECK SYNCHRONISER APPLICATIONS ~

The absolute values of the two voltages (Vline and Vbusbar) must be above or below settable
thresholds, to allow the circuit breaker closing.
The following voltage controls are available:
• Vline and Vbusbar for network coupling
• Vline and Vbusbar for network locking
• Vline and not(Vbusbar)
• not(Vline) and Vbusbar
• not(Vline) and not(Vbusbar)

With Vline and Vbusbar TRUE if the measured voltage is above the threshold V>, and not(Vline)
and not(Vbusbar) TRUE if the measured voltage is below the threshold V<.
The selection of the voltage control is made during the configuration phase.
By configuration, a single synchrocheck can manage two circuit breakers. Be careful, in this
case the voltage switching is not managed by the computer.
7.1.2 Auto-Recloser (AR)
7.1.2.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 temporisation 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 case 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.2.2 Behaviour
The general diagram of the auto-recloser function is:
Auto-recloser out
of service
In Service request
Auto-recloser in
service
TRIP /TRIP_1P_X
3 phases
no 1 phase
CB_HEALTHY Analysis of the CB_HEALTHY no
Cycle n˚=1
= SET ? received trip = SET ?
yes yes
Waiting CB Waiting CB
opening opening
End of 150 ms timer End of 150 ms

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

TRIP closed
Launch Cycle = cycle +1

recovering timer
Launch
recovering timer
End of TRIP
timer
Cycle n˚=2
TRIP End of
timer
no
Last cycle?
yes
AR locked
C0137ENa
FIGURE 47: AUTO-RECLOSER SCHEME LOGIC

7.1.2.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.2.2.2 Analysis of the receiving trip

This analyse allows to detect the type of auto-recloser cycle, which 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 will be not
authorised and the automation will be re-initialised to wait the first cycle. The CB_HEALTHY
BI is optional: if it doesn’t exist, no check is done.
7.1.2.2.3 Waiting CB opening
As soon as the trip has been detected, a 150 ms timer is launched to wait 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 poles CB:
• Whatever was the cycle, the 3 phase position is awaited in the OPEN state
(CB_STATE)
For a 3-phases 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.2.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 case, the current
cycle is stopped and the second 3-phases slow cycle is launched.
7.1.2.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 the first
cycle.
7.1.2.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.2.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 which lead to an auto-recloser locking are:
• A trip during the last auto-recloser cycle (in this case, 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 (i.e. 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 case, 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 case, 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.2.3 Informations 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.3 Trip Circuit Supervision

The trip circuit supervision monitors the trip circuit wiring continuity irrespective of CB
position but only when the trip relay is not activated. Activation of the trip relay is indicated to
the C264 by a separate input and inhibits the detection of continuity.
The MiCOM C264/C264C computer is able to support the two diagrams used in Trip Circuit
Supervision:
• Trip Circuit Supervision with one Digital Input + external resistor.
The resistor in the trip circuit supervision scheme (R) should have a value according to 2
criteria:
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 has been 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.
Areva recommends 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-
Vn+
DI-3
Vn-
CB
- Uaux
C0138ENb
FIGURE 48: TRIP CIRCUIT SUPERVISION WITH ONE DI
• Trip Circuit Supervision with two Digital Inputs without external resistor.
+ Uaux
Computer
Protection relay
Vn+
DI-1
Vn-
Vn+
DI-2
Vn-
Vn+
DI-3
Vn-
Vn+
DI-4
Vn-
CB
C0139ENb
- Uaux
FIGURE 49: TRIP CIRCUIT SUPERVISION WITH TWO DI

NOTE: This diagram can be used with inputs which detection threshold of the
"set" state is > 55% Vn (example CCU A07).
7.1.4 Automatic Voltage Regulation (AVR)

7.1.4.1 Introduction
The Automatic Voltage Regulation function is used to automatically maintain the correct
voltage at the lower voltage of transformers. Secondary voltage is changed by controlling the
tap changer of transformers.
AVR is able to manage one transformer or several transformers in parallel. Transformers are
in parallel if their secondary poles are interconnected. Each transformer is controlled by one
computer but AVR function is only activated on one computer. The following figure shows an
example of architecture for AVR function controlling two transformers.
AVR function is activated on computer C264-1. This computer gets analogues values from
computers C264-2 and C264-3 through the station bus and sends tap changer commands
through the station bus.
acquisition of U,I,Q,P
Tr2
station bus C264-2
(iec 61850)
command of tap changer

C264-1
AVR on
acquisition of U,I,Q,P
Tr3
C264-3
command of tap changer

C0344ENa
AVR also manages:
• Active and reactive compounding in order the maintain the voltage at a remote
location,
• Homing in order to adjust a transformer to the voltage of the busbar which it will be
connected to,
• Minimisation of circulating currents.
7.1.4.2 Interfaces
For each transformer, the MiCOM C264/C264C that acquires:
• Active and reactive compounding in order to maintain the voltage at a remote location,
• Electrical topology of the LV side, including connection of the transformer to the

busbar and coupling of busbars into the LV level,
• Tap Changer MCB state (Tap Position Indication).

The operator, through PACiS OI or TE, has an access to the following controls:
• Global AVR on/off,
• AVR on/off per busbar,
• Five target voltages per busbar (5 floating values: % of Vtarget in the range [-10% ,
+10%] , step 1%)
The current busbar AVR mode is equal to (busbar AVR mode) AND (Global AVR mode).
The following specific alarms and indications are available:

• Substation alarms or indications
− Homing On/Off (defined during the configuration phase)
− Target Not Achievable
− AVR defective
− Error Log Indication
− DBI override
• Busbar alarms or indications
− Invalid voltage (when different values for parallel transformers)
− More than four transformers in the group
− Under-voltage or over-voltage: AVR INHIBITED
− A circuit breaker or a disconnector in an invalid state in the group
• Transformer alarms or indications
− AVR on/off
− Hunting: this alarm is reset 30 seconds after the group is switched to AVR Off
− MCB tripped
− bad TCIP: this alarm is reset 30 seconds after the group is switched to AVR OFF
− Tap Position is not the expected one
− current > Overcurrent value
− AVR disconnected
− Bay in local mode
− Voltage, current, MW and MVAR
− AVR homing
− Invalid Voltage
− Low Voltage
− Over Voltage
− Run Away: this alarm is reset 30 seconds after the group is switched to AVR OFF
− Tap long TCIP

The AVR Defective Alarm and the AVR Error Log Indication are grouped alarms with the
following inputs:
• Per busbar
− Invalid voltage (when different values for parallel transformers)
− More than 4 transformers in the group
− A circuit breaker or a disconnector in an invalid state in the group

• Per transformer
− hunting
− MCB tripped
− Bad TCIP
− Tap position is not the expected one
− Bay disconnected (this takes into account power supply fail)
− Bay in local mode
− Invalid voltage
The AVR Defective Alarm is set if one of the inputs is set, and is reset if all the inputs are
reset.
The AVR Error Log Indication is set if one of the input is set and is reset if the operator
selects the "Clear AVR Faults" command.
7.1.4.3 Groups
7.1.4.3.1 Definition
A group defines a set of interconnected busbars. A transformer belongs to a group if it is
electrically connected to a busbar of this group into the low voltage level.
Group mode is used to allow the automatic control of transformers. Group mode is either In
automatic control, or Out of automatic control. Busbars and transformers have their own
modes used to calculate the group mode.
7.1.4.3.2 Group mode calculation
This section details the group mode calculation. Each transformer, busbar and group is
characterised by attributes, used to calculate the transformer, busbar and group modes.
Attributes are entered during the configuration phase or calculated with the dynamic
electrical topology and settings of the system. Attributes may be ignored to calculate the
mode, this is defined during the configuration phase.
Transformer attributes are:
• Type (Auto or double wound)
• Transformer rating in MVA
• Number of taps
• Tap span
• Its actual connection with a busbar (topology)
• The state of its MCB (Open or Closed)
• Tertiary reactor capacities (in MVAR)
• The state of its tap changer: normal, abnormal (tap changer control) the state is
abnormal if:
− TCIP signal too late or too long,
− the tap is invalid,
− the tap number is not the required tap, we may have this problem after a tap
operation if the tap number is not the expected one.
• Its hunting status (True or False). Hunting is detected if more than N changes occurs
in less than T. The window time for hunting is comprised between 120 seconds to
1800 seconds in 0,1 second increments.
• Its homing status (On, Off or Inhibited)
• Status of the bay containing the tap change control: local/remote,

connected/disconnected (supervision values)
• Associated Voltage, current, MWs, MVARs, and their validity (measured values)
• Its mode: In or Out (of automatic control). Mode is Out if:
− The transformer is disconnected AND it is not in Homing mode

OR
− The transformer is connected OR it is not in Homing mode,

AND
− Tap changer is tripped OR tap changer state is abnormal OR transformer is

hunting OR its voltage is invalid OR the bay containing the tap changer control is
in local mode OR the bay containing the tap changer control is not accessible
OR
− The busbar is OUT of automatic control

A transformer is disconnected if it is not electrically connected to a busbar.
Busbar attributes are:
• Its transformers (configuration and topology)
• Its topology (busbar section and coupler)
• Its voltage target
• Its priority. This is given by configuration.
• Its actual voltage: This voltage is the average of the LV voltages of the connected
transformers. If one of the voltages differs by more than x% from the average, or if one
voltage is invalid then actual voltage is invalid.
• Its mode: In or Out (of automatic control). Mode is Out if:
− The mode of one of the transformers connected to it is Out

OR
− Actual Voltage is invalid.

Group attributes are:
• Its voltage target. This target is deduced from the busbar target composing the group.
The busbar with the highest priority forces the target.
• Its actual voltage. This voltage is the average of the busbar actual voltages. If one of
the voltages differs by more than x% from the average, or if one voltage is invalid then
actual voltage is invalid.
− busbars. This is given by the topology.
− Its mode: In or Out (of automatic control). Mode is Out if:
− Global AVR is Out

OR
− The mode of one of the busbars composing the group is Out and the mode
group connexion is "IN and OUT => OUT”.
OR
− Actual voltage is invalid

OR
− More than 4 transformers in the group.

OR
− Invalid state of a disconnector or a circuit breaker in the group.

When a group is set OUT of automatic control, it remains in this state until the operator sets
the group IN automatic control.
It is only necessary to select one busbar in a group to automatic control to place the whole
group under automatic control.
When the substation control mode is Remote, the AVR control is allowed from the RCP and
inhibited from the SCP. When the substation control mode is Standby, the AVR control is
allowed from the SCP and inhibited from the RCP.
7.1.4.4 Tap changer control

If a transformer is in automatic control and if there is an invalid evolution of the tap changer,
then the tap changer MCB is tripped and the RunAway alarm is set.
7.1.4.5 Moving Tap Changers

7.1.4.5.1 General
Automatic control of a transformer is only allowed if it belongs to a group in Automatic control
mode or for homing. Manual control of a transformer is only allowed if its setting mode is Out
of automatic control.
Note that:
• Automatic control of a tap changer is independent of the mode of the substation

(SCP/RCP)
• Automatic control of a tap changer may be used in conjunction with manual control of
transformer belonging to an other group in manual mode or with manual control of the
rest of the apparatus (breaker, disconnector, protections, ...)
• Simultaneous operations on transformers belonging to independent groups is allowed,

since the electrical topology is not affected.
• Decision to move one or more tap changers is caused by one of the following reasons:
• Voltage in one group is outside of the Voltage Target Deadband. This is the most
common situation.
• Voltage is correct, but there is a circulating current between parallel transformers .

This will happen when two groups are interconnected.
• Voltage is correct, but the tap span and patterning may be changed when any of the
relevant switchgear change state.
• Homing of one transformer. This will happen when the circuit breaker at the LV side of
the transformer is open, and Homing status is on.
7.1.4.5.2 Voltage is outside of the Voltage Target Deadband

This paragraph specifies the algorithm used to decide the change of a tap, when voltage is
outside the voltage deadband.
The target voltage that must be reached is defined by:
Target Voltage = [Selected Target Voltage + Voltage Compounding] * Voltage SetPoint,
where:
• Selected Target Voltage is one of the five pre-programmed Selected Target Voltages.
(when the AVR starts up, the selected target voltage is a target voltage pre-set in
database)
• Voltage Compounding is line drop compensation, it allows to maintain the nominal

voltage at a remote location of the actual measurement point.
• Voltage SetPoint is a coefficient typically comprised between 0.9 and 1.

There are two methods for line drop compensation. According to the customer, one is
defined during the configuration phase:
1. First line drop compensation method:
Voltage Compounding = Actual busbar load (MW ) * Resistive multiplier
+ Actual busbar load (MVAR ) * Reactive multiplier.
2. Second line drop compensation method:
Alternatively the line drop compensation can also be achieved by using the resistance R and
reactance X of the connection circuit as compounding settings. In this method, the measured
voltage is adjusted such that:
V = √ ((V0 – A)² + B²)
Where
V0 actual measured value
V adjusted measured value. V is used to determine the tapping action by comparing
with the target voltage
A = (R*P + X*Q) / V0
B = (X*P - R*Q) / V0
P active power, Q reactive power,
R et X are the resistance and the reactance of the connection circuit for the resistive
and reactive compounding respectively.
Voltage deadband
The Voltage Deadband is expressed as a percentage of the nominal voltage. By
configuration, coefficients are set to adjust the deadband with the number of transformers in
a group.
Voltage deadband = Initial Voltage deadband * coefficient.
Two examples:
case 1 case 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 * Nominal Voltage

OR
• Voltage < Target Voltage - Voltage Deadband * Nominal Voltage for more than a time-
out T1.
Dual deadbands are used to ensure that the post tapping voltage is sufficiently closed to the
selected target voltage. Deadband 1 is used to initiate tapping and deadband 2 is used to
end tapping.
7.1.4.5.3 Timeouts
Moving the taps of the transformers is achieved with respect of some time-outs.
The "first 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 is drifting in and out of the deadbands, the system counts up to T1 when
the voltage is outside of the deadband1. If before T1 is reached the voltage returns within the
deadband2 then the system counts down to 0.
When the voltage is crossing from one side of the deadband1 to the other side, the count is
reset to zero and the new time delay is T1.
After an auto-recloser operation , the group (or the two new groups) keeps the same AVR
modes; however the count is reset to zero and the new time delay is T1.
T1 is adjustable between 15 and 120 seconds in 0,1 second increments.
T2 is adjustable between 0 and 120 seconds in 0,1 second increments.
Moreover, the AVR shall not drive the system voltage by more than a pre-set rate (defined in
database). This rate, “maximum voltage change rate” is settable between 0,1kV/min and
5kV/min in 0,1kV/min increment.
If a Tapping is required after a previous tap control:
• Ti is the date when the previous tapping was performed
• T is the current date
• MVCR is the Max voltage 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), tapping is performed as soon as the following are TRUE:
• T > Ti + T2
• V < Vi + MVCR * (T - Ti)

For a Tap Down (to decrease voltage), tapping is performed as soon as the following are
TRUE:
• T > Ti + T2
• V > Vi - MVCR * (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 50: 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 greater than the maximum rate. It is performed when the current voltage
change rate becomes lower than the maximum rate.
It is possible to choose by configuration a T1 delay as a fixed delay or as an inverse time
delay.
When inverse initial time delay is selected:
DV = | actual group voltage - deadband limit voltage |
• IF DV < 1% target voltage THEN initial tap time delay = T1.
• IF 1% <= DV < 10% target voltage THEN initial tap time delay = T1/DV.
• IF DV >= 10% target voltage THEN initial tap time delay = T1/10.
When a transformer belongs to a group of several transformers, the time out is applied to the
group. Two different groups have separate time out 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 is crossing from one side of the deadband to the other side.
7.1.4.5.4 Single transformer management
If a group is restricted to one transformer and is in automatic control mode, raise and lower
commands are issued if the voltage exceeds the voltage deadband with respect of the time
outs.
7.1.4.5.5 Multiple transformers management

If a group is composed of 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 methods depending on the substation constraint and customer
requirement. By configuration one of these three methods has to be chosen.
For the three following methods, if all the transformer tap-changers reach their end stop
while tapping is required to go further, then the substation alarm "target not achievable" is
generated. This alarm disappears when the problem is cleared.
First method: “TAP”
In this case, assumption is made that:
• the primary voltages of the transformers are identical
• the number of taps and tapping ranges of the transformers are identical
Then the maximum tap span between the transformers will be 1 and there will be a balanced
control of them when the voltage is changing.
Calculation is as follows:
1. if voltage is out of the deadband,
1.1. and under the deadband -> action is raise on the transformer with the lowest
Tap
1.2. and upper the deadband -> action is lower on the transformer with the highest
Tap
2. if voltage is in the deadband, the system sets the transformer within one tap
Second method: “Transformer ratio”
In this case, assumption is made that the primary voltages of the transformers are identical.
Calculation is as follows:
1. if voltage is out of the deadband,
1.1. and under the deadband -> action is raise on the transformer with the lowest
transformer ratio
1.2. and upper the deadband -> action is lower on the transformer with the highest
transformer ratio
2. if voltage is in the deadband, the system sets the transformer within a percentage of
transformer ratio. This percentage P is calculated for all groups:
P = Maximum (tapping range / (number of taps - 1 ))
Example:
Group with 3 transformers:
• SGT1: 19 taps, tapping 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 method: “circulating current minimisation”
In this case, there is no assumption that the primary voltages of the transformers are
identical.
With a sample example of two transformers:
SGT1 SGT2
I1 I2
Per transformer, we know
• Sn (rating),
• x (Impedance in % on Sbase: e.g.100 MVA),
• U,
• I,
• P,
• Q,
• Current tap
• Unom (nominal secondary voltage)
X (reactance) = x * (Unom)² / Sbase
One transformer can be presented as below:
E
The both transformers can be presented as below:
I
Ic
X1
X2
U
I1 I2
E1 E2
We have
U = E1 - X1*I1 = E2 - X2*I2 => E1-E2 = X1*I1 - X2*I2
I = I1 + I2
E1 - E2 = (X1 + X2 ) * Ic
=> Ic = (X1*I1 - X2*I2) / (X1 + X2)
For each transformer, we have U,I,P,Q (So U1,I1,P1,Q1 and U2,I2,P2,Q2)
We have 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 hughest |ϕ| 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).
TapSpan: tap span for the transformer
NbTap: number of taps for the transformer
Unominal: nominal secondary voltage
∆U1tap = (TapSpan/(NbTap -1)) * Unominal
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.1.4.5.6 Target voltage
When the operator changes a target voltage, the new target voltage is indicated immediately.
The actual target voltage will not be changed by more than the corresponding pre-set value if
the busbar is under automatic control. If the busbar is not under automatic control the new
target voltage is immediately achieved.
7.1.4.5.7 AVR inhibited
AVR is inhibited for the corresponding group while the measured system voltage is less than
a pre-set value or higher than an other pre-set value.
Overcurrent on a transformer will also inhibit the transformer's group.
7.1.4.5.8 Homing
Homing is a facility which 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 when the
mode of this busbar is In automatic control.
Homing is only able if there is at least one transformer connected on the corresponding
busbar and if transformer busbar disconnector is closed and 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.
Homing ceases when the tap changer is faulty and until the operator selects "Clear AVR
faults". If the Tap Changer is still faulty then the transformer remains OUT of automatic
control.
Time out T3 is used for the first tap in the homing mode.
Time out T4 is used between successive taps.
7.1.4.6 Capacity
AVR is able to manage a maximum of:
• 7 transformers,
• 4 transformers in parallel,
• 8 busbars,
• 4 transformers per busbar,
• 2 reactors per transformer,
• 2 voltage levels.
7.1.4.7 List of configurable parameters

General parameters:
• AVR used / or not
• Homing ON / OFF
• Presence of an external ARS / or not
• Initial tap time delay (T1) fixed / or not
• Calculation mode:
− method “TAP”
− method “ transformer ratio”
− method “circulating current minimisation”
• Period of AVR calculation (default value: 1 second)
• Percentage of the Homing deadband (default value: +/-3%)
• Initial tap time delay: T1 (default value: 60 seconds; range 15 to 120)
• Inter tap time delay: T2 (default value: 10 seconds; range 0 to 120)
• Initial tap time delay: T3 (default value: 60 seconds; range 15 to 120)
• Inter tap time delay: T4 (default value: 10 seconds; range 0 to 120)
• Hunting window: T5 (default value: 500 seconds; range 120 to 1800)
• Coefficients for 1, 2, 3 and 4 transformers (default values: 1)

• Maximal number of successive taps in opposite direction for hunting (default value: 4 )
• Overcurrent setting (default value: 140%; range 100 to 200% )
• Percentage of accepted difference between secondary voltages for transformers in the

same group. (default value: +2%)
• Under-voltage: percentage of nominal voltage under which AVR or Homing is inhibited

(default value: 80%)
• Over-voltage: percentage of nominal voltage over which AVR or Homing is inhibited

(default value: 120%)
• Mode group interconnexion: IN and OUT => IN or IN and OUT => OUT
• Mode if bay in local: IN / OUT
• Compounding method: setpoint adjust or voltage adjust

Parameters per busbar:
• Resistive multiplier (default value: 0.01%; range –0,1% to +0,1%)
• Reactive multiplier (default value: 0.01%; range –0,1% to +0,1%)
• SetPoint value (default value: 1; range 0.9 to 1 )
• Priority: 0 to 4
Parameters per transformer:
• AVR tap minimum and maximum value
• AVR transformer rating (default value: 240 MVA)
• AVR transformer impedance on nominal tap on 100 MVA base
• AVR transformer type (autotransformer or double wound)
• AVR tapping range:
− upper value (default value: +20%)
− lower value (default value: -20%)
• Nominal ratio
Parameters per voltage level:
• Target voltage ramping rate (default value: 1.5 kv per minute)

• Max voltage change rate (default value: 0,1 kv per minute)
• voltage deadband1 (default value: +/-1%; range +/-0.5% to +/-5% )
• voltage deadband2 (default value: +/-1%; range +/-0.5% to +/-5% )
• Target voltage 1 (default value: 90% of nominal voltage; range +/- 10% of nominal
voltage)
voltage)
• Target voltage 3 (default value: nominal voltage; range +/- 10% of nominal voltage)
voltage)
voltage)
To maintain a system voltage supply within a given deadband, it is necessary to regulate the
system voltage. The On-Line Tap Changing (OLTC) transformer maintains a stable
secondary voltage by selecting appropriate tapping on the secondary transformer windings.
Selection orders are issued from the Voltage Regulation function that continuously monitors
the transformer.
The motors-driven OLTC received the "Raise" and "Lower" control commands from the
Voltage Regulation module. These orders change the OLTC position and the transformer
voltage value is adapted to the pre-set required voltage level.
7.2 Interlocking: logical equations

In an electrical substation, the switching devices are primarily the followings:
• 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.
The goal of the function of interlocking is to prohibit operating which 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, awashed with substation equations, are generated
by independent software. This software takes in account the topology and some predefined
rules to provide these equations
7.2.1 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 (e. g. system failures, equipment operation modes, ...),
• Limits derived from measured values from the systems analog input boards (CT, VT,
transducers), from other system computers, from protection relays and other IED’s via
communication network.
7.2.2 Outputs
Result of the interlocking equation is transmitted through a system binary output and saved,
locally in RAM, by the function managing interlocking logical equations.
And, a service is available for any task to get the result of the computation.
Thus , the function managing “control of sequence” uses this service to know whether control
can be executed.
Then, a simple transient binary input can be set if defined in configuration. The same SPS is
used for the commands “open” and “ close” of a xPC
7.2.3 Control
No control. An equation is computed each time that one of its input changes of state or of
validity.
7.2.4 Behaviour
7.2.4.1 Principle
In computer, a logical interlocking equation is defined as a sum of product (AB+CDE+F for
example).
7.2.4.1.1 Introduction
Interlocking function uses up to 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, e. g. 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 which controls the switching device.
Local equation is made up of information obtained from its own digital inputs and IEDs
connected to this computer.
Substation interlocking is made up information obtained from its digital inputs and inputs
provided by the communication network from other computers, from bay computers and from
IED’s (protection relays, etc.). Substation interlocking can also be managed by the
topological interlocking function (Refer to Topological interlocking for more details.
7.2.4.1.2 Local interlocking
The local interlocking is done by calculation of a logical equation. It can exist up to one
equation per switching device and per each direction (open and close). If there is no
equation for a switching device for a direction, the corresponding variable is true.
7.2.4.1.3 Substation interlocking
The substation interlocking analyses the position of all switching devices in the substation
and calculates the substation interlocking equation to authorise control of a switching device
according to the mechanical and electrical capabilities of the switching device. If there is no
equation for a switching device for a direction, the corresponding variable is true.
7.2.4.1.4 Validity of information
The interlocking equation does not only use the value of the information but also the validity
of the information (invalid, ...).
Thus the result, saved in RAM, of a logical equation is only TRUE or FALSE, An Interlocking
equation in the INVALID state will be considered as FALSE .
But, the system binary input also generated can be valid (SET or RESET) or invalid.
The evaluation of the result of basic logical function such as NOT, AND or OR is defined as
follows:
NOT
True False
False True
Invalid Invalid
OR True False Invalid

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

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

7.2.4.1.5 Interlocking bypass
Bypass made by key switch
Interlocking can be overridden (interlocking bypass mode). Overriding of interlocking can be
set from the local control point.
During configuration optional overriding of interlocking from any other control point can be
defined according to customer requirements. This includes the possibility of overriding of
interlocking per switching device or per bay or per substation entity basis.
If an interlocking is overridden, the associated variable is true.
Bypass within the control
From any control point, operator can bypass the interlocking check. Bypass is then an
attribute of the control. If bypass is set, the function managing the “control of sequence” does
not use the service giving the current result of the interlocking equations.
7.2.4.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:
• Simple 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
As said before, 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 ofa new state or quality for a data
• Get logical state associated 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 new state of the system binary input representing 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 associated 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.2.5 Limits and performance

Up to 256 operands can be used on a per equation basis.
Up to 256 equations can be defined in a computer.
A datapoint can be used in up to 255 interlocking equations.
7.3 Slow automation: Programmable Logic Control (PLC)

The MiCOM C264/C264C allows the user to configure specific control sequences or
automations (e.g. switching sequences, busbar transfer, load shedding, GIS-pressure
supervision) during the substation configuration phase.
The Programmable Logic Controls (PLC) or Configurable Automations are entered and built
onto a logic development workbench. The real time kernel of the computer runs them.
The solution retained for developing control logic programs in the computer is a Soft Logic
package.
The Soft Logic package Workbench is a host-based software development environment
associated to the System Configurator. It is used to create control logic programs.
It is a full-featured set of tools providing:
• Editing
• Code generation
• Simulation
• Debugging
• Project management
The Soft Logic package supports standard programming languages of the IEC 1131-3:
• Sequential Function Chart, SFC (GRAFCET)
This language can be used with Function Block Diagram (FBD), Ladder Diagram (LD) or
Instruction List (IL) for action and transition descriptions.
• Structured Text, ST
The code generated by the Soft Logic package workbench is uploaded to the computer
target system that runs it.
Control logic
application
code
Soft Logic Target

package hardware
C0019ENa
FIGURE 51: PLC WORKBENCH

7.3.1 Inputs
All the datapoints of the computer can be used as an input of a PLC.
7.3.1.1 Data acquired by the computer

• BI: non filtered change of states are transmitted to PLC kernel
• MEAS
• CT
• Tap position (TPI or SPI)
7.3.1.2 Data managed by the computer

• 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.3.1.3 Acknowledgement of control

A PLC function can manage a control sequence:
• Send control
• Process acknowledgement to the sent control
7.3.2 Outputs
A PLC function can:
• generate a BI, e.g. PLC is considered as source of acquisition of the data point,
• generate a MEAS,
• generate a CT,
• generate a SPI,
• generate a SIG,
• modify quality of a Binary Input defined in the computer: force, suppress or

substitution request,
• modify quality of a MEAS defined in the computer: force, suppress or substitution

request,
• modify quality of a SIG defined in the computer: force, suppress or substitution

request,
• send binary order to computer boards or IED or to another computer,
• send digital setpoints to computer boards or IED or to another computer.
7.3.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.3.4 Behaviour
The computer has a software execution engine designed to interpret the automation
application code according to the cycle described hereafter.
Read inputs
Execute programs
Write outputs
C0345ENa
Basically, the cycle duration depends on the number of I/O to be scanned and the complexity
of the operations to be performed. It will be set during the configuration process.
7.3.4.1 Interfacing with a HMI or a RCP/SCADA

A remotely sited master station can send and receive data to and from the automation
applications of the computer.
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 the computer.
7.3.5 Limits and performances

• 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 runs on one computer, which means a PLC-program cannot be

distributed within the system. However, it is possible to use information obtained by
other computers.
• Routing of the automatism applications to the memory must be carry out according the
memory and hardware design.
• The debugging of the applications must be possible in connecting a local PC on the

front face. The hardware design will take in account this possibility and will separate
out the debugging and the application download.
7.4 Fast automation: Programmable Scheme Logic (PSL)

As automatisms created through ISaGRAF are dependent from the ISaGRAF cycle whose
value is about 50ms in the best case, it is necessary to implement some configurable
automatisms that can be achieved in less than 50ms.
PSL is the solution for implementation of automatism that must be performed as quickly as
possible.
Designed solution is mainly based on mechanism used for the computation of logical
interlocking (refer to §logical interlocking for more details). Indeed, logical gates AND, OR,
NOT, NAND, NOR or a combination of these gates can be processed as a logical equation.
Some other functions (drop-off and pickup timer, bistables) are added to these logic gates.
These automations are event-driven: they are calculated each time an input changes (i.e.
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 case 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 52: EXAMPLE OF PSL

8. USER INTERFACE
This section is described in the chapter Human Interface.
9. RECORDS
Several kinds of records are stored into MiCOM C264/C264C.
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

A waveform recording deals with the storage of measurement and logical information in
order to visualise the electrical network behaviour when electrical event 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 which gives access to samples
• Slow wave form which gives access to RMS values
9.1.2.1 Fast Waveform Recording

The inputs for the fast waveform records are up to 4 CT samples and 4 VT samples, and the
values of the selected digital inputs and outputs. Up to 128 digital channels may be captured.
The choice of selected inputs/outputs is defined in configuration.
The waveform recorder provides up to 8 analogue measurements and up to 128 digital
channels for extraction by a remote device.
A maximum of 480 cycles ( 9,6 seconds at 50 Hz) of measurements samples, with 32
samples per cycle, can be stored, divided in 1, 2, 4 or 8 files saved in flash disk.
A timer channel is also required to provide accurate timing information for each sample. The
delay between each sample is assumed constant over a single cycle.
Number of Files Number of cycles

8 60
4 120
2 240
1 480
The 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)
• 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.
9.1.2.2 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 up to 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
MiCOM C264/C264C stores at maximum 5000 integrated values as follow:
Number of Files Number of integrated values

1 5000
2 2500
5 1000
10 500
20 250
50 100
The integrated value has duration up to one hour. It is defined in configuration.

For analogue, the stored value is the average value during integrated period.
For digital, the stored value depends also on the average:
If average value > x then the stored value is 1 else it is 0, x is defined in configuration and it
is a value between 0.1 and 0.9.
The slow waveform recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of binary inputs (SP, DP, MP, SI or Groups)
• Changes in state of digital outputs
• Measurement threshold violations
• Operator request
• Periodically (i.e. every day at 00h00)

9.1.3 Events
All data change or events declared in MiCOM C264/C264C 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 CMT equipment. They also can be printed.
Events, following MiCOM C264/C264C configuration, may typically contain the MiCOM
C264/C264C description, the date of the event and the time of the event with an accuracy of
1 ms, plus specific information regarding the causes of the events.
The MiCOM C264/C264C under the following circumstances may create events:
• Changes of state of Binary Inputs (SP, DP, MP, SI, Groups)
• Changes of state of Measurements
• Changes of state and value of Tap Position Indications
• Devices Control actions and acknowledgements
• Alarm acknowledgement
The size queue is:
• 200 data for front panel
• 2000 data for CMT
• configurable per slave protocol for SCADA
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 which must absolutely not be
overlooked.
9.2.1.1.2 Types of alarmed data
An alarm can be generated by the following events:
• each Binary Input (SP, DP, MP, SI, IED input, Groups) state
• each Measurement state
• each TPI state or value
• each metering state

associated 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.
Furthermore, an alarm can be associated to a control acknowledgement. In this case, the
alarm is considered as “spurious”.
9.2.1.1.3 Alarm states definition

An alarm is generated by an event (e.g. a particular datapoint in a state defined during the
configuration phase as “to be alarmed”).
While this event is still present (e.g. the previous particular datapoint is still in the same
state) the alarm is “active”.
When this event disappears (e.g. 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 front
panel.
So 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 on a per alarm basis:
• 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 desappears

In this case 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: e.g. « JAMMED » or « TOGGLING » or « OPEN » state (the last
one which has appeared).
By configuration, one of the following behaviour 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 53: 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 54: 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 case «alarmed event disappears (AL-)» means that the
associated data is now in another state which 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 which is flagged to be alarmed with any gravity
level to another state which is also flagged to be alarmed with any gravity level (AL+). In this
case 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 which 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 a SPS (named Global alarm ack)
specially dedicated to a global acknowledgement of alarms.: When this SPS is set to
the SET state all alarms present in the computer are acknowledged. As long as this
SPS remains in the SET state, any new alarm is inserted in the alarm list with the
ACKLOWLEDGED status.
In addition to the Global Alarm Acknowledgement SPS, a Local Alarm
Acknowledgement SPS can be defined on a per C264 basis (i.e. one per 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 (i.e. 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
cases 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 which 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, which allows to clear all “inactive-acknowledged” alarms in a
single operation, will be provided.
Audible alarms
An audible alarm can be associated with the “unacknowledged” state of an alarm. This
facility is configurable on a per alarm basis.
If an alarm is configured “audible” then the sound appears when the alarm is displayed.
The audible alarm is stopped when all audible alarms are acknowledged.
An audible alarm can be associated with the “unacknowledged” state of an alarm. This
facility is configurable on a per alarm basis.
If an alarm is configured as “audible” then the sound appears when the alarm is displayed.
The audible alarm is stopped when all audible alarms are acknowledged.
BLANK PAGE
Hardware C264/EN HW/C40
MiCOM C264/C264C
HARDWARE
CONTENT
2. HARDWARE DESCRIPTION 4
2.1 Concept 4
2.1.1 Components 4
2.1.2 Hardware Overview 5
2.2 MiCOM C264C 6
2.2.1 Hardware presentation 6
2.2.2 Modularity 7
2.2.3 I/O Capabilities 8
2.2.4 Front Back Plane – FBP24x 8
2.2.5 Front Panels 9
2.3 MiCOM C264 11
2.3.1 Hardware presentation 11
2.3.2 Modularity 12
2.3.3 I/O Capabilities 13
2.3.4 Front Back Plane – FBP28x 13
2.3.5 Front Panels 13
2.4 Coding of board address 14
2.5 Modules description 15
2.5.1 Power auxiliary supply and legacy ports board – BIU241 15
2.5.2 Central Processing Unit and base communications board – CPU260 17
2.5.3 Central Processing Unit and base communications board – CPU270 19
2.5.4 Digital Inputs Unit – DIU200 20
2.5.7 Digital Outputs Unit – DOU200 23
2.5.8 Circuit breaker Control Unit - CCU200 24
2.5.9 Analogue Input Unit – AIU201 25
2.5.12 Transducer less Measurements Unit – TMU200/TMU220 28
2.5.13 Ethernet Switch Unit – SWU200/SWU202 29
2.5.14 Ethernet Redundant Switch Unit – SWR202/SWR212, SWR204/SWR214 31
2.5.15 Dual Homing Ethernet Switch Unit – SWD202/SWD204 37
2.5.16 Extended communication Unit – ECU200 44
2.5.17 Extended communication Unit – ECU201 45
2.6 Hardware tropicalisation 45
C264/EN HW/C40 Hardware
BLANK PAGE

This document is a chapter of MiCOM C264/C264C documentation binders. It describes the
product hardware which is not the commissioning chapter.
2. HARDWARE DESCRIPTION
2.1 Concept
2.1.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 computer
redundancy and 2 insulated RS485/RS232 interface
• CPU260 (also named CPU2) or CPU270 (also named CPU3): Central Processing Unit
and communications board based on PowerPC processor
• DSP200: Digital Signal Processing board is the processor board for CT VT calculation.
It is the CPU200 daughter board
• FBP28x: Front BackPlane: bus for 80TE case
• FBP24x: Front BackPlane: bus for 40TE case
• DIU200: Digital Inputs Unit each with 16 digital inputs
• DIU210: Digital Inputs Unit each with 16 digital inputs with current-peak and voltages
from 24V to 220V
• DIU220: Digital Inputs Unit each with 16 digital inputs for voltages 48/60V and
110/125V
• DOU200: Digital Outputs Unit each with 10 digital outputs for alarms
• CCU200: Circuit breaker Control Unit each with 8 digital inputs and 4 digital outputs
• AIU201: Analogue Input Unit each with 4 analogue inputs direct current or voltage
• AIU210/AIU211: Analogue Input Unit each with 8 analogue inputs direct current
• TMU200 (TMU220): Transducerless Measurements Unit board for direct CT/VT

measuring acquisition with 4 CT and 4 VT ( 5 VT for TMU220)
• 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 redundant 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 insulated RS232 into
optical signal
• ECU201: Extended Communication Unit board to convert non insulated RS232 into
insulated RS485 signal
• GHU201 (for C264) or GHU200 (for C264C): Graphical Human machine interface
Unit: Front Panel including 17 LEDs (13 free 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 MMI management
• GHU211 (for C264) or GHU210 (for C264C): Front Panel including 17 LEDs (12 free
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.2 Hardware Overview
Watchdog
FBP280 BIU241
or FBP242 (1) Redundancy
RS232 or RS485 or RS422
COM 1 / COM 2
RS232 or RS485
Power Supply
Electrical RJ45 link
CPU260 Ethernet Optical link ( CPU260 ) or Electrical link (CPU270)

or
CPU270
COM 1 / COM 2 RS232
(1) ECU20x RS485
RS422
DSP 260 IRIG- B RS232 ECU20x Optical
OR
GHU200 or GHU201
OR
GHU210 or GHU211
OR
GHU220 or GHU221 GHU20x or GHU21x
SWU200 Optical 1 / Optical 2

(up to 1)
Electrical 1 to 4
Mandatory
SWR200 Optical 1 / Optical 2
Optional
(up to 1)
or
SWD200
Electrical 1 to 4
(up to 1)
AIU201 or AIU210 or AIU211

(up to 6)
N digital inputs
( N= 4 for AIU201, N=8 for AIU210, AIU211)
DOU200
(up to 15)
10 digital outputs
CCU200
8 digital inputs
(up to 15)
4 digital outputs
DIU200 or DIU210 or DIU220

(up to 15)
16 digital inputs
TMU200 or TMU220
4 current inputs
(up to 1)
N voltage inputs
( N = 4 for TMU200, N = 5 for TMU220) C0117 ENh
FIGURE 1: HARDWARE OVERVIEW

2.2 MiCOM C264C

2.2.1 Hardware presentation
The MiCOM C264C mechanical rack has the following features:
• Height: 4 U
• Width: 40 TE
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.2 Modularity
The MiCOM C264C is available in two case versions allowing flexibility and scalability in the
use of the I/O modules:
FIGURE 4: MiCOM C264C – REAR PANEL OVERVIEW WITH CT/VT BOARD

FIGURE 5: MiCOM C264C – REAR PANEL OVERVIEW WITHOUT CT/VT BOARD

2.2.3 I/O Capabilities
Inside the Case with CT/VT, there are 4 available slots for I/O boards (DIU200, DIU210,
DIU220, AIU201, AIU210, AIU211, DOU200 or CCU200) or switch boards (SWU20x or
SWR2xx or SWD2xx).
Inside the Case without CT/VT, there are 6 available slots for I/O boards (DIU200, DIU210,
SWR2xx or SWD2xx).
2.2.4 Front Back Plane – FBP24x
The FBP242 board is the back plane used for the MiCOM C264C equipped with the
CPU260.
FIGURE 6: MiCOM C264C – FBP242 BOARD

The FBP243 board is the back plane used for the MiCOM C264C equipped with the
CPU270.
FIGURE 6BIS: MiCOM C264C – FBP243 BOARD

2.2.5 Front Panels

2.2.5.1 GHU200
The GHU200 is the front panel with LCD and LEDs used for the MiCOM C264C:
• 17 LEDs (13 free configurable)
• 7 pushbuttons (L/R, Open, Close, etc)
• a keypad at the front plate for local MMI management with 5 pushbuttons
• a LCD (resolution of 128 x 128 pixels /16 lines of 21 characters each)
FIGURE 7: MiCOM C264C – GHU200 BOARD

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

2.2.5.3 GHU220
The GHU220 is the front panel used for the MiCOM C264C. This includes only a RJ11
coupler in order to connect a remote GHU20x or GHU21x.

2.3 MiCOM C264

2.3.1 Hardware presentation
The MiCOM C264 mechanical rack has the following features:
• Height: 4 U
• Width: 80 TE
Dimensions of this rack are in the figure bellow:
FIGURE 10: 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 11: FIXATION HOLES POSITION FOR C264

2.3.2 Modularity
The MiCOM C264 is available in two case versions allowing flexibility and scalability in the
use of the I/O modules:
FIGURE 12: MiCOM C264 – REAR PANEL OVERVIEW WITH CT/VTCONNECTOR
FIGURE 13: MiCOM C264 – REAR PANEL OVERVIEW WITHOUT CT/VT CONNECTOR
2.3.3 I/O Capabilities

Inside the Case with CT/VT, there are 14 available slots for I/O boards (DIU200, DIU210,
SWR2xx or SWD2xx).
Inside the Case without CT VT, there are 15 available slots for I/O boards (DIU200, DIU210,
SWR2xx or SWD2xx).
2.3.4 Front Back Plane – FBP28x
The FBP280 board is the back plane used for the MiCOM C264 equipped with the CPU260.
FIGURE 14: MiCOM C264 – FBP280 BOARD
The FBP283 board is the back plane used for the MiCOM C264 equipped with the CPU270.
FIGURE 14BIS: MiCOM C264 – FBP283 BOARD

2.3.5 Front Panels
2.3.5.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 MMI management with 5 pushbuttons
• a LCD (resolution of 128 x 128 pixels /16 lines of 21 characters each)
FIGURE 15: MiCOM C264 – GHU201 BOARD

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

2.3.5.3 GHU221
The GHU221 is the front panel used for the MiCOM C264. This includes only a RJ11 coupler
in order to connect a remote GHU20x or GHU21x.
2.4 Coding of board address

Same rule is applicable to all I/O boards (DIU200, DIU210, DIU220, AIU201, AIU210,
AIU211, DOU200, and CCU200):
Binary coding on 4 jumpers top down (From 0 to 15)
− 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
2.5 Modules description
2.5.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 insulated interfaces (Port 1: RS232 or RS485, Port 2: RS232, RS422 or RS485)

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

The BIU241 board provides two insulated serial links.
This following figure shows how to configure the serial links.
C0033ENa
FIGURE 19: ZOOM ON BIU JUMPERS

2.5.1.1 Configurable communication Port 1 - RS232/485
The communication link characteristics are:
• full duplex serial protocol
• 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 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.5.1.2 Configurable communication Port 2 - RS232/422/485
The communication link characteristics are:
• full duplex serial protocol
• 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
resistor has to be used).
2.5.2 Central Processing Unit and base communications board – CPU260

The CPU260 board is based on a PowerPC processor including the 10/100BaseT Ethernet
communication.
Optionally, this board includes the following capabilities:
• One 100BaseF Ethernet port (ST connector)
• Two non insulated 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)
• One IRIG-B input
• One daughter board (DSP260) for CT/VT management

This 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 20: MiCOM C264 - CPU260 BOARD

FIGURE 21: MiCOM C264 – DSP200 DAUGHTER BOARD ON CPU260

2.5.3 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 insulated 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)
• One IRIG-B input
• One daughter board (DSP260) for CT/VT management

This board is interfaced with all I/O boards and the front panel.
CPU270 has the following key features:
• 32-bits Power PC-based microprocessor (MPC8270VR) clocked at 266 MHz;
• 128 Mbytes SDRAM
• 64 Mbytes Flash memory
• 256 Kbytes static memory SRAM
• Calendar saved
FIGURE 22: MiCOM C264 - CPU270 BOARD

2.5.4 Digital Inputs Unit – DIU200

The Digital Input module provides 16 optically insulated digital inputs.
The capabilities of the DIU200 boards are:
• 16 optically insulated digital inputs
• 1 negative common contact for 2 inputs
• Protection against reversal polarity
• The digital inputs can be used for single or double status, pulse or digital
measurement input on the same module.
FIGURE 23: MiCOM C264 - DIU200 BOARD


• 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
FIGURE 24: MiCOM C264 - DIU210 BOARD

Current peak response curve:
35
30
25
Current (mA)
20
15
10
0
0 50 100 150 200 250 300
Tension (V)
C0159ENa

• 1 positive common contact for 2 inputs
INPUT NOMINAL VOLTAGES: 48/60VDC OR 110/125 VDC

2.5.7 Digital Outputs Unit – DOU200

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

A self-monitoring device for the output control chain is provided (address check, state
monitoring)
The +5V voltage is monitored to avoid issuing inadvertent controls.
The digital outputs can be configured in single or double remote control or set point outputs
on the same module.
FIGURE 25: MiCOM C264 - DOU200 BOARD

2.5.8 Circuit breaker Control Unit - CCU200

The Circuit breaker Control Unit (CCU200) board provides 8 digital inputs (8 DI) and 4
double pole outputs (4 DO) using integrated relays.
The CCU200 provides 8 optically insulated digital inputs.
The digital input (DI) capabilities of the CCU200 boards are:
• 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 inadvertent controls.
The digital outputs can be configured in double remote signalling only.
FIGURE 26: MiCOM C264 - CCU200 BOARD

2.5.9 Analogue Input Unit – AIU201

The Analogue input module (AIU201) has 4 independent analogue inputs. Each AI can be
configured in voltage or current range individually between.
FIGURE 27: MiCOM C264 - AIU201 BOARD


The Analogue input modules AIU210 has 8 analogue inputs ( 1 negative common for 2
inputs). Each AI can be configured in the current range.


The Analogue input module (AIU211) has 8 isolated analogue inputs. Each AI can be
configured in the current range.

2.5.12 Transducer less Measurements Unit – TMU200/TMU220

The transducers less 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 30: MiCOM C264 – TMU200 BOARD

2.5.13 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 31: MiCOM C264 – SWU200 BOARD

Some 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 Enable less aggressive back-off Open
back-off
W4 Max length is 1536 byte Enable enforce the max frame length for Open
VLAN is 1522
W5 Enable half duplex back Disable half duplex back pressure Open
pressure
W6 Continue sending frame Enable to drop frame after 16 collisions Open
regardless of number of
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 Enable equal amount of buffers per port Open
buffers on a single 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.5.14 Ethernet Redundant Switch Unit – SWR202/SWR212, SWR204/SWR214

These boards are Ethernet switches with 4 electrical links and 2 optical links for a redunded
ring.
The SWR21x switches are SNMP managed
The SWR202/SWR212 models hav a Multi-mode optical interface.
The SWR204/SWR214 models have a Single mode (mono-mode) optical interface.
FIGURE 32: MiCOM C264 – SWR202 BOARD
FIGURE 33: MiCOM C264 – SWR204 BOARD – WITH SC CONNECTOR

FIGURE 34: MiCOM C264 – SWR212 BOARD
L1 L2
Fx1
Rp
J1
J3 Es
Rs
L5 L6 L7 L8 J2
L3 L4 Ep
J6-1
L9 L10 L11 L12 J6-4 1_
J7-1
S4 2_
J4
J7-7
3_
J9
J8-1
L13 L14 L15 L16 4_
J8-6
J5
L17 L18 L19 L20 C0120ENa

Factory
N° Open Closed
setting
S4 Open
J7-1 Board address bit 1 = 1 Board address bit 1 = 0 Close
Address of the board:

Each board on the ring has a specific address. Each address must be single and included
between 1 and 127.
The address is equal to the sum of the « open bits ».
At the beginning address = 0
If J7-1 = open address = address + 1 if not address = address + 0
Example:
Address = 0
J7-1 = open address = address + 1
J7-3 = close address = address + 0
Address = 11
OPEN CLOSE
Internal LED:
Some LED are used to indicate the state of the links.
The table below indicates the function of each LED:
LED
FUNCTION DESCRIPTION
number
L1 Receive RpEs
L2 Link RpEs
L3 Receive RsEp
L4 Link RsEp
L5 Link and activity port 1 Off: no connection
Green: link
Green + blink: link + activity
L6 Link and activity port 2 «
L9 Speed port 1 Off: 10Mbps Green: 100Mbps
L10 Speed port 2 «
L11 Speed port 3 «
L12 Speed port 4 «
L13 Address board bit 0 Only the first 4 bits are visualized
L14 Address board bit 1 «
L17 Number of repeter detected on the ring bit 0 Only the first 4 bits are visualized
L18 Number of repeter detected on the ring bit 1 «
Fault signal output:

The optical ring is monitored. If one link comes down the default is announced by the
contacts (250V/5A):
1 Default Rp-Es
2 Common
1 2 3 3 Default Rs-Ep
Close if default
C0121ENa
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
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 SWR202, the connector type for the multi mode fibre is ST.
On the SWR204 (Ref 2071021 A02 – up to Index B), the connector type for the single mode
fibre is ST.
On the SWR204 (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
fibres
SWR200 SWR200
1
SWR200 SWR200
Patch Patch
Panel Panel
SWR200 SWR200
C0123ENa
Fibre type Multi mode (SWR202) Single mode (SWR204)

Wavelengh:1310nm
62,5/125 micron 9/125 micron
Power coupled into - 19 dBm - 15 dBm
fiber
sensitivity - 31 dBm - 34 dBm
Example 1: between two repeaters
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 repeaters via patch panel
Patch loss (2) 2 dB 1 dB
Allowed link attenuation -0,8 dB 8,2 dB
Maximum range 0 20 km
The values given above are only approximate ones. Always use cable and connector losses
as specified by the manufacturer.
2.5.15 Dual Homing Ethernet Switch Unit – SWD202/SWD204

These boards are Ethernet switches with 4 electrical links and 2 optical links for a dual
homing solution.
The SWD202 model has a multi-mode optical interface.
The SWD204 model has a single mode (mono-mode) optical interface.
FIGURE 35: MiCOM C264 – SWD202 BOARD – ST CONNECTOR
FIGURE 36: MiCOM C264 – SWD204 BOARD – WITH SC CONNECTOR

L1 L2
Fx1
R Link A
J1
J3 E Link A
R Link B
L5 L6 L7 L8 J2
L3 L4 E Link B
J6-1
L9 L10 L11 L12 J6-4 1_
J7-1
S4 2_
J4
J7-7
3_
J9
J8-1
L13 L14 L15 L16 4_
J8-6
J5
L17 L18 L19 L20 C0296ENa

Factory
N° Open Closed
setting
S4 Open
Address of the board:

between 1 and 127.
Example:
Address = 0
Address = 11
OPEN CLOSE
Internal LED:
Some LED are used to indicate the state of the links.
LED
FUNCTION DESCRIPTION
number
L1 Receive Link A
L2 Status Link A
L3 Receive Link B
L4 Status Link B
L5 Link and activity port 1 Off: no connection
Green: link
L9 Speed port 1 Off: 10Mbps Green: 100Mbps
L10 Speed port 2 «
L11 Speed port 3 «
L12 Speed port 4 «
L13 Number of repeaters detected on the ring bit 0 Only the first 4 bits are visualized
L14 Number of repeaters detected on the ring bit 1 «
L17 Number of repeaters detected on the ring bit 4 Only the first 4 bits are visualized
Fault signal output:

Dual homing links are monitored. If one link comes down the default is announced by the
contacts (250V/5A):
1 Default Link A
2 common
1 2 3 3 Default Link B
Close if default
C0297ENa
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
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 SWD202, the connector type for the multi mode fibre is ST.
On the SWD204 (Ref 2071355 A02 – up to index Z), the connector type for the single mode
fibre is ST.
On the SWD204 (Ref 2071355 A02 – from index A 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
fibres.
SWR200 SWR200
1
SWR200 SWR200
Patch Patch
Panel Panel
SWR200 SWR200
C0123ENa
Fibre type Multi mode (SWD202) Single mode (SWD204)

Wavelengh:1310nm
62,5/125 micron 9/125 micron
Power coupled into - 19 dBm - 15 dBm
fiber
sensitivity - 31 dBm - 34 dBm
Example 1: between two repeaters
Allowed link attenuation 6,4 dB 13,4 dB
Maximum range 6,4 km 33 km
Example 2: between two repeaters via patch panel
Patch loss (2) 2 dB 1 dB
Allowed link attenuation -0,8 dB 8,2 dB
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 SWD20x
Rp LINK A
Rp
LINK A
Es
Es
SWD20x SWD20x
Rs
Rs LINK B
LINK B Ep
Ep
C0298ENa
Between more than 2 Dual Homing SWD20x
Rp LINK A
Rp
LINK A
Es
Es
SWD20x SWD20x
Rs
Rs LINK B
LINK B Ep
Ep
Rp Rp
LINK A LINK A
Es Es
SWD20x SWD20x
Rs Rs
LINK B LINK B
Ep Ep
C0299ENa
2.5.16 Extended communication Unit – ECU200

This is an additional module plugged on DB9 connector of the CPU board. This module
converts non-insulated RS232 into optical signal.
There is a jumper onto ECU200.
When the jumper is set, light is sent for the “1” level.
When the jumper is not set, light is sent for the “0” level.
For IEC870-5-103 standard, there is no jumper. Otherwise, set the jumper.
FIGURE 37: MiCOM C264 – ECU200 MODULE

Optical characteristics:
• Connector type: ST
• Wavelength: 820 nm
• Recommended Fibre cable ; 62,5/125 micron

2.5.17 Extended communication Unit – ECU201

This is an additional module plugged on DB9 connector of the CPU board. This module
converts non-insulated RS232 into insulated RS485/RS422.
There is a jumper onto ECU201.
RS422 conversion: Set the jumper.
RS485 conversion: no jumper.
The indication on the module is as follows:
TA (+)
TB (-)
Ground
RA (+)
RB (-)
In RS422 Mode, TA (+), TB(-), RA (+) and RA (-) are used.
In RS485 Mode, only TA (+), TB (-)- are used.
FIGURE 38: MiCOM C264 – ECU201 MODULE

2.6 Hardware tropicalisation
In option, the MiCOM C264/C264C hardware is available in a tropicalised version.
In this case, each board is coated with a dedicated varnish.
BLANK PAGE
Connections C264/EN CO/C40
MiCOM C264/C264C
CONNECTIONS
CONTENT
2. CONNECTOR BLOCKS 4
2.1 I/O Connector Block 4
2.2 CT/VT Connector Block 5
2.3 Serial communications connections 6
2.4 Optical communications connections 7
2.5 Ethernet-based communications connections 8
3. CONNECTION OF THE PROTECTIVE CONDUCTOR (EARTH) 9

3.1 Earthing 9
3.2 Cable fitting 9
4. CONNECTION DIAGRAMS FOR EACH I/O BOARDS 12

4.1 Power auxiliary supply and legacy ports board – BIU241 12
4.1.1 Connector description 12
4.1.2 Block diagram 13
4.1.3 BIU wiring for redundant C264 14
4.2 Central Processing Unit – CPU260/CPU270 15
4.3 Digital Inputs module – DIU200 17
4.6 Digital Outputs module – DOU200 23
4.7 Circuit breaker Control Unit - CCU200 25
4.8 Analogue Input module – AIU201 27
4.9 Analogue Input module – AIU210/AIU211 29
C264/EN CO/C40 Connections
4.10 Transducerless Measurements Unit module –TMU200 33

4.11 Transducerless Measurements Unit module –TMU220 35
4.12 Ethernet Switch Unit - SWU200/SWU202 37
4.12.1 Ethernet connectors description 37
4.12.2 Fault signal connector description 37
4.13 Ethernet Redundant Switch Unit - SWR202/SWR212, SWR204/SWR214 38
4.14 Dual Homing Ethernet Switch Unit - SWD202/SWD212, SWD204/SWD214 39
4.15 Front panel 40

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-way 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 insulated category 5 (FTP: Foil Twisted Pair) or insulated (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 insulated 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 GND - Port 1
14 RS232: TxD RS485: A - Port 1
15 GND - 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 - -
9
10
11 RS232/
12 RXD / TB RS485 Serial
link 1
13 SG
14 TXD / TA
#
15
SG
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 -
-
C0050 ENe
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 (+)
Redundancy output contact 3 ------> 7 Redundancy input: 1+
relay 1
(Closed when “Active”,
Open when “Standby”)
Redundancy input: 1+ 7 <------ 3 Redundancy output contact
relay 1
(Closed when “Active”
Open when “Standby”)
Redundancy input - common 8 (-) 8 Redundancy input - common
1 & 2 (-) 1 & 2 (-)
Redundancy input: - 2+ 9 <------ 1 Redundancy output contact
relay 2
(Open on C264 Failure)
4.2 Central Processing Unit – CPU260/CPU270

In base, this board includes the 10/100BaseT Ethernet interface (RJ45 connector).
This board includes:
• The IRIG-B interface ( standard NF S 87-500, May 1987) with the following
characteristics:
− interface: BNC plug
− modulated amplitude, 1 kHz carrier signal
− time-of-year code: BCD
− compatible with IRIG B122 code
• Two non-insulated RS232 interfaces (DB9 male connector)

The external modules ECU200/ECU201 convert non-insulated RS232 into optical
link/insulated RS485 or RS422.
The DB9 connectors description:
1 CD
2 RX
3 TX
4 5V ( for ECU20x supply)
5 ground
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 11: OPTIONAL LEGACY PORTS (PORTS N°3 / N°4) - DESCRIPTION

The ECU201 module has a 5 wires female connector.
1 TA (+)
2 TB (-)
3 Ground
4 RA (+)
5 RB (-)
TABLE 5: ECU201 - DESCRIPTION

For RS422 connection: TA(+), TB(-), RA(+), RB(-) are used. Jumper S1 must be set.
For RS485 connection: only TA(+) and TB(-), are used. Jumper S1 must not be set.
The ECU200 module has 2 optical fibre connectors (ST type):
• TX: optical emitter
• RX: optical receiver

4.3 Digital Inputs module – DIU200

The Digital Input module (DIU200) provides 16 optically insulated digital inputs (with 1
common for 2DI).
4.3.1 Block diagram
D igital Input U nit DIU200

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

NOTE: Different types of DIU200 boards exists 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-way 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 6: DIU200 BOARD - CONNECTOR DESCRIPTION


The Digital Input module (DIU210) provides 16 optically insulated 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.
Block diagram
Digital Input Unit DIU 210

board
PIN Signal inputs
V IN V IN
1
DI 1 DI 2
c om c om
2
3
4 V IN V IN
DI 3 DI 4
c om c om
5
6
7 V IN V IN
DI 5 DI 6
c om c om
8
9
10 V IN V IN
DI 7 DI 8
c om c om
11
12
V IN V IN
13 DI 9 DI 10
c om c om
14
15
V IN V IN
16
DI 11 DI 12
c om c om
17
18
19 V IN V IN
DI 13 DI 14
c om c om
20
21
22 V IN V IN
DI 15 DI 16
c om c om
23
24
C0056 ENd

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

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


The Digital Input module (DIU220) provides 16 optically insulated digital inputs with one
common for two DI. This common links the positive inputs of the two opto-couplers).
4.5.1 Block diagram
Digital Input Unit DIU 220

board
PIN
+ +
1 DI 1 -
DI 2
-
2
3
+ +
4 DI 3 -
DI 4
-
5
6
+ +
7 DI 5 -
DI 6
-
8
9
+ +
10 DI 7 -
DI 8
-
11
12
+ +
13 DI 9 -
DI 10
-
14
15
+ +
16 DI 11 -
DI 12
-
17
18
+ +
19 DI 13 -
DI 14
-
20
21
+ +
22 DI 15 -
DI 16
-
23
24
C0415ENa

NOTE: Two different types of DIU220 boards exists depending on the input
voltage range so before connection, a special attention is to be paid
about the version of the board:

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-

4.6 Digital Outputs module – DOU200

The Digital Outputs Unit (DOU200) board provides 10 outputs (10 DO) using relays.
4.6.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 15: DOU200 BOARD – BLOCK DIAGRAM


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

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

4.7 Circuit breaker Control Unit - CCU200

The Circuit breaker Control Unit (CCU200) board provides 8 digital inputs (8 DI with one
common for 2DI) and 4 double pole outputs (4 DO) using integrated relays.
4.7.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 16: CCU200 BOARD – BLOCK DIAGRAM

NOTE: Different types of CCU200 boards exist depending on the input
voltage range so before connection, a special attention is to be paid
about the version of the board:
- version A01 for 24VDC,
- version A04 for 220 VDC

The CCU200 board is equipped with a 24-way 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 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 10: CCU200 BOARD - CONNECTOR DESCRIPTION

4.8 Analogue Input module – AIU201

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

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


The AIU201 board is equipped with a 24-way 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.9 Analogue Input module – AIU210/AIU211

The Analogue input module AIU210 provides 8 Analogue inputs (8AI) with one common
point (-) for 2 inputs.
The Analogue input module AIU211 provides 8 Isolated Analogue inputs (8AI).
The AIU210/AIU211 boards are equipped with a 24-way 5.08 mm pitch connector.
AIU210 block diagram:
Analogue Input U nit AIU210

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

WARNING: WITH AIU210 IN ORDER TO ENSURE THE MEASUREMENT
CHARACTERISTICS AND PRECISION, THE EXTERNAL CURRENT
SOURCE ARE TO BE FULLY INDEPENDENT OR AS A MINIMUM, THEY
ARE TO BE WIRED TO TAKE CARE OF THE AIU210 INPUT COMMON
POINTS(-).
AIU211 Block diagram:
Analogue Input Unit AIU 211

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


Pin N°. Signal

1 Analogue Input 5+ (current)
2 Common Analogue Input 1/5
5 Insulated Ground 1( not wired)
6 Ground
11 Insulated Ground 2 ( not wired)
12 Ground
18 Ground
24 Ground

Pin N°. Signal

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

4.10 Transducerless Measurements Unit module –TMU200

The Transducerless Measurements Unit module (TMU200) provides 4 transducerless
voltage inputs (VT) and 4 transducerless current inputs (CT).
4.10.1 Block diagram
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 20: CT/VT 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
22 Voltage Input – U2
23 Voltage Input – V1
24 Voltage Input – V2
25 Voltage Input – W1
26 Voltage Input – W2
27 Voltage Input – N1
28 Voltage Input – N2
TABLE 14: TMU200 BOARD - CONNECTOR DESCRIPTION

4.11 Transducerless Measurements Unit module –TMU220

The Transducerless Measurements Unit module (TMU220) provides 5 transducerless
voltage inputs (VT) and 4 transducerless current inputs (CT).
4.11.1 Block diagram
Transducerless 1A Transducerless 5A
Current and Voltage TMU 220 Current and Voltage TMU 220
Unit board Unit board
4 Transducerless 4 Transducerless
PIN PIN
current inputs current inputs
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
X1 X1
19 20 X2 19 20 X2
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
5 Transducerless 5 Transducerless
voltage inputs voltage inputs
C0060 ENb_modif
FIGURE 21: CT/VT BOARD – BLOCK DIAGRAM


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

Wave form:
Electrical Measure type in Measure type in
Pin N°. Signal Related
Signal PACIS PACIS
channel
Configurator Configurator
1 Current Input 5A - N1 IBusbar1 5A - CI#3
Ibusbar RMS 1 Ibusbar RMS 1
2 Current Input 5A – N2 IBusbar1 5A + value of the value of the
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 - CI#2
6 Current Input 5A – C2 IC 5A + IC, RMS value of IC, RMS value of
the current phase the current phase
7 Current Input 1A – C1 IC 1A - C C
8 Current Input 1A – C2 IC 1A +
9 Current Input 5A – B1 IB 5A - CI#1
10 Current Input 5A – B2 IB 5A + IB, RMS value of IB, RMS value of
11 Current Input 1A – B1 IB 1A - B B
12 Current Input 1A – B2 IB 1A +
13 Current Input 5A – A1 IA 5A - CI#0
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 VI#4
value of the value of the
20 Voltage Input – X2 busbar voltage busbar voltage
U Busbar2 + phase phase
21 Voltage Input – U1 UA - VAN, RMS value of VAB, RMS value VI#0
the voltage phase of the voltage
22 Voltage Input – U2 UA + A phase AB
23 Voltage Input – V1 UB - VBN, RMS value of VBC, RMS value VI#1
the voltage phase of the voltage
24 Voltage Input – V2 UB + B phase BC
25 Voltage Input – W1 UC - VCN, RMS value VCA, RMS value VI#2
of the voltage of the voltage
26 Voltage Input – W2 UC+ phase C phase CA
27 Voltage Input – N1 U Busbar1 - Vbusbar RMS 1 Vbusbar RMS 1 VI#3
value of the value of the
28 Voltage Input – N2 busbar voltage busbar voltage
U Busbar1 + phase phase
TABLE 15: TMU220 BOARD - CONNECTOR DESCRIPTION

4.12 Ethernet Switch Unit - SWU200/SWU202

The SWU200 board provides four electrical links.
The SWU202 board provides four electrical links and two optical links.
4.12.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.12.2 Fault signal connector description
These boards are equipped with a 3 pin connector block to deliver a communication fault
signal.
1 Open
2 Common
1 2 3 3 Close
Close if default
C0119ENa
Wiring recommendation:
Due to the proximity of the port 4 Ethernet connector, it is strongly recommended that the
“Fault signal connector” connections are visually checked before any hand manipulation of
the Ethernet connectors.
Particular attention is to be paid during the wiring phase, not to damage the cable’s isolation.
FIGURE 22: SWITCHES: PORT 4 ETHERNET AND FAULT SIGNAL CONNECTORS

4.13 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.14 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.15 Front panel

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

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

MiCOM C264C Front panel:
RS 232 port: This serial port

is dedicated to a PC for
Tunnelling.
C0062ENc
FIGURE 24: MICOM C264C FRONT PANEL

BLANK PAGE
MiCOM C264/C264C
INSTALLATION
CONTENT
2. REQUIREMENT 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 Tools installation on the PC 10
7.1.1 Recommendation for the PC performances 10
7.1.2 Installation on the PC 10
7.2 Connection between the PC and C264 16
7.2.1 Without Ethernet Switch 16
7.2.2 With Ethernet Switch 16
7.3 Settings to enter 17
7.4 Input new settings 17
7.5 C264 Firmware installation 18
7.6 C264 Software upgrade 18
8. DOWNLOADING DATABASE 19
8.1 Database download with CMT 19
8.1.1 Loading DB under CMT 19
8.1.2 Download DB onto C264 19
C264/EN IN/C40 Installation
8.2 Database download with SMT 19

8.2.1 Loading DB under SMT 19
8.2.2 Download DB onto C264 20
8.2.3 Switch to downloaded data base 20
9. AFTER COMPUTER INSTALLATION 21
10. OPTIONAL INSTALLATION 22

10.1 External master clock connection 22
10.2 Printer installation 22
11. CMT ONLINE HELP 23

11.1 INTRODUCTION 23
11.1.1 Scope 23
11.2 Pacis Computer Maintenance Tool (CMT) overview 23
11.2.1 Generalities 23
11.2.2 Launching the software 23
11.2.3 CMT main window 24
11.2.4 Operations performed by CMT buttons 28

This document is a chapter MiCOM C264 documentation binder. 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. REQUIREMENT
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 CPU260 or 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 AREVA T&D Safety Guide: SFTY/4L M/C11 (or later issue)
and rules of chapter C264/EN SA (Safety & Handling).
The CPU260/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 Win2000 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

While you have inserted the PACiS CD-ROM System installation into your CD-drive you will
find the install software of the computer into the following directory:
\System\Delivery\PACiS Va.b.c\C264 VX.YZ (Va.b.c is the PACiS system version, X.YZ is
the computer version).
Install the Computer_X.YZ.exe on your PC.
It is recommended to use default installation parameters. This will install CMT (Computer
Maintenance Tool), FTP server and set the C264 application in a directory accessible by the
MiCOM C264.
Connect the MiCOM C264 and the PC on the same Ethernet switch or directly with a
crossed Ethernet wire.
7.1 Tools installation on the PC
The tools and C264 softwares are delivered on a CD-ROM, these softwares have to be
installed on a PC.
7.1.1 Recommendation for the PC performances
• At least Pentium 3 or similar
• At least 700MHz
• Windows 2000, Windows NT or Windows XP SP2
• At least 100 Mb fee space on hard disk
• A CD-ROM drive
• An Ethernet port
7.1.2 Installation on the PC
The software is in the C264/VX.YZ folder (X.YZ is the computer version).
• Insert the CD-ROM in the CD-drive
• Launch the Computer_X.YZ.exe file
• During installation select parameters as detailed below:

Note: The following screenshots describe installation of release 4.33A of the
computer. Installation for later releases (4.41,…) issimilar.
Click on Next
Click on Nex
Select I accept the agreement and click on Next
Choose the path to install the software but it is better to keep the default parameters.
Click on Next.
Click on Next
Click on Next
Click on Next
Click on Install
Click on Finish
7.2 Connection between the PC and C264

Connect the PC and the C264 via Ethernet following one of the following architecture.
7.2.1 Without Ethernet Switch
Crossed Ethernet
wire
PC C264
C0146ENa
The crossed Ethernet wire is as below:
Connector RJ-45 EIA/TIA-232

1 (connected to pin 8)
2 DTR
3 TxD
4 GND
5 GND
6 RxD
7 DSR
8 (connected to pin 1)
1 Wire colors T-568B:

8
1 ORANGE/
2 ORANGE
3 GREEN/
4 BLUE
5 BLUE/
6 GREEN
7 BROWN/
8 BROWN
Wire colors T-568A:

8 1
1 GREEN/
1 1
2 GREEN
2 2
3 ORANGE/
3 3
4 BLUE
4 4
5 BLUE/
5 5
6 ORANGE
6 6
7 BROWN/
7 7
8 BROWN
8 8
C0148ENa
7.2.2 With Ethernet Switch
Direct Ethernet
cables
PC C264
Ethernet Switch
C0147ENa
The crossed Ethernet wire is as below:

1 connected to 1, 2 connected to 2, etc
7.3 Settings to enter

The computer has a default factory IP address and alias, this needs to be changed to the
application specific values.
The settings to enter are:
• host IP address: your maintenance laptop IP@
• target name: should be the Computer name defined by SCE for its database
• C264 IP address: should be the Computer IP address defined by SCE for its database
Other parameters should not be modified.
The following item describes how to modify the parameters.
7.4 Input new settings
− Launch PACiS FTPD server previously installed.

There is the following icon on your PC desk:
− Launch CMT software previously installed.
There is the following icon on your PC desk:

NOTE: CMT provides an online HELP. This Help is also included in the end of
this IN chapter.
− Access your C264 by select “Search computers” button

NOTE: If there is no computer in the list, it is perhaps due to the Ethernet
interface of your PC. Go into “file” in the top of the window and “Network
interface” to choose the right interface.
− Select your MiCOM C264 in the list
− Go into “Boot Parameters” Menu
− Select “Network boot” option
− Modify:
− “IP on Ethernet (e)“ and set the Ethernet address you have chosen for the MiCOM
C264
− “host IP (h)” and set the Ethernet address of the PC that supports CMT
− “target name (tn)” and set a name for the MiCOM C264
− Click on “Set Boot Parameters” button in order to send the new parameters to the
MiCOM C264.
− Select “Reboot Computer” in order to restart the C264. It will restart with the software
installed on the PC.
7.5 C264 Firmware installation
WARNING : THE OPERATOR MUST CHECK THE TYPE OF CPU EQUIPPING THE
C264 PRIOR STARTING THE FIRMWARE INSTALLATION; THE CPU270
MUST ONLY BE EQUIPPED WITH THE FIRMWARE SELECTED IN THE
“_CPU3” DIRECTORY.
On the CMT application:
− Go into “Boot Parameters” Menu
− Select “flash boot” option
− Click on “Set Boot Parameters” button in order to take into account the new
parameters
− Click on “BootInstall” Menu
− Choose C264_cpu3 directory for CPU270 board

or
Choose C264_cpu2 directory for CPU260 board
− Click on “Updatebootrom”
− Wait for the end of installation
− Click on “Start bootInstall”
− Wait for the end of installation, MiCOM C264 installation takes around 1 minute
− When it is finished restart your computer by clicking on “reboot computer” to take into
account the new parameters and software
After the reboot the computer C264 will switch into maintenance mode. Computer is ready
for receiving the application database.
7.6 C264 Software upgrade
To upgrade a software, the sequence is quite identical with the CMT:
− Click on “BootInstall” Menu
− Choose C264_cpu2 directory
− Click on “Updatebootrom”
− Wait for the end of installation
− Click on “Start bootInstall”
− Wait for the end of installation, MiCOM C264 installation takes around 1 minute
− When it is finished restart your computer by clicking on “reboot computer” to take into
account the new parameters and software
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 CMT (Computer Maintenance Tool) are used to download and switch
the databases.
The use of SMT or CMT 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 CMT
8.1.1 Loading DB under CMT
First action is to copy the .zip database issued from SCE on your PC.
8.1.2 Download DB onto C264
On the CMT application:
− Go into “Key and DB” Menu
− click on “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”
− Click on “Download Data Base” or “Choose your Download/Database Only”

button, choose the “.adb” file of your computer and click on “OK”
− When it is done, click on “Switch Data Bases” button, the MiCOM C264 computer
will restart on the database you have downloaded
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 :
8.2 Database download with SMT

8.2.1 Loading DB under SMT
First action under SMT is to load the DB version. The DB is then stored on the hard disk and
prepared for communication (with communication setting).
The DB will appear in the database list, a right click allows 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 chose the “download all” option and wait for the acknowledgement of
a successful transfer.
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 which case the new database will have 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 are:
• 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.
11. CMT ONLINE HELP

11.1 INTRODUCTION
11.1.1 Scope
This document is an operating manual and describes how to use the Pacis Computer
Maintenance Tool.
Each section explains a particular operation made with the CMT.
11.2 Pacis Computer Maintenance Tool (CMT) overview
11.2.1 Generalities
The CMT provides a friendly way to maintain MICOM Cx6x computers.
Typing commands in the computer shell is not required; the graphical interface does main
operations.
CMT is running on Personal Computers (PC) using Windows 98, NT and 2000.
Moreover, a serial link between the operator PC and the computers is not needed: all the
operations are performed using the local Ethernet network. CMT uses raw Ethernet packet,
in direct Mac addressing mode.
11.2.2 Launching the software
CMT is shipped with the default installation of the MiCOM COMPUTER software.
The CMT is usually found in C:\Program Files\Areva\PACiS\Computer\Cmt, or by clicking on
the "Start menu"/ Program/Areva /Pacis /Computer/Cmt.
When the software is launched, it shows a starting view during 3 seconds.
11.2.3 CMT main window

This window is divided in four sections.
A menu, a "computer" part at the top right, an "operation" section with buttons at the left, and
the most important part, at the center, containing the output of the chosen operations.
11.2.3.1 The menu: File, Tools, and Help

11.2.3.1.1 File menu
File menu contains two submenus: Network Interface and Quit.
Network interface submenu ( F2 )
It selects the Networks Interface board used by the PC to access computer Network.
A chooses window opens and proposes Network interface board existing on your PC.
Select the board you want to use and click OK, or close the window using Windows close
mechanism
For a PC with only one Ethernet board the right board is automatically selected
example:
• MS TCP Loop back interface : (not useable by CMT)
• 3Com 3C90x Ethernet Adapter:
• 3Com Ether Link PCI:
• AT-2500 NDIS Series 4.0 driver:
• NdisWan Adapter : (not useable by CMT)

The selection is saved in Registry
Quit submenu (CTRL + q)
It's used to exit the software
11.2.3.1.2 Tools menu

Tools menu contains two submenus: Language and Background color.
Language submenu
It’s proposing you to choose the language used by CMT. The default language is English,
submenu English ( F3 ) alternate language is French ( F4 ).
The selected language is saved in Registry.
Background colour
It proposes you to choose the background colour used by CMT windows. The default colour
is Grey
Background colour pops up a panel of the 256 colours you can use and lets you pick one of
them. This colour will be the new default background colour. It's better to choose a colour in
the middle of a line.
The selected colour is saved in Registry.

11.2.3.1.3 Help menu

File menu contains two submenus: Index and About.
Index submenu ( F1)
Displays the CMT help file, this file.
About submenu ( F5)
Displays a "about" box: CMT's version and copyrights.
11.2.3.2 The "Search computers" button

It is used to search for computers on the current Local Area Network (LAN).
When pressed, application starts the search, and wait answers for 3 seconds.
After this delay, a list of all the "responding" computers is displayed, with their name, IP
address, Type and serial number.
Just click left on a computer to select it.

Each button is colored representing computer internal state :
application software running or normal : green
application software stopped : blue
Bootprom : red
The selected computer name, IP address, Type and serial number is shown in the top right
white box "Selected Computer:".
Each window can show 20 buttons, clicking the tab ( Next...) makes the next 20 computers
visible. A maximum of one hundred computers is possible.
11.2.3.3 The "Computer's list" button
The list of all the "responding" computers is displayed, with their name, IP address, Type and
serial number, without searching on network.
11.2.3.4 The left bar
It contains all the operations that can be performed on the selected computer:
Simply click on a button to launch the desired task.
Each operation is described in the next section of this manual.
11.2.4 Operations performed by CMT buttons

11.2.4.1 Computer version
The output window software and database information from Cx6x computer:
• Version
• Database compatibility
• UCA2 agency version
• Isagraf software version
• Triangle software version
• creation date of the application software
Information on the running database is also given ( if a database is running ...):
• device name
• device type
• model
• company
• description
• substation
• database name
• version
• path of the database.
• database creation date and last setting date
Information on the computer state:
ACTIVE or MAINTENANCE or INITIALIZATION or SIMULATION or STANDBY or
FAULTY or HALTED or STOPPED
11.2.4.2 Boot Parameter
"Boot Parameters" button shows current computer boot parameters.
Modifications of the values can be done for all the fields displayed in white box ("inet on
Ethernet", "host inet" and "target name").
The radio buttons "Network boot" and "Flash boot" and "Bootprom boot". These three
buttons automatically change the required fields in the boot line to make the computer boot
using FTP (Network ) or using its flash memory (Flash ) or stopped after boot (Bootprom ).
The normal mode is "Flash boot"

Ethernet Interface Type can be selected and saved in computer flash using the white choose
box "Ethernet interface".
possible selection :
[Composant FrontPage Enregistreur de résultats]
RJ45 auto detect is the default mode : auto negotiation between the computer and switch
"Get Boot parameters" button gets information reading computer flash memory.
Once the modifications are finished, the "Set boot Parameters" button has to be pressed in
order to apply the changes on the computer.
Modifications are saved in the flash memory of The CX6X
Modifications will be used only after the next reboot.
11.2.4.3 Key and Data base Management
"Key and DB" button shows the key and data base window management.
11.2.4.3.1 Key Management
Computer software utilization is limited by a software key mechanism.
Each computer is associated with a permission key. This window allows user to read "Get
computer key" or to update "Set computer key" the computer with a new key.
Keys are unique and associated to the computer Ethernet address.
Authorized functions are marked with a black radio button.

11.2.4.3.2 Data base Management
The data base part of the window is used to manage computer data base.
"Data base 1" shows the first data base version revision and its state "CURRENT" or
"STANDBY"
"Data base 2" shows the second data base version revision and its state "CURRENT" or
"STANDBY"
"Clean all DB" removes the first and the second data base.
"Switch data bases" switches the two data bases from "CURRENT" becomes
"STANDBY" and "STANDBY" becomes "CURRENT".
"Select a Data base version" with this button user can select a versioned system data base ,
generated by "System configurator" (S.C.E ).selecting this button opens a new window, type
file chooser, and user can select a "*.x.yy.zip" file.
Once the file "*.x.yy.zip" selected, the file is unzipped and his version revision x.yy is
memorized for the future download operation: "New DB version".
"My Computer" button gives access to the file system of your PC.
Once a data base version is selected user can download the "*.adb" file to computer using
"Download data base".
A file chooser window opens and proposes the "*.adb" files compressed in the "*.x.yy.zip" file
and unzipped by using "Select a Data base version".
Clicking on "OK" will start download database process to computer.

11.2.4.4 Data and Time

This section reads or changes date and time information from or to computer
11.2.4.4.1 Computer use
This section reads memorized data on computer :
"first running date" of the computer: The value stored in "/flash/MAINT/firstrd" is directly
displayed here.
"Computer use "the number of hours the computer has been running. This value is read in
"/flash/MAINT/ophours".
11.2.4.4.2 Get computer date

This section reads time on computer ( local time).
11.2.4.4.3 Set date

This section selects a time and date value from PC and sends it to computer.
"Set date" is used to modify the computer date and time. The current date and time are
taken from Windows on the operator PC and displayed. They can be changed if needed. The
"OK" button is used to confirm the changes and to update the settings on the computer.
Clicking "OK" sends time to computer, if the new time is accepted or not, this confirmation
window will open.
11.2.4.4.4 Set year

This section selects a year value from PC and sends it to computer.
"Set year" acts like "Set date" but only the year is changed. It’s useful to set year on a new
computer because IRIG B does not contain the year information. The default value is taken
from Windows and can be changed. "OK" set the value on the computer.
Clicking "OK" sends time to computer, if the new year is accepted or not, this confirmation
window will open.
11.2.4.4.5 IRIG-B
This section reads IRIG B information from computer.
If IRIG-B interface is present on the CPU board :
If IRIG-B interface is not present on CPU :

11.2.4.4.6 Synchronism
This section reads synchronism information from computer.
11.2.4.5 Errors
The content of "/flash/systrap/index.txt" is displayed. It shows the number of 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 "File to display" choose box.
On a CX6X the last tenth error files are archived, you can select one of this file using "File to
display" choose box
Once a file is selected you visualize it, clicking :
⇒ "Open" shows the file on the output window.

⇒ "Print" sends the file to the Windows printer.
"Save as ..." save the file on the PC disk. It opens a new file chooser window.
Note that the file filename refers to the file "/flash/SYSTRAP/STxx.TXT" on the computer.
11.2.4.6 File Explorer

This section is designed like many FTP clients or files explorer.
The left part is an image of the local PC file system, the right one an image of the computer
file system.
11.2.4.6.1 Local PC Side ( Left )

On the PC-side , the default current directory is the latest selected directory ( value saved in
Registry )
Directories are displayed with a bold font. They can be browsed by simple click. The
content of the browser is automatically updated to reflect the new directory files or
subdirectories.
Files are shown with a normal font. To select a file, just simple click on it ( dark blue
background indicates the selection).
The top box "Change disk" list all the drives of the PC used as root for the browser.
A grey box shows the current path or selected file ( bold).
11.2.4.6.2 Remote Computer Side ( Right )
On the right size, you first have to choose the root of the computer file system. /RAMDEV (
ramdisk ) and /flash ( flash memory ) are available. click on the "Change root" box.
a simple click on a directory shows its content and simple click on a file selects it ( dark
blue background indicates the selection).
For each file, its size and modification date is also displayed.
11.2.4.6.3 Download ( Left to Right Arrow )

To begin a transfer, use the two arrows between the two browsers:
The "Left to Right Arrow" download the file selected on the PC browser in the directory
selected on the computer.
Name is not changed, only files with DOS name format ( 8 . 3 character format ) can be
copied .Files is automatically overwritten on the computer if it's already exist.
The progress-meter shows the advancement of the transfer in yellow, write time on flash
memory is represented by a full red progress-meter
11.2.4.6.4 Upload ( Right to Left Arrow )
The "Right to Left Arrow" uploads a file. The file selected on the computer is uploaded on the
PC, in the current directory.
Name is not changed. Files is automatically overwritten on the computer if it's already exist.
The progress-meter shows the advancement of the transfer in yellow.
11.2.4.6.5 Delete
The "Delete" button delete the selected file on the computer file system.
A confirmation window opens showing the full path of the file to be deleted and user can
confirm or cancel.
11.2.4.6.6 Format
The "Format" button erases and reformats the computer file system , all files are deleted.
This button is only useable wile computer is stopped or on boot mode.
A confirmation window opens and user has to confirm or cancel his click.
11.2.4.7 BootInstall
This function is equivalent to the BootInstall command, launched from a shell. It's
downloaded automatically a set of files mandatory for a Cx6x computer application.
The directory is to be selected by the operator. the set of file is automatically selected and
must match with the type of CPU Board equipping the C264 :
11.2.4.7.1 Local PC Side ( Left )
On the PC-side, the default current directory is the latest selected directory (value saved in
Registry)
Directories are displayed with a bold font. They can be browsed by simple clicks. The
content of the browser is automatically updated to reflect the new directory files or
subdirectories.
Files are shown with a normal font. To select a file, just simple clicks on it ( dark blue
background indicates the selection).
The top box "Change disk" list all the drives of the PC used as root for the browser.
A grey box show the current path ( bold). If a file is selected, only the path is used, the
filename is ignored.
11.2.4.7.2 Start BootInstall

If the computer is not in the mode: STOPPED or BOOT
After a confirmation window , the BootInstall begins.
The upper progress-meter, shows the advancement file by file ( yellow for the transfer and
red for write ).
The lower progress-meter, shows the advancement of the global process (yellow).
the "Start BootInstall" button is deleted after each used , you have to re-click on "BootInstall"
button and reselect a directory.
11.2.4.7.3 Abort BootInstall
The "Abort BootInstall" button can stop the file transfer process. Click is memorized and stop
the download after a full file transfer, it can't stop inside a file transfer. No confirmation is
needed.
11.2.4.7.4 Update bootrom
The "Update bootrom" button is used to update the bootrom part of the computer flash (
software executed after a restart) . Computer must be in stop mode to allow this function.
First user must select a directory witch contains "bootrom.flh" file. A confirmation is
requested.
The file is downloaded first to computer /RAMDEV/bootrom.flh and after copied in flash.
Be sure of your choice, if a bad file is selected the computer will not reboot at next
restart.
11.2.4.8 Telnet
This button launches the default Windows Telnet client on the operator PC. Telnet is
connected to the selected computer.
It can be used to easily get a shell on the computer, in order to perform tasks that CMT can't
handle.
the "logout" command or the Windows close can be use to terminate the session.
As Telnet is launched independently of CMT, multi sessions on two or more computers are
possible.
Telnet used TCP/IP stack and the computer have to be accessible from the PC in this
mode ...
11.2.4.9 Event log storage
This section reads or changes event log storage and printer configuration from or to
computer.
11.2.4.9.1 Event log storage management
Function Information
"Function information" gives information about event log storage mechanism.
Enable/Disable event log storage
"Disable event log storage" (default state) disables event log storage mechanism. The state
is updated in function information window.
"Enable event log storage" (default state) enables event log storage mechanism. The state is
updated in function information window.
Get stored event log

"Get stored event log" reads event log saved in computer flash memory, transfers it in a
"temporary" file : c:\Temp\ArchX.lst
and opens a "notepad" window.

The file can be edited, printed, saved like a regular PC file.

11.2.4.9.2 Printer management
Get Printer Parameter

"Get Printer Parameter" reads printer configuration.
Device can be one of:

"no printer"
"Frontal RS232": subd 9 points on front panel ( setting or shell connector )
"/Scc1/tty": port 1 on BIU
"/Scc2/tty": port 2 on BIU
"/Scc3/tty": port 3 on Cpu260 board (rear side)
"/Scc4/tty": port 4 on Cpu260 board (rear side)
Control can be one of:

"0 (none)" no control
"1 (Xon/Xoff)" software control
"2 (Hard)" hardware control
"3 (Both)" software and hardware control
Printer mode
"printer mode" changes printer mode from NORMAL ( prints events marked as printable in
configuration) to OFF ( don't print any events even if printable in configuration ) or DEBUG
(print all events even if they are not marked printable in configuration).
Event log mode

"Event log mode" changes event log mode from NORMAL ( saves events marked as "log"
in configuration) to DEBUG (saves all the events even if they are not marked "log" in
configuration).
11.2.4.10 Stop Computer

This operation stops the selected computer application software, It suspends alls tasks
except "SYNCHRO" and "SUPERV". A confirmation is needed.
11.2.4.11 Reboot Computer

This operation reboots the selected computer. A confirmation is needed.
MiCOM C264/C264C
SETTINGS
CONTENT

1.1 Tree Panel Navigation 3
1.2 Tree Panel Parameters 4
C264/EN ST/C40 Settings
BLANK PAGE

This document is a chapter of MiCOM C264 documentation binders. 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) part with default
and range values.
1.1 Tree Panel Navigation
Tree panel is accessible from bay panels by selecting the following key:
All data points are grouped into features and folders. To access a given feature the operator
should navigate the panels using the arrow keys. The folders hierarchy is displayed in each
panel.
switches to neighbouring folder
switches to neighbouring folder
select and expand the folder switching to its first item
go up to father folder
At the bottom of the hierarchy, the folder is the single point of information, control or
parameter. Edit mode allows the operator to change values.
Enter into Edit mode. It then asks to enter the level 2 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 .
1.2 Tree Panel Parameters
Available Values
Parameter
MENU TREE Or
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
Parameter
MENU TREE Or
signification
- 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
Parameter
MENU TREE Or
signification
- 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
synchrccheck”
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
synchrccheck”
operator control.
- MAN SYN CLO LDBD YES, NO Flag to permit or not a
and a dead bus. for a
“close with
synchrccheck”
operator control.
Available Values
Parameter
MENU TREE Or
signification
- 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
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
order for a 3 phases
trip.
Available Values
Parameter
MENU TREE Or
signification
- 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
order.
- FOURTH CYCLE [1000;3600000](1000)(ms) Time between the
fourth protection trip
and the Circuit Breaker
close 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
Parameter
MENU TREE Or
signification
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
Parameter
MENU TREE Or
signification
- 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,12
00,2400,4800,9600,19
200,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.
- PASSWORD XXXX Password: needed to
modify parameters.
- 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.
FIGURE 1 : MENU TREE FOLDER ORGANISATION

Communications C264/EN CT/C40
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 7
2.1.4 Supported data objects 7
3. SCADA COMMUNICATION 8
3.1 Overview 8
3.2 SCADA common functionality 8
3.2.1 Interface to SCADA 8
3.2.2 Behaviour and specific treatments 9
3.2.3 Data sent to SCADA 10
3.2.4 Data sent to MiCOM C264 12
3.3 Slave DNP3 profile 13
3.3.1 DNP3 level 3: IMPLEMENTATION TABLE 16
3.4 Slave IEC 60870-5-101 profile 20
3.4.1 System or device 20
3.4.2 Network configuration 20
3.4.3 Physical layer 21
3.4.4 Link layer 21
3.4.5 Application layer 22
3.4.6 Basic application functions 26
3.4.7 Protocol Requirements 30
3.4.8 Application Functions 30
3.5 Slave IEC 60870-5-104 Server profile 32
3.5.1 System or device 32
3.5.2 Network configuration (Network-specific parameter) 32
3.5.3 Physical layer (Network-specific parameter) 33
3.5.4 Link layer (Network specific parameter) 33
3.5.5 Protocol Requirements 34
3.5.6 Application layer 34
3.5.7 Basic application functions 40
3.6 Slave DNP3 (TCP/IP) profile 43
C264/EN CT/C40 Communications
3.7 Slave Modbus (MODICON) profile 44

3.7.1 Introducing MODBUS 44
3.7.2 Slave responses 45
3.7.3 Serial transmission mode 46
3.7.4 MODBUS Functions 47
3.7.5 Function 01 / 02: Read Coil Status – Read Input Status 48
3.7.6 Function 03 / 04: Read Holding Registers / Input Registers 49
3.7.7 Function 05: Force Single Coil 51
3.7.8 Function 06: Preset single register 51
3.7.9 Function 08: Diagnostic [Sub-function 0 only] 52
3.7.10 Function 15: Force Multiple Coils 52
3.7.11 Function 16: Preset multiple registers 52
4. IED COMMUNICATION 53
4.1 Overview 53
4.2 IED Common functionality 53
4.2.1 Interface to IEDs 53
4.2.2 Behaviour 54
4.2.3 Data received from IEDs 58
4.2.4 Data sent to IEDs 58
4.2.5 Tunnelling 59
4.2.6 Limits and Performances 62
4.3 MODBUS communication 62
4.3.1 Finality 62
4.3.3 Behaviour 63
4.3.6 Error management 64
4.3.7 Limits and Performances 64
4.3.8 Modbus communication for Px4x events 65
4.4 DNP 3.0 Communication 66
4.4.1 Finality 66
4.4.3 Behaviour 67
4.4.6 Master DNP3.0 Profile 69
4.4.7 DNP.3 Level 3 IMPLEMENTATION TABLE 72
4.5 IEC 60870-5-103 Communication 76

4.5.1 Finality 76
4.5.3 Behaviour 77
4.6 IEC 60870-5-101 Communication 82
4.6.1 Finality 82
4.6.2 Master IEC 60870-5-101 profile 82
BLANK PAGE

This document is a chapter of MiCOM C264 documentation binders. It describes the various
standard communications protocols implemented in the MiCOM C264.
MiCOM C264 supports 3 different types of communications:
• SCP Communication: communication over Ethernet IEC61850
• 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. SCADA COMMUNICATION
3.1 Overview
A MiCOM C264 can be connected to a SCADA through networks using various protocols:
1. DNP3 (serial link)
2. T101 (serial link)
3. T104 (TCP/IP link)
4. DNP3 (TCP/IP link)
5. MODBUS (serial link)
It is possible to have:
• Two different protocols running in parallel on different links
• The same protocol on two links (redundant mode). This is actually not supported for
Modbus protocol.
• For protocols running on TCP/IP link, there is only one Ethernet port. So redundancy
is not available for those protocols, and they all are physically running on the same
network (including IEC61850 protocol).
• In T104 protocol the C264 (server) can manage two clients. These two clients have
separate configurations but may have same data. On the SCADA port, up to four front
ends can be defined, corresponding to one active port and three backup ports. So, up
to four IP addresses will be defined during the configuration of each T104 client. If
both clients are communicating with the computer, they must manage thein own
redundancy for doing controls with coherency.
Common features to all SCADA communication and all protocols are specified below.
Specific features to each protocol are specified in subsequent paragraphs.
3.2 SCADA common functionality
3.2.1 Interface to SCADA
This paragraph describes the exchange of data between the “SCADA communication”
function and the Master SCADA. It is split into 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:
3.2.1.1 Input
Data DNP3 T101 T104 DNP3 on IP MODBUS

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

Digital input Treated Treated Treated Treated Treated
Dated Digital input Treated Treated Treated Treated Not Treated
Measurement (Events) Treated Treated Treated Treated Not Treated
Measurement (Cyclical) Treated Treated Treated Treated Treated
Counter Treated Treated Treated Treated Treated
Tap position Treated Treated Treated Treated Treated
Control acknowledgement Treated Treated Treated Treated Treated
Setpoint acknowledgement Treated Treated Treated Treated Treated
MiCOM C264 Disturbance Not Treated Not Treated Not Treated Not Treated Not Treated
Sequence Of Event File Not Treated Treated Treated Not Treated Not Treated
3.2.2 Behaviour and specific treatments

NOTE: In subsequent paragraphs, the master station (e.g.: SCADA) is referred to
as the controlling station.
3.2.2.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).
3.2.2.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.
3.2.2.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.
3.2.2.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)
3.2.2.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.
3.2.2.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.
3.2.2.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.
3.2.2.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
3.2.2.9 Automatic synchrocheck
SCADA can send control to synchronised circuit breakers with a facility to bypass the
synchrocheck.
3.2.3 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.
3.2.3.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.
3.2.3.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.
3.2.3.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.
3.2.3.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.
3.2.3.5 Computer disturbance file
Only Slow Wave Form is implemented for T101 or T104. maximum 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
3.2.3.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
3.2.3.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.
3.2.4 Data sent to MiCOM C264
SCADA can send data to MiCOM C264. The type of data is described in subsequent
paragraphs.
3.2.4.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.
3.2.4.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

3.2.4.3 Synchronisation
Depending on the configuration, MiCOM C264 can be synchronised by a SCADA.
3.3 Slave DNP3 profile
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 _______________________ 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
________________________________________________________________
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 (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
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.
3.3.1 DNP3 level 3: IMPLEMENTATION TABLE
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes (2)
(dec) (hex)
(dec) (hex)
1 0 Binary Input – All Variations 1 00,01,06,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 Change - All Variations 1 06,07,08 129,130 17
2 1 Binary Input Change without Time 1
2 2 Binary Input Change with Time 1 06,07,08 129,130 17
2 3 Binary Input Change with Relative Time 1
10 0 Binary Output - All Variations 1
10 1 Binary Output
10 2 Binary Output Status 1
12 0 Control Block - All Variations (1)
12 1 Control Relay Output Block (1) 3,4,5,6 17,28 129 Request
echo
12 2 Pattern Control Block
12 3 Pattern Mask
20 0 Binary Counter - All Variations 1,7,8,9,10 00,01,06,17,28
20 1 32-Bit Binary Counter 1 00,01,06,17,28 129 00,17,28
20 2 16-Bit Binary Counter 1 00,01,06,17,28 129 00,17,28
20 3 32-Bit Delta Counter
20 4 16-Bit Delta Counter
20 5 32-Bit Binary Counter without Flag 1 00,01,06,17,28 129 00,17,28
20 6 16-Bit Binary Counter without Flag 1 00,01,06,17,28 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
Func Qual
(dec) (hex)
(dec) (hex)
21 0 Frozen Counter - All Variations 1 00,01,06,17,28
21 1 32-Bit Frozen Counter 1 00,01,06,17,28 129 00,17,28
21 2 16-Bit Frozen Counter 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
21 6 16-Bit Frozen Counter with Time of
Freeze
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 1 00,01,06,17,28 129 00,17,28
21 10 16-Bit Frozen Counter without Flag 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 Change Event - All Variations 1 06,07,08
22 1 32-Bit Counter Change Event without
Time
22 2 16-Bit Counter Change Event without
Time
22 3 32-Bit Delta Counter Change Event
without Time
22 4 16-Bit Delta Counter Change Event
without Time
22 5 32-Bit Counter Change Event with Time 1 06,07,08 129,130 17
22 6 16-Bit Counter Change Event with Time 1 06,07,08 129,130 17
22 7 32-Bit Delta Counter Change Event with
Time
Time
23 0 Frozen Counter Event - All Variations 1 06,07,08
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
Time
REQUEST RESPONSE
OBJECT
Func Qual
(dec) (hex)
(dec) (hex)
30 0 Analog Input - All Variations 1 00,01,06,17,28
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
32 1 32-Bit Analog Change Event without 1 06,07,08 129,130 17
Time
32 2 16-Bit Analog Change Event without 1 06,07,08 129,130 17
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 1,2 07 (quantity=1)
50 2 Time and Date with Interval
51 0 Time and Date CTO - All Variations
51 1 Time and Date CTO
51 2 Unsynchronized Time and Date CTO
52 0 Time Delay - All Variations
52 1 Time Delay Coarse
52 2 Time Delay Fine
REQUEST RESPONSE
OBJECT
Func Qual
(dec) (hex)
(dec) (hex)
60 0
60 1 Class 0 Data 1 06,07,08
60 2 Class 1 Data 1 06,07,08
20,21 06
60 3 Class 2 Data 1 06,07,08
20,21 06
60 4 Class 3 Data 1 06,07,08
20,21 06
70 0 File management – All variations
70 2 Authentication Object 29 5b 129 5b
70 3 File Command Object 25,27 5b 129 5b
70 4 File Command Status Object 26,30 5b 129 5b
70 5 File Transfert Object 1,2 5b 129 5b
70 7 File Description 28 5b 129 5b
80 1 Internal Indications
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
3.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.
3.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)
3.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

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

3.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 to to 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
<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 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

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<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 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
3.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
3.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)
3.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 return 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 an other 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.
3.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
3.5.1 System or device
System definition
Controlling station definition (Master)
Controlled station definition (Slave)
3.5.2 Network configuration (Network-specific parameter)
Point-to-point Multipoint-party line
Multiple point-to-point Multipoint-star
3.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
3.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.
3.5.5 Protocol Requirements
3.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)
3.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)
3.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
<2> M_SP_TA_1
<3> M_DP_NA_1 X X X X
<4> M_DP_TA_1 .
<5> M_ST_NA_1 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
<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 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

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<51> C_BO_NA_1
<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

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


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
3.6 Slave DNP3 (TCP/IP) profile

See Slave DNP3 Profile
3.7 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.
3.7.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
3.7.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.
3.7.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.
3.7.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.
3.7.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 do not reply to corrupted data messages, i.e when the CRC is not correct or
when parity is not correct.
3.7.2 Slave responses

3.7.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.
3.7.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 the
ACKNOWLEDGE 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 Not used in the gateway
PARITY ERROR
3.7.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)

3.7.4 MODBUS Functions

MODBUS defines 24 functions, valid codes are in the range of 1-24.
3.7.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
3.7.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.
3.7.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
3.7.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).
3.7.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
3.7.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.
3.7.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.
3.7.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.
3.7.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.
3.7.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)
3.7.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.
3.7.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.
3.7.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. IED COMMUNICATION
4.1 Overview
Different types of IEDs are connected to a MiCOM C264 through networks using various
legacy protocols:
1. IEC 60870-5-103 (T103)
2. Modbus
3. DNP3
4. IEC 60870-5-101 (T101)
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.
4.2 IED Common functionality
4.2.1 Interface to IEDs
4.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
4.2.1.2 Output
Data Note
Control Treated
Setpoint Depending on the protocol
Alarm acknowledgement Not Treated
Tunnelling Frame question Depending on the protocol
Time synchronisation Treated
4.2.2 Behaviour
4.2.2.1 Network supervision
The number of networks and IEDs is known by configuration.
Each network is managed independently of the other networks.
The management of a network consists of:
• 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.
4.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.
4.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.
4.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.
4.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.
4.2.3.1 Digital inputs
Digital inputs can be received as states or as changes of state. The choice between state
and change of state depends on the IED and on the protocol. This is known by configuration.
Even if digital inputs are received as change of state, it is still possible to request data as
states for general interrogations.
The conversion from digital input to binary input is performed by the binary input processing
function. A digital input can be associated with a single point or a double point.
Measurements can be received in various formats: float, binary, BCD, etc. The received
value is converted into an internal format, which is common to all measurements in the
MiCOM C264.
Measurements can be received as periodical messages or as changes of state: variation,
threshold, and invalidity.
A message is sent to the processing function whenever a measurement is received from an
IED.
4.2.3.3 Counters
Counters are treated for DNP3.0
4.2.3.4 Tap position
Tap position are treated like measurements
4.2.3.5 Disturbance File
MiCOM C264 stores disturbance files as they are sent by IEDs without control of the format
of the Disturbance Files (Comtrade, …).
4.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.
4.2.4.1 Controls
Controls are priority message. The polling sequence must be interrupted in order to send the
control as soon as possible.
Not all IEDs send control 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 send 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).
4.2.4.2 Setpoints
SP controls are priority message. The polling sequence must be interrupted in order to send
the SP control as soon as possible.
Not all IEDs send SP control 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.
4.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.
4.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”.
4.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.
4.2.5.3 Procedure of use of the serial tunnelling
• Connect a LapTop to the computer with a 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)

4.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.
4.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.
4.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.
4.2.5.7 Tunnelling limits and Performances
The legacy protocols supported [protocols for which serial tunnelling is available] are the
following:
• 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’s automatically configured:
19200Bd, 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.
4.2.6 Limits and Performances
• 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.
• Performance depends on the protocol used and on the number of IEDs connected to
each Network.
4.3 MODBUS communication
4.3.1 Finality
MODBUS is a legacy bus master/slave protocol that is used by many devices such as
relays, MiCOM C264s or monitoring devices. The aim of this chapter is not to describe the
protocol itself and its mechanisms (other documents and norms are there for that) but to give
the specificity of the functions that will be implemented in the MiCOM C264. These are the
MODBUS function numbers that will be used, the way in which each type of data will be
internally or externally updated, the general mechanisms used for the time synchronisation
and the configuration needs.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master Modbus” in the MiCOM C264.
The following MODBUS functions are implemented in the MiCOM C264:
Function
Sub-code Used for Commentary
number
1–2 / Read DIs Read N bits
3–4 / Read DIs / MEAS / Read N words
Disturbance files
5 / Write CO Write 1 bit
15 / Write CO Write N bits
This function could be used with the
following restriction: you can only write
COs one after the other.
7 / Polling Read status byte
This function is used for detecting a DI
change of state, the presence of
disturbance files (Areva IEDs)
8 0 Polling Echo
This function could be used for
detecting if a device is connected or
not.
6 / Eventually for Write 1 word
tunnelling
16 / Eventually for Write N words
tunnelling
4.3.3 Behaviour
4.3.3.1 Polling
During a polling procedure, each slave is polled one after the other. This means that the
master waits for the answer to a request sent to a device before sending a new request to
the same or an other device.
There will be 2 types of polling:
• the polling performed by the application for the measurements and the digital inputs
• a low level polling used for detecting if a device is present or not.

If an IED does not correctly answer after a defined timeout (configured), the request is resent
by the MiCOM C264. If the IED do not correctly answer after a defined number of retries
(configured) it is considered as disconnected. Then it is polled regularly (not too often) to
eventually be reconnected to the network.
The processing applied to the measurements is the same for all devices.
The application reads the measurements by polling the device at a defined frequency.
We define a block of measurements as a set of measurements that have been configured at
consecutive addresses. As a result, to improve the polling performance, all the
measurements of a block will be read thanks to just one exchange having regard to the
number of measurements to be read.
4.3.4.2 Digital Inputs
The processing applied to the DIs depends on the IEDs. Each change of a DI is dated, either
in the MiCOM C264 or in the IED, depending on the IED type.
We define a block of DIs as a set of DIs that have been configured at consecutive
addresses. As a result, to improve the polling performance, all the DIs of a block will be read
thanks to just one exchange having regard to the number of DIs to be read.
Processing for generic IEDs
By default, the DI blocks are regularly polled by the application. Then the application
compares the state of each DI with the previous state. So the MiCOM C264 itself performs
the time stamping of a change of state.
Processing for Areva IEDs
The status byte-taking place in an Areva IED contains the information indicating that events
(DI changes) are present. As a result, the status byte is regularly polled by the link layer
through a low level polling and compared with the previous one. If a change is detected, the
master reads the event queue inside the IED, checks which data have changed, checks if
they have been configured and then reads the information itself. Notice that in this case, the
DI changes are dated in the IED and the MiCOM C264 downloads their date and time.
4.3.4.3 Disturbance files
Disturbance files are only treated for devices that conform to the MODBUS Areva rules and,
if needed for other devices (specific developments).

4.3.5.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.
Areva IEDs
The “Read status byte” frame is used for checking the connection of the device.
4.3.5.2 Time synchronisation
Preliminary remark: All the devices connected to a given network must have the same
synchronisation procedure (address and time and date format)
because the synchronisation is performed through a broadcast frame.
There will be three types of synchronisation depending on a configuration parameter:
• No synchronisation;
• Areva synchronisation: date and time conform to the inverted IEC 870-5-4
CP56Time2a format and is set at address 800h;
• SEPAM synchronisation: date and time conform to the SEPAM (Merlin Gerin)
documentation ( SEPAM1000+S20, SEPAM1000+S40, PM500, PM650, SEPAM2000)
No calculation of the transmission delay is performed.
4.3.5.3 Commands
Commands are sent to the IED and have the highest priority level. They come from the
application and have to be transmitted to the destination device as fast as possible. An
acknowledge (which is the answer from the IED to the MiCOM C264 in the MODBUS
exchange) is waited by the application. If the acknowledge is not received after a defined
timeout, you consider that the command has not been taken into account.
4.3.6 Error management
The MODBUS protocol handles a mechanism of exception answer. This means that an IED
could answer with an exception frame if it does not understand the request. There are
different exception codes:
Exception
Meaning Processing performed by the master
code
01 Illegal function Send a “Configuration error” message to the
application and continue
02 Illegal data address Send a “Configuration error” message to the
03 Illegal data value Send a “Configuration error” message to the
04 Slave device failure Send a “IED error” message to the application
05 IED busy because of a Retry after a defined temporisation
long treatment duration
06 IED busy Retry after a defined temporisation
07 Treatment not possible Send a “IED error” message to the application
08 IED memory parity error Send a “IED error” message to the application
4.3.7 Limits and Performances
The performances depend a lot on the number of devices connected on the network. It is
advised to connect devices that have similar performance level on a given network, i.e. the
same reply time for instance.
Each device on a MODBUS network must have the same synchronisation mode.
4.3.8 Modbus communication for Px4x events

Only Events extraction is managed:. The various kind of events: “Alarm event”, “Output
Contact event”, “Opto input event” and “Protection event” are managed.
The disturbance file extraction is out of the scope.
Description of Event record format in Px4x
Each Modbus address references a 16 bits Modbus register.
Modbus Address Contents Description

3x00103 … 3x00106 Time stamp of the Event IEC870 Time & Date
3x00107 Event type Code 0, 1 ,2, 3 = Alarm event
Code 4 = output contact event
Code 5 = opto input event
Code 6 = Protection events
3x00108 … 3x00109 Event value New value of the 32 bits register
containing the xPS which had
changed.
3x00110 32 bits Register Modbus address of the 32 bits
reference register containing the xPS which
had changed.
Caution: real Modbus address
must be re-computed with
substraction of the 30001 value.
3x00111 … 3x00112 Not used by C264 -
Management of Px4x on Modbus will be done on the same scheme than Px2x management.
That implies following rules:
• The C264 identifies a relay as being a Px4x;
• The C264 synchronizes the Px4x truth the legacy network;
• At initialization stage, first acquisition of xPS is done by polling (*);
• In all cases (the Px4x is synchronized or not synchronized), the acquisition of status
xPS changes is done by Event extraction.
(*)
Polling means that all register containing Px4x xPS – defined in C264 configuration - are
periodically read.
4.4 DNP 3.0 Communication

4.4.1 Finality
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.
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

4.4.2.1 Input
Object Variation Data GI Polling Function

01 0 Static BI ♦ [1] READ
02 0 BI Event ♦ [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.
4.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
[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
4.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:
− Poll BI, Poll Measurement, Poll counter, Poll BI ….
− Poll C1, Poll C2, Poll C3, Poll C1 …
− 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.
• 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
4.4.6 Master DNP3.0 Profile
Vendor Name: AREVA T&D

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
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 Configurable (attach explanation)
other (explanation below)
User option to have all Binary Input

Change Events returned as either:
• time-tagged OR
• non-time-tagged
Sends Unsolicited Responses: Sends 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
• 16-Bit Binary Counter
Sends Multi-Fragment Responses: Yes No
4.4.7 DNP.3 Level 3 IMPLEMENTATION TABLE

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

REQUEST RESPONSE
OBJECT
Func Qual
(dec) (hex)
(dec) (hex)
21 0 Frozen Counter - All Variations 1 00,01,06
21 1 32-Bit Frozen Counter 1 00,01,06 129,130 00,01
21 2 16-Bit Frozen Counter 1 00,01,06 129,130 00,01
21 3 32-Bit Frozen Delta Counter 1 00,01,06 129,130 00,01
21 4 16-Bit Frozen Delta Counter 1 00,01,06 129,130 00,01
21 5 32-Bit Frozen Counter with Time of 1 00,01,06 129,130 00,01
Freeze
21 6 16-Bit Frozen Counter with Time of 1 00,01,06 129,130 00,01
Freeze
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 1 00,01,06 129,130 00,01
21 10 16-Bit Frozen Counter without Flag 1 00,01,06 129,130 00,01
21 11 32-Bit Frozen Delta Counter without Flag
21 12 16-Bit Frozen Delta Counter without Flag
22 0 Counter Change Event - All Variations 1 06,07,08
22 1 32-Bit Counter Change Event without 1 06,07,08 129,130 17,18
Time
22 2 16-Bit Counter Change Event without 1 06,07,08 129,130 17,18
Time
22 3 32-Bit Delta Counter Change Event 1 06,07,08 129,130 17,18
without Time
22 4 16-Bit Delta Counter Change Event 1 06,07,08 129,130 17,18
without Time
22 5 32-Bit Counter Change Event with Time 1 06,07,08 129,130 17,18
22 6 16-Bit Counter Change Event with Time 1 06,07,08 129,130 17,18
Time
Time
Remarks:
Frozen counters (type21) are uploaded during general interrogation, but never polled after this.
REQUEST RESPONSE
OBJECT
Func Qual
(dec) (hex)
(dec) (hex)
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
Time
23 2 16-Bit Frozen Counter Event without 1 06,07,08 129,130 17,18
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
23 5 32-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17,18
23 6 16-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17,18
Time
Time
30 0 Analogue Input - All Variations 1 00,01,06
30 1 32-Bit Analogue Input 1 00,01,06 129,130 00,01
30 2 16-Bit Analogue Input 1 00,01,06 129,130 00,01
30 3 32-Bit Analogue Input without Flag 1 00,01,06 129,130 00,01
30 4 16-Bit Analogue Input without Flag 1 00,01,06 129,130 00,01
31 0 Frozen Analogue Input - All Variations
31 1 32-Bit Frozen Analogue Input
31 2 16-Bit Frozen Analogue Input
31 3 32-Bit Frozen Analogue Input with Time
of Freeze
31 4 16-Bit Frozen Analogue Input with Time
of Freeze
31 5 32-Bit Frozen Analogue Input without
Flag
31 6 16-Bit Frozen Analogue Input without
Flag
32 0 Analogue Change Event - All Variations 1 06,07,08
32 1 32-Bit Analogue Change Event without 1 06,07,08 129,130 17,18
Time
32 2 16-Bit Analogue Change Event without 1 06,07,08 129,130 17,18
Time
32 3 32-Bit Analogue Change Event with 1 06,07,08 129,130 17,18
Time
32 4 16-Bit Analogue Change Event with 1 06,07,08 129,130 17,18
Time
33 0 0 Frozen Analogue Event - All Variations
33 1 32-Bit Frozen Analogue Event without
Time
33 2 16-Bit Frozen Analogue Event without
Time
33 3 32-Bit Frozen Analogue Event with Time
33 4 16-Bit Frozen Analogue Event with Time
40 0 Analogue Output Status - All Variations 1 00,01,06
40 1 32-Bit Analogue Output Status 1 00,01,06 129,130 00,01
40 2 16-Bit Analogue Output Status 1 00,01,06 129,130 00,01
REQUEST RESPONSE
OBJECT
Func Qual
(dec) (hex)
(dec) (hex)
41 0 Analogue Output Block - All Variations 3,4,5,6 17,28 129 Request
echo
41 1 32-Bit Analogue Output Block 5,6 17,28 129 Request
echo
41 2 16-Bit Analogue Output Block 5,6 17,28 129 Request
echo
50 0 Time and Date - All Variations
50 1 Time and Date 2 07 (quantity=1)
50 2 Time and Date with Interval
51 0 Time and Date CTO - All Variations
51 1 Time and Date CTO 129,130 07
(quantity=1)
51 2 Unsynchronized Time and Date CTO 129,130 07
(quantity=1)
52 0 Time Delay - All Variations
52 1 Time Delay Coarse 129,130 07
(quantity=1)
52 2 Time Delay Fine 129,130 07
(quantity=1)
60 0
60 1 Class 0 Data 1 06,07,08
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
70 1 File Identifier
80 1 Internal Indications 2 00 (index=7 ou
index=4)
1 00,01
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

4.5 IEC 60870-5-103 Communication

4.5.1 Finality
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.
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

4.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
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 – MiCOM Px3x only
couple FUN/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
4.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 adress 0 which is DVICE: Device type
144 Setpoint Reg D only
4.5.3 Behaviour
4.5.3.1 Synchronisation
The “Master T103” link is always synchronised by the MiCOM C264. No calculation of the
transmission delay is performed.
4.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.
4.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
4.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
4.5.3.5 Station Interlocking
This functionality is only available on MiCOM P139 in private T103 range (Alstom 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).
4.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).
4.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, (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

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

4.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
4.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.
4.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).
4.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
ASDU
DN2 Cfg Function type Cfg
DN3 Cfg Information Number Cfg
DC0 1=OFF; 2=ON DC0 1=OFF; 2=ON
X 0 RII Set by master
Comparing ASDU105 & ASDU01
ASDU105 ASDU01
Field Value Field Value
ASDU No 69H ASDU No 01H
VSQ 81H VSQ 81H
COT 45H, 46H, 47H, COT 14H, 15H, 0BH
7FH
Device address @ied Common Address of @ied
ASDU
DN2 Idem ASDU232 Function type Idem ASDU20
DN3 Idem ASDU232 Information Number Idem ASDU20
DPI 1=OFF; 2=ON DPI 1=OFF; 2=ON
X 0 msLow
Four octet binary
msLow msHigh
time
Four octet
msHigh IV 0 mmmmmm
binary time CP32Time2a
IV 0 mmmmmm SU 00 hhhhhh
CP32Time2a
SU 00 hhhhhh SIN Idem RII ASDU20
Configuration
Management of commands through ASDU 232.
• The ASDU number [232]
• DN2 & DN3 (respectively ‘y’ & ‘x’ component of PID)

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

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

4.6.1 Finality
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.
4.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.
4.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)
4.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

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

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

20 to 37 to
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45 46 47
36 41
<47> C_RC_NA_1 X X X X X X X X X
<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
4.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
4.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.
BLANK PAGE
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/C40 Commissioning
BLANK PAGE

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 AREVA T&D Safety Guide: SFTY/4L M/C11 ( 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
“AREVA”.
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)

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,
DIU220 or CCU200).
For DIU200, DIU210 and DIU220 boards:
D I <time>
DIU <Number>
DI 0 <status> DI 8 <status>
For CCU200 boards:
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 or
CCU200).
For DOU200 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 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 CMT to answer these
questions and ensure that the MiCOM C264 is fully operational in its application.
The CMT is fully described in IN chapter.
With the CMT, 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/C40
MiCOM C264/C264C
RECORD SHEET
CONTENT
2. COMMISSIONING RECORD 4
3. MAINTENANCE RECORD SHEET 5

C264/EN RS/C40 Record Sheet
BLANK PAGE

This document is a chapter of MiCOM C264 documentation binders. 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 7
2.2 Maintenance period 7
2.3 Method of repair 7
2.3.1 Replacing the complete MiCOM C264/C264C 8
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/C40 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 AREVA T&D Safety Guide: SFTY/4L M/C11 (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 LED fast blinking LED off
blinking
1 Red There is at least one There is at least Not used There is
major fault one minor fault no fault
(hardware, database) (I/O board,
communication to
IEDs, …)
2 yellow All the alarms are All alarms There is at least There is
acknowledged, but displayed in the one not no alarm.
there is at least one alarm panel are acknowledged
alarm still active. inactive and alarm displayed in
acknowledged the alarm panel
NOTE: When the
alarm disappears, the
LED returns
automatically to OFF
3 yellow Computer in service Computer in Computer in test Computer
maintenance in reboot
4 Green Power up is present Not used Not used Power up
is out
5 (Fixed Red All bays managed by Bays managed by Not used All bays
only for the computer are in the computer are managed
without LOCAL mode not in the same by the
LCD panel: control mode computer
GHU2x1) are in
REMOTE
A minor fault is a fault causing only the non-availability of a part of the functionality:
Phenomenon LED status Possible reason Way to solve

Functions like All LEDs are OFF The cable between CPU Verify the connection
communication, and GHU2xx, or between CPU or
automation, printing GHU2xx itself is not GHU2xx.
are well operating operational
If connection is OK and
and the watch dog on
the problem is not
BIU (see chapter
already solved then
C264/EN CO) is
change the GHU2xx
SET.
board.
The supply is ON and All LEDs are OFF Problem with BIU board Replace BIU board or
the watch dog on BIU or CPU board CPU board.
(see chapter
C264/EN CO) is
RESET.
C264 is not running LED1 ON Incoherent database Download a coherent
or not fully database.
operational
Hardware fault Go in Fault panel and
Board panel to
determine the faulty
board and change it.
C264 is not fully LED1 is blinking A IED is disconnected Go into IED panel to
operational determine the
disconnected IED and
verify the cable, the BIU
configuration, the
communication
parameters inside the
PACiS configurator, the
communication
parameters inside the
relay.
The printer is Go into Fault panel and
disconnected verify that paper is
available, the printer is
switch ON, the printer
cable.
A problem about clock Go into Fault panel and
synchronisation verify that the external
clock is switch ON, the
external clock is
connected to the
antenna, the external
clock is connected to the
C264.
A problem about PLC Go into Fault panel and
(ISaGRAF) connect the ISaGRAF
workbench to the C264.
Verify the behaviour of
the PLC.
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 AREVA T&D EAI 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 AREVA 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 (AREVA T&D SAFETY
GUIDE: SFTY/4L M/C11 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 TMU200/TMU220 BOARD
FIGURE 3: MiCOM C264C WITHOUT TMU200/TMU220 BOARD

FIGURE 4: MiCOM C264 WITH TMU200/TMU220 BOARD
FIGURE 5: MiCOM C264 WITHOUT TMU200/TMU220 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)
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, DOU200, CCU200, AIU201, AIU210,
AIU211)
The I/O boards can be located in any slot from C to Q.
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).
An URL is defined to access this webserver. Operator has to know the IP address of the
computer 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,
CCU200 ( if configured and present)
• the status ( valid OPEN / valid CLOSE) of the binary outputs of boards BIU241,
DOU200, CCU200 ( 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 CMT 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. Please report to the IN chapter.
The CMT user guide is also completely described inside the CMT online help.
MiCOM C264/C264C
LEXICAL
CONTENT
2. LEXICAL 4
C264/EN LX/C40 Lexical
BLANK PAGE

This document is a chapter of MiCOM C264 documentation binders. It is the lexical.
2. LEXICAL
AC Alternating Current
A/D Analog/Digital
ADC Analogue to Digital Converter
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.
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..)
ATCC Automatic Tap Change Control
Same as AVR, automation charged to regulate secondary voltage
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 ‘Local Control Display),… Usually associate
with Remote/Local control.
BI Binary Input (or Information)
Name given into Computer C264 of information already filtered,
before it becomes a SPS, DPS… with time tag and quality attributes
BIU Basic Interface Unit
Computer C264 Board for auxiliary power supply, watchdog relay,
redundancy I/O
BNC A connector for coaxial cable.
B-Watch Monitoring and control device for GIS substation.
CAD Computer Aided Design
Computer application dedicated to 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)
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 modelisation 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.
CM
CMT Computer Maintenance Tool
COMTRADE Common Format For Transient Data Exchange ( international
standard IEC 60255-24)
CPU Central Processing Unit
Computer C264 main Board based on PowerPC
CRC Cyclic Redundancy Check
Coding result send with packet of transmitted data to guarantee their
integrity. Usually result of a division of transmitted data by polynomial.
CSV Character Separate Values
ASCII values separated by predefined character or string like in Excel
or ASCII Comtrade.
CT Current Transformer
Basically the electric device connected to process and extracting a
current measurement. By extension part of a device (C264) that
receives AC values and convert it to numerical measurement value.
CT/VT Current and Voltage transformers
(Conventional) By extension, it is the C264 TMU board.
CT/VT Current and Voltage transformers
(Non-Conventional or New generation of captor based for example on light diffraction under
intelligent) electric field, without transformer, that give s directly numerical
measurement of voltage and current like communicating IED.
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.
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.
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
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.
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
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.
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).
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
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
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)
GHU Graphical Human Unit
Front panel of C264 with LCD and buttons
GIS Gas Insulated Substation
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
Group Logical combination of BI (i.e. SP, DP, SI or other groups).
Hand Dressing Facility for an operator to set manually the position of a device
(acquired by other means) from the HMI at SCP level; e.g. from
OPEN to CLOSE (without any impact on the “physical ” position of
the electrical switching device).
HMGA Horizontal Measurement Graphical Area
HMI Human Machine Interface
Can be PACIS OI (Operator Interface) or C264 LCD (Local Control
Display) or Leds, mosaic...
HSR High Speed auto-Recloser
First cycles of AR
HTML Hyper Text Mark-up Language
Used as standard for formatting web display
HV High Voltage (for example 30kV to 150kV)
I/O Input/Output
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 two 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
(Kbus Courier) RS422).
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 AREVA or MODICON
LCD Liquid Crystal Display
Local Control Display
On C264
LD Ladder Diagram
LSB Least Significant Bit
LED Light Emitting Diode
LF Low Frequency
LOC Local Operator Console
Dedicated to maintenance operation
L/R Local / Remote
Local / Remote When set to local for a given control point it means that the
Control Mode commands can be issued from this point, else in remote control are
issue for upper devices.
LV Low Voltage
MAFS Marketing And Functional Specification
MC Modular Computer
MCB Mini Circuit Breaker. Its position is associated to tap changer.
MDIO Management Data Input/Output
A standard driven, dedicated-bus approach that is specified in
IEEE802.3
Measurements Values issued from digital inputs or analogue inputs (with value, state
and time tag).
Metering Values computed depending on the values of digital or analogue
(non-tariff) inputs during variable periods of time (time integration).
Metering Values computed depending on the values of digital or analogue
(tariff) inputs during variable periods and dedicated to the energy tariff.
These values are provided by dedicated “tariff computer ” which are
external to the MiCOM Systems.
MIDOS AREVA Connector: Used for CT/VT acquisition
MMC Medium Modular Computer
ModBus Communication protocol used on secondary networks with IED or
with SCADA RCP. 2 versions exist with standard MODICON or
AREVA one.
Module Word reserved in PACIS SCE for all electric HV devices. It groups all
switch-gears, transformer, motors, generators, capacitors, …
MOTION Transient state of a Double Point

Occurs when the two associated digital inputs are momentarily in
state 0 (e.g. position indication when an electrical device is
switching). The concept of “momentarily” depends on a
user-selectable delay.
MPC Protection Module for Computer
MV Medium Voltage
MVAR Mega Volt Ampere Reactive
NBB Numerical Busbar Protection
NC Normally Closed (for a relay)
NO Normally Open (for a relay)
OBS One Box Solution
Computer that provides protection and control functions with local
HMI. The prime application of this device is intended for use in
substations up to distribution voltage levels, although it may also be
used as backup protection in transmission substations. Likewise, the
OBS may be applied to the MV part of a HV substation that is being
controlled by the same substation control system.
OI Operator Interface
OLE Object Linking and Embedding
OLE is a Microsoft specification and defines standards for interfacing
objects.
OLTC On Line Tap Changing
OPC OLE for process control
OPC is a registered trademark of Microsoft, and is designed to be a
method to allow business management access to plant floor data in a
consistent manner.
Operation hours Sum of time periods, a primary device is running under carrying
energy, e.g. circuit breaker is in Close state and the current is
unequal 0 A.
OSI Open System Interconnection
Split and define communication in 7 layers : physical, link, network,
transport, session, presentation, application
PACiS Protection, Automation and Control Integrated Solutions
PLC Programmable Logic Control
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
PT100 Probes of temperatures providing analogue signals.
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 associate with Remote/Local sub-station
control. It is a SCADA interface managed by the MiCOM system
through Telecontrol BUS. Several RCP’s can be managed with
different protocols.
Remote Control Mode When set for a control point it means that the commands are issued
from an upper level and are not allowed from this point.
Remote HMI Remote HMI is a client of the substation HMI server. The client may
provide all or part of functions handled by the substation HMI.
RI Read Inhibit
This output indicates the availability of an analogue output (e.g.
during DAC converting time)
RJ-45 Registered Jack-45
A 8-pin female connector for 10/100 Base-T Ethernet network
RMS Root Mean Square
RRC Rapid ReClosure
RS-232 Recommended Standard 232
A standard for serial transmission between computers and peripheral
devices.
RS-422 A standard for serial interfaces that extends distances and speeds
beyond RS-232. Is intended for use in multipoint lines.
RS-485 A standard for serial multipoint communication lines. RS-485 allows
more nodes per line than RS-422
RSVC Relocatabled Static Var Compensator
RTC Real Time Clock
RTU Remote Terminal Unit
Stand alone computer that acquires data and transmit them to RCP
or SCADA. Typically it is the C964. RTU link is the TBUS.
SAT Site Acceptance Test
Validation procedures executed with the customer on the site.
SBMC Site Based Maintenance Control mode
A bay in SBMC mode does not take into account the commands
issued from RCP; moreover, some of its digital points and
measurements (defined during the configuration phase) are not sent
anymore to the RCP (they are “ automatically ” suppressed).
SCADA Supervisory Control And Data Acquisition
SCE System Configuration Editor
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
SCP Substation Control Point
Name given to the device or part used to control locally several bays
or sub-station. Usually associate with Remote/Local sub-station
control. It is commonly PACIS Operator Interface.
SCS Substation Control System

SCT Single Counter
Setpoints (analogue) Analogue setpoints are analogue outputs delivered as current loops.
Analogue setpoints are used to send instruction values to the process
or to auxiliary devices.
Setpoints (digital) Digital values sent on multiple parallel wired outputs Each wired
output represent a bit of the value. Digital setpoints are used to send
instruction values to the electrical process or to auxiliary devices.
SFC Sequential Function Chart
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)
SINAD Signal-plus-Noise-plus-Distorsion to Noise-plus-Distorsion ratio.
SINAD is fully expressed in dB.
SOE Sequence Of Events
Other term for the event list.
SP Single Point
SPS Single Point Status
SPC Single Point Control
ST Structured Text
STP Shielded Twisted Pair
Substation computer Bay computer used at substation level.
Suppression A binary information belonging to a bay in SBMC mode will be
(Automatic) automatically suppressed for the remote control. However changes of
state will be signalled locally, at SCP.
Suppression (Manual) A binary information can be suppressed by an order issued from an
operator. No subsequent change of state on a “suppressed
information ” can trigger any action such as display, alarm and
transmission.
SWR Switch Redundant
Computer C264 board Ethernet switch with redundant Ethernet
SWU Switch Unit
Computer C264 board Ethernet switch
T101 Term used for IEC60870-5-101 protocol
TBC To Be Completed
TBD To Be 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
The total demand distortion is similar to the THD but applied to
currents and with a rated current (In) as reference
THD Total Harmonic Distorsion
The total harmonic distortion represents the sum of all voltage
harmonics
TMU Transducerless Measurement Unit
Topological Interlocking algorithm, based on evaluation of topological information
interlocking of the switchgear arrangement in the HV network, the switchgear kind
and position, and defined rules for controlling this kind of switch (e.g.
continuity of power supply)
TPI Tap Position Indication (for transformers).
Frequently acquired via a Digital Measurement
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)
VDEW Term used for IEC60870-5-103 protocol
VMGA Vertical Measurement Graphical Area
Voltage level Set of bays whose plants and devices are dealing with the same
voltage (e.g. 275kV, 400 kV).
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.
WYE Three phases + neutral AI values
ANNEX C264/EN AN/C40
MiCOM C264/C264C
ANNEX:
COMMUNICATION
ETHERNET SWITCHES
Annex: SW Communication C264/EN AN/C40
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 - 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 AREVA T&D 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/C40 Annex: SW Communication
3.5 SWD21x Leds 14

3.5.1 LEDs 15
3.6 Settings 15
4. SWU20X RANGE - STAR ARCHITECTURE 16

4.1 Ethernet Port Characteristics 16
4.1.1 10/100BaseTx Port 16
4.1.2 100BaseFx Multi Mode Port 16
4.1.3 100BaseFx Single or Mono Mode Port 16
4.2 Ethernet Port Switching Features 17
4.2.1 10BaseTx and 100BaseTx 17
4.2.2 100Base Fx 17
4.3 Ethernet Management 17
4.3.1 Address look up 17
4.3.2 Buffering 17
4.3.3 Back off operation 17
4.3.4 Back pressure for half duplex 17
4.3.5 Broadcast storm protection 17
4.3.6 Auto Negotiation and Speed-Sensing 17
4.3.7 Forwarding 17
4.3.8 Priority tagging 17
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.
AREVA T&D 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, AREVA T&D has designed and still
developing a complete range of products that communicate via Ethernet links.
Electric plant requirements leads 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 has been specially tailored for
the PACiS system. The MiCOM Hxxx 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 - RING ARCHITECTURE

The SWR21x range is dedicated for fast redundant Ethernet ring and defined by the type of
Ethernet optical fibre support. All equipment of the SWR21 range has 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
between 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 1310 nm 2 x ST
(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 AREVA T&D 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 AREVA T&D 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 AREVA’ ring. The AREVA 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 AREVA repeter
3 sysUpTime xday yh:zm:zzs:yyms
4 sysName
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
7 and 8: ports for redundant ring
Private:
Address Name
0 Ccitt
1 ISO
3 Org
6 DOD
1 Internet
4 private
1 enterprises
22006 AREVA T&D
1 EAI
2 MiCOM
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
AREVA MIB in AREVA 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.
Front Panel Rear Panel
J10:
Adress of
repeater
J12:
Reserved
C0424ENa
2.3.1 LEDs
LED N° Color Description

E1 default L1 Red Seal Heating on RsEp
Link Rp L2 green Rp (Reception Primary) Link OK
Receive Rp L3 Green Traffic detected
E2 default L4 Red Seal Heating RpEs
Link Rs L5 Green Link
Receive Rs L6 Green Traffic detected
Number of repeater detected on the ring bit 0 L7 Green
Link and activity port 1 L15 Green Off: no connection
Green: link
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 :

between 1 and 127.
2.4.3 How to configure the address ?
Example :
Address = 11
2.4.4 IP Address of the repeater

The repeater IP address is accomplished in the following way:
Always 254
123.086.254.045
IP Network Base Repeater number

C0422ENa
FIGURE 5: IP ADDRESS
Note: It is important to note that the AREVA_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 SWR21x 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 1310 nm 2 x ST

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

1 2
« Dual Homing » B1
Links A et B A2 B2
A1
SWITCH SWITCH
Network A Network B
Dual Homing
Dual Homing 4
3
Main Links
3
C0423ENa
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

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
Link and activity port 1 L15 Green Off: no connection
Green: link
Speed port 1 L20 Green Off: 10Mbps
Green: 100Mbps
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.
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 1310 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
Center wavelength 1310 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.
Publication: C264/EN T/C40
AREVA T&D's Automation & Information Systems Business www.areva-td.com

T&D Worldwide Contact Centre online 24 hours a day: +44 (0) 1785 25 00 70 http://www.areva-td.com/contactcentre/

c264 en T c40 Global

Uploaded by

Copyright:

Available Formats

c264 en T c40 Global

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

c264 en T c40 Global

Uploaded by

Copyright:

Available Formats

MiCOM

MiCOM C264/C264C Page 1/2

Safety & Handling C264/EN SA/C40

Introduction C264/EN IT/C40

Technical data C264/EN TD/C40

Functional Description C264/EN FT/C40

Hardware Description C264/EN HW/C40

Connection C264/EN CO/C40

Installation C264/EN IN/C40

Settings C264/EN ST/C40

Commissioning C264/EN CM/C40

Commissioning Record Sheet C264/EN RS/C40

Maintenance C264/EN MF/C40

Lexical C264/EN LX/C40

ANNEX: Communication ETHERNET Switches C264/EN AN/C40

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 AREVA T&D EAI PRODUCTS 12

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 AREVA T&D EAI 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.