Schneider Micom C264C - Tech Guide PDF

MiCOM
C264/C264C
Bay Computer
Technical Guide
C264/EN T/A14
Technical Guide C264/EN T/A14
MiCOM C264/C264C Page 1/2
MiCOM C264/C264C
BAY COMPUTER
CONTENT
Safety & Handling C264/EN SA/A14
Introduction C264/EN IT/A13
Technical data C264/EN TD/A13
Functionnal Description C264/EN FT/A13
Hardware Description C264/EN HW/A13
Connection C264/EN CO/A14
Installation C264/EN IN/A13
Application C264/EN AP/A13
Settings C264/EN ST/A13
Logic Diagrams C264/EN LG/A13
Communications C264/EN CT/A13
Commissioning C264/EN CM/A13
Commissioning Record Sheet C264/EN RS/A13
Maintenance C264/EN MF/A13
Lexical C264/EN LX/A13

C264/EN T/A14 Technical Guide
Page 2/2 MiCOM C264
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. GUARANTIES 10
8. COPYRIGHTS & TRADEMARKS 11

8.1 Copyrights 11
8.2 Trademarks 11
9. WARNINGS REGARDING USE OF T&D EAI PRODUCTS 12

C264/EN SA/A14 Safety & Handling
Page 2/12 MiCOM C264/C264C
BLANK PAGE
1. INTRODUCTION
This document is a chapter of the MiCOM C264C/C264 documentation binder. It describes
the safety, handling, packing and unpacking procedures applicable to MiCOM C264C/C264
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/D11
(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.5 mm², 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,
Red Spot type of equipment, unless otherwise stated in the technical data section of the
product documentation.
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…)
Insulation class IEC 601010-1: 1990/A2: 1995 This equipment

requires a protective
Class I
(safety) earth
EN 61010-1: 1993/A2: connection to ensure
user safety.
Class I
Insulation Category IEC 601010-1: 1990/A2: 1995 Distribution level, fixed
(Overvoltage): installation.
Class III
EN 61010-1: 1993/A2: Equipment in this
category is
Class III
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 601010-1: 1990/A2: 1995 Compliance is
demonstrated by
Pollution degree 2
reference to generic
EN 61010-1: 1993/A2: safety standards.
Pollution degree 2
Product Safety: 72/23/EEC Compliance with the
European Commission
Law Voltage Directive.
EN 61010-1: 1993/A2: 1995 Compliance is
demonstrated by
EN 60950: 1992/A11: 1997
reference to generic
safety standards.
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 T&D 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, you must be 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.
T&D 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 Cx64/Cx64C 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. GUARANTIES
The media on which you received T&D software are guaranted 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
will, at its option, repair or replace software media that do net execute programming
instructions if AREVA T&D receive notice of such defects during the guarantee period. T&D
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 guarantee work. AREVA T&D
will pay the shipping costs of returning to the owner parts, which are covered by warranty.
AREVA T&D 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, T&D 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 if errors are suspected. In no event shall AREVA T&D 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 makes no guarantees, express or implied and
specifically disclaims and guarantees of merchantability or fitness for a particular purpose.
Customer's rights to recover damages caused by fault or negligence on the part T&D shall
be limited to the amount therefore paid by the customer. AREVA T&D 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 will apply regardless of the form of action, whether in contract or tort, including
negligence. Any action against AREVA T&D must be brought within one year after the cause
of action accrues. T&D shall not be liable for any delay in performance due to causes
beyond its reasonable control. The warranty provided herein dues net cover damages,
defects, malfunctions, or service failures caused by owner's failure to follow the AREVA T&D
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 T&D.
8.2 Trademarks
PACiS, PACiS SCE, PACiS ES, PACiS SMT, PACiS PS, PACiS SCE, AREVA T&D,
pacis.biz and pacis.com- are trademarks of AREVA T&D. Product and company names
mentioned herein are trademarks or trade names of their respective companies.
9. WARNINGS REGARDING USE OF T&D EAI PRODUCTS

AREVA T&D products are not designed with components and testing for a level of reliability
suitable for use in or 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 testing platforms but also a user or
application designer may use T&D products in combination with other products. These
actions cannot be evaluated or contemplated by AREVA T&D; Thus, the user or application
designer is ultimately responsible for verifying and validating the suitability of AREVA T&D
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 Functional Description (FT) 4
2.1.4 Chapter Technical Data (TD) 4
2.1.5 Chapter Communications (CT) 4
2.1.6 Chapter HMI, Local control and user interface (HI) 4
2.1.7 Chapter Installation (IN) 4
2.1.8 Chapter Hardware Description (HW) 4
2.1.9 Chapter Connection diagrams (CO) 4
2.1.10 Chapter Commissioning (CM) 5
2.1.11 Chapter Commissioning record sheet (RS) 5
2.1.12 Chapter Logic diagrams (LG) 5
2.1.13 Chapter Applications (AP) 5
2.1.14 Chapter Settings (ST) 5
2.1.15 Chapter Maintenance, Fault finding, Repairs (MF) 5
2.1.16 Chapter Problem analysis (PR) 5
2.1.17 Chapter Lexical (LX) 5
2.2 Operation guide 5
2.3 Technical guide 5
2.4 Getting Started guide 5
3. INTRODUCTION TO MiCOM APPLICATIONS 6

3.1 MiCOM Computers 6
3.2 Applications and Scope 6
C264/EN IT/A13 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.
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.

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 guides is 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 Cx64/x64
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 Functional Description (FT)
This chapter contains a description of the product. It describes functions of the MiCOM
computer.
2.1.4 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.5 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.6 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.7 Chapter Installation (IN)
This chapter contains the installation procedures.
2.1.8 Chapter Hardware Description (HW)
This chapter contains the hardware product description (product identification, case,
electronic boards, operator interface, etc.).
2.1.9 Chapter Connection diagrams (CO)
This chapter contains the external wiring connections to the Cx64 computer.
2.1.10 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.11 Chapter Commissioning record sheet (RS)
This chapter provides detailed record sheets to commission the computer.
Chapters used in application conception
2.1.12 Chapter Logic diagrams (LG)
This chapter contains the Logic function description, the description of logic and automation
tool, Built in functions and controls.
2.1.13 Chapter Applications (AP)
Comprehensive and detailed description of the features of the MiCOM C264/264 including
both the computer elements and the other functions such as transducerless (CT/VT)
measurements, events and disturbance recording, power quality, 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.
CHAPTERS ON MAINTENANCE
2.1.14 Chapter Settings (ST)
This chapter contains the list of the setting with defaults values and range.
2.1.15 Chapter Maintenance, Fault finding, Repairs (MF)
This chapter advice on how to recognise failure modes, fault codes and describes the
recommended actions to repair.
2.1.16 Chapter Problem analysis (PR)
This chapter advice on practical examples of problem solving and the company contact
information. It includes all information on the self-checking features and diagnostics of the
MiCOM Cx64/Cx64C computer.
2.1.17 Chapter Lexical (LX)
This chapter contains lexical description of acronyms and definitions.
2.2 Operation guide
This binder contains the following chapters:
SA, TD, IT, HW, LG, AP, FT, LX
2.3 Technical guide
SA, TD, IT, HW, CO, IN, HI, ST, LG, CT, CM, RS, MF, PR, FT, LX
2.4 Getting Started guide
SA, TD, IT, HW, CO, IN, HI, ST, PR, FT, LX
3. INTRODUCTION TO MiCOM APPLICATIONS

MiCOM C264/C264C computer range is designed to address the needs of a wide range of
installations, from small to medium 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.
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) 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 and new range of computers products, MiCOM Cxxx 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.
These new generations of computers, the MiCOM C264/C264C have been specially tailored
for the PACiS system. A major objective, of the MiCOM C264/C264C range is to make the
range as easy as possible for the customer to accept, adapt and integrate into his system
and operation.
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.
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.
Key features are that this computer family is based on a UCA2 client/server architecture, it is
a modular computer that offers a large variety of applications such as Bay Computer,
Remote Terminal Unit and Programmable Logic Controller.
3.2 Applications and Scope
The MiCOM C264/264C modular bay controller, RTU or PLC is used to control and monitor
switchbays. The information capacity of the MiCOM C264/264C is designed for controlling
up to 24 electrically 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). To simplify the setting of parameters, a number of different
bay types with defined default settings are stored in the MiCOM C264/264C memory. The
bay type corresponding to the bay being controlled can then be permanently set. The
operator can select the bay type and adjust individual default parameters to correspond to
the particular functions required. If a specific bay type is not included, it can be created on
request and loaded into the MiCOM C264/264C.
The MiCOM C264/264C can be connected to a higher control levels, local control level or
lower levels by way of a built-in communications interface.
FIGURE 1: TYPICAL USE OF A MiCOM C264 – BAY CONTROLLER

FIGURE 2: TYPICAL USE OF A MiCOM C264 – RTU APPLICATION

The figures above only show typical cases that can be mixed to handle specific constraints.
Two examples illustrate this case:
• System application like figure 1 might use several C264 with several communication
links to SCADA (one per level of voltage for example) in order to greatly enlarge the
number of communication links to SCADA.
• RTU applications can use several C264 linked (via SBUS Ethernet UCA2 as in FIG 1) to
a C264 RTU as a single communication port with SCADA (when it is not necessary to
use a separate PACiS Gateway).
Technical Data C264/EN TD/A13
MiCOM C264/C264C
TECHNICAL DATA
CONTENT
1. SCOPE OF THE DOCUMENT 3
2. CONFORMITY 3
3. GENERAL DATA 3
3.1 Design 3
3.2 Installation Position 3
3.3 Degree of Protection 3
3.4 Weight 3
3.5 Dimensions and Connections 3
3.6 Terminals 3
3.7 Creepage Distances and Clearances 4
4. RATINGS 5
4.1 Auxiliary Voltage 5
4.2 Digital inputs 5
4.3 Digital outputs 6
4.3.1 DOU200 6
4.3.2 CCU200 6
4.3.3 BIU241 7
4.4 Analogue inputs 7
4.5 CT/VT inputs 7
4.5.1 Currents 7
4.5.2 Voltages 8
4.5.3 A/D converter 8
5. BURDENS 9
5.1 Auxiliary Voltage 9
5.2 Digital inputs 9
5.3 Digital outputs 9
5.3.1 DOU200 9
5.3.2 CCU200 10
5.4 Analogue inputs 10
5.5 CT / VT inputs 10
5.5.1 Currents 10
C264/EN TD/A13 Technical Data
6. ACCURACY 11
6.1 Reference Conditions 11
6.2 Measurement Accuracy 11
7. TYPE TESTS 12
7.1 Dielectric Withstand 12
7.2 Mechanical Test 12
7.3 Atmospheric Test 13
7.4 “DC” Auxiliary Supply Test 13
7.5 “AC” Auxiliary Supply Test 14
7.6 EMC 14
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 72/73/EC.)
The product designated “MiCOM C264/C264C computer” has been designed and
manufactured in conformance with the European standards EN 60255-6 and EN 61010-1
and with the ‘EMC Directive’ and the ‘Low Voltage Directive’ issued by the Council of the
European Community.
3. GENERAL DATA
3.1 Design
Surface-mounted case suitable for wall installation or flush-mounted case for 19” cabinets
and for control panels.
3.2 Installation Position
Vertical ±15°.
3.3 Degree of Protection
Per DIN VDE 0470 and EN 60529 or IEC 60529.
IP51 for the front plane for both MiCOM C264C and MiCOM C264.
IP51 for the rack of the MiCOM C264C modular computer.
IP20 for the rack of the MiCOM C264 modular computer.
3.4 Weight
Case 40 TE: approx. 4 kg
Case 80 TE: approx. 8 kg
3.5 Dimensions and Connections
See dimensional drawings in the chapter C264/EN HW and terminal connection diagrams in
the chapter C264/EN CO.
3.6 Terminals
PC Interface:
DIN 41652 connector, type D-Sub, 9-pin on the front panel.
A special connecting 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 fibbers (trough external RS232/optical converter): optical plastic fibber connection
per IEC 874-2 or DIN 47258 or ST ® glass fibber optic connection (ST ® is a registered
trademark of AT&T Lightguide Cable Connectors)
Inputs and Outputs modules:

M3 threaded terminal ends, self-centring with wire protection for conductor cross sections
from 0.2 to 2.5 mm² for BIU241 (power supply board), DIU200, DOU200, CCU200 and
AIU200 (I/O) boards.
The I/O boards are equipped with a 24-way 5.08 mm pitch male connector:
Entrelec L 255 324 01 000/24-G-5.08
Can be equipped with other compatible connector.
Current-measuring and Voltage-measuring inputs:

M5 threaded terminal ends, self-centring with wire protection for conductor cross sections :
2 * 2.5 mm² for VT connection
2 * 2.5 mm² or 1 * 4 mm² for CT connection
The Transducerless (4CT+4VT) board is equipped with a “MICOM: ASSEMBLY
CONNECTEUR BLOCKL GJ104” connector.
3.7 Creepage Distances and Clearances
Per EN 61010-1 and IEC 664-1.
Pollution degree 3, working voltage 250 V.
Overvoltage category III, impulse test voltage 5 kV.
4. RATINGS
4.1 Auxiliary Voltage
Tanks to the BIU241 board, the MiCOM C264C/C264 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 20 – 72 V -
A03 110 to 125 VDC 88 – 132 V -
A04 110 to 220 VDC and 176 – 264 V 92 – 276 V
150 to 230VAC
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Ω at 500 VDC
• Dielectric withstand: 2 kV – 50/60 Hz during 1min

4.2 Digital inputs
The DIU200 board is available in four nominal wetting voltage versions that characteristics
are specified in the table below:
Version Nominal wetting voltage (+/-20%) Triggering threshold (VDC)

A01 24 VDC 5 to 10.1
A02 48 to 60 VDC 13.5 to 17.4
A03 110 to 125 VDC 34.4 to 50
A04 220 VDC 63 to 108
4.3 Digital outputs

4.3.1 DOU200
The characteristics of the Output Relay Contacts of the DOU200 board are specified in the
table below:
Features Values
External operating Voltage (UN) ±24 to ±250 VDC
230 VAC – 50/60Hz
Make and Carry 2.5 A in continuous
30 A for 500 ms
100 A for 30 ms
Break (in VDC) Resistive load:
50 W
Inductive load (L/R=20ms):
15 W
Break (in VAC) 250 V – 2.5 A - cos. phi > 0.6
Maximum 2.5 A and 300 V
Loaded contact 10.000 operations minimum
Unloaded contact 100.000 operations minimum
Operating time < 7ms
• Isolation: 2 kV – 50 Hz between coil and contacts
• The +5V voltage is monitored to avoid issuing inadvertent controls.
4.3.2 CCU200
The CCU200 board is available in four nominal wetting voltage versions, specified in the
table below:
Version Wetting voltage (+/-20%) Operating range Consumption

A01 24 VDC 19.2 – 28.8 VDC 8 mA
A02 48 to 60 VDC 20 – 72 VDC 5 mA
A03 110 to 125 VDC 38.4 – 132 VDC 3 mA
A04 220 VDC 176 – 264 VDC 2 mA
The characteristics of the Output Relay Contacts of the CCU200 board are specified in the
table below. Each relay of the CCU board has double pole contacts. To have the
characteristics described below, the two contact outputs are to be wired in serial.
Features Values
External operating Voltage (UN) ±24 to ±250 VDC
230 VAC – 50/60Hz
Make and Carry 5 A in continuous
15 A for 4s
250 A for 30 ms
Break (in VDC) Resistive load:
100 W
Inductive load (L/R=’0ms):
30 W
Features Values
Break (in VAC) 250 V – 8 A - cos. phi > 0.6
Maximum 15 A and 300 V
Loaded contact 10,000 operations minimum
Unloaded contact 100,000 operations minimum
Operating time < 7ms
• The +5V voltage is monitored to avoid issuing inadvertent controls.
4.3.3 BIU241
The characteristics of the Output Relay Contacts of the BIU241 board are the same as the
DOU200 board.
4.4 Analogue inputs
The AIU200 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
Currents ± 1mA, 0-1 mA
± 2 mA, 0-2 mA
± 5 mA, 0-5 mA
± 10 mA, 0-10mA
± 20 mA, 0-20mA
4-20 mA
Voltages ±1V
± 2.5 V
±5V
± 10V
The main features of the AIU200 board are specified in the table below:
Features Values
Resolution A/D Converter 16-bit (15 bits + sign)
Sampling period <40 ms
Serial mode rejection ratio (SMMR) >40 dB at 50 / 60 Hz
Common mode rejection ratio (CMMR) >100 dB at 50 / 60 Hz
Linearity error ± 2 LSB
4.5 CT/VT inputs (TMU 200)

4.5.1 Currents
The same terminal is provided for the 1A and 5A windings.
The four measurement Current Transformers (4 CT) inputs have the following
characteristics:
Operating range
Features
1A 5A
Nominal AC current (IN) 1 Aeff 5 Aeff
Minimum measurable current 0.01 Aeff 0.05 Aeff
Maximum measurable current 4 Aeff 20 Aeff
Frequency 50 or 60 Hz ± 10% 50 or 60 Hz ± 10%
CT load rating:
Withstand
Duration
1A 5A
3 second (not measurable on board, without 6 Aeff 30 Aeff
destruction)
1 second (not measurable on board, without 20 Aeff 100 Aeff
destruction)
4.5.2 Voltages
The four measurement Voltage Transformers (4 VT) inputs have the following
characteristics:
Features Operating range

Nominal AC voltage (VN) 57.73 Veff to 500 Veff .
Minimum measurable voltage 5.773 Veff
Maximum measurable voltage 636 Veff
Frequency operating range 50 or 60 Hz ± 10%
VT load rating:
Duration Withstand
10 second measurable without destruction 880 Veff
4.5.3 A/D converter

The A/D converter of the TMU200 board has the following characteristics:
Features Values
Width 16 bits
Conversion period < 30 µs
Scanning period 64 samples/period
Linearity error ± 2 LSB
SINAD ratio > 80 dB at operating range
Isolation 2 kV at 50Hz
5. BURDENS
5.1 Auxiliary Voltage
The MiCOM C264C/C264 computer burdens are specified in the table below:
Version Case size Nominal1 Maximum2

A01 C264C (4U – 40TE) 12VA DC 13W AC 17VA DC 17W AC
24 VDC
48 to 60 VDC
A03 C264C (4U – 40TE)
110 to 125 VDC
110 to 220 VDC and
115 to 230 VAC
A01 C264 (4U – 80TE) 30VA DC 31W AC 39VA DC 39W AC
24 VDC
A02 C264 (4U – 80TE) 35VA DC 36W AC - -
48 to 60 VDC
A03 C264 (4U – 80TE)
110 to 125 VDC
A04 C264 (4U – 80TE) 39VA DC 40W AC - -
110 to 220 VDC and
115 to 230 VAC
5.2 Digital inputs

The DIU200 board burdens are specified in the table below:
Nominal wetting Consumption (W)

Version Current at Un (mA)
voltage (+/-20%) per DI (wetting)
A01 24 VDC 3.5 0.15
A02 48 to 60 VDC 5 for 48 VDC 0.64
6.8 for 60 VDC
A03 110 to 125 VDC 2.5 for110 VDC 0.59
3 for 125 VDC
A04 220 VDC 2 0.7
5.3 Digital outputs

5.3.1 DOU200
The DOU200 board burdens are specified in the table below:
Consumption (W)
Nominal voltage (+/-20%) Current at Un (mA)
per board
220 V 1.2 1.25
1
Nominal is with 50% of the DI energized and one relay per board energized.
2
Maximum is with all DI and all relays energized.
5.3.2 CCU200
The CCU200 board burdens are specified in the table below:
Nominal3 Maximum4 consumption

Nominal wetting voltage (+/-
Version consumption (W) (W)
20%)
per board per board
A01 24 VDC 1.4 3
A02 48 to 60 VDC 1.8 3.6
A03 110 to 125 VDC 2.1 4.2
A04 220 VDC 2.6 5.2
5.4 Analogue inputs

The burden per AIU200 board is 5W approximately.
5.5 CT / VT inputs
5.5.1 Currents
The TCU200 card burdens are specified in the table below:
CT burden (at nominal current – IN) Nominal consumption (VA)

1A <0.15
5A <0.75
The TVU200 card burdens are specified in the table below:
VT burden (at nominal voltage – VN ) Nominal consumption (VA)

Vn = 130 Veff <0.1
3
Nominal is with 50% of the DI energized and one relay per board energized.
4
Maximum is with all DI and all relays energized.
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 DC 48V or 110V ±5%
AC 67.8 or 155.5V
6.2 Measurement Accuracy

The TMU200 board has the following characteristics:
Quantity Accuracy
Current 0.2% full scale (at 25 °C)
Voltage 0.2% full scale (at 25 °C)
Frequency ± 0.025 Hz
Amplitude < 1%
Phase ± 1°
Overall temperature coefficient ± 10 ppm/°C
Harmonics Up to 15th
7. TYPE TESTS
7.1 Dielectric Withstand
Type Test Name Type Test Standard Conditions

Insulation Resistance IEC 60255-5 100 MΩ at 500 Vdc (CM & DM)
Dielectric Withstand IEC60255-5 50 Hz, 1mn, 2kV (CM), 1kV (DM)
IEEE C37.90
High Voltage Impulse Test IEC 60255-5 5 kV CM & 3 kV DM(1)
7.2 Mechanical Test

Free Fall Test IEC 60068-2-31 2 falls of 5 cm (Computer not powered)
Free Fall Packaging Test IEC 60068-2-32
25 falls of 50 cm (1) (2) (Packaging computer)
Vibration Response – IEC 60255-21-1 Class 2:
Powered On
Acceleration: 1g from 10 (1) to 150Hz
Vibration Response – Not IEC 60255-21-1 Class 2:
Powered On
Vibration Endurance – Not IEC 80068-2-6 Class 2:
Powered On
Shocks – Not Powered On IEC 60255-21-2 Class 1:
15g, 11 ms
Shocks – Powered On IEC 60255-21-2 Class 2:
10g, 11 ms
Bump Test – Not Powered IEC 60255-21-2 Class 1:
On
10g, 16ms, 2000/axis
Seismic Test – Powered On IEC 60255-21-3 Class 2:
Acceleration: 2g
Displacement: 7.5mm horizontal
Acceleration: 1g
Displacement: 3.5mm vertical V
7.3 Atmospheric Test

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

Operating
Dry Heat Test – Storage IEC 60068-2-1 Test Bd:

+70°C / 96h
Powered On at +70°C
Enclosure Protection IEC 60529
Front: IP=52
7.4 “DC” Auxiliary Supply Test

Inrush current (start-up) DICOT HN 46-R01-4 T < 1.5 ms / I < 20 A
T < 150 ms / I < 10 A
T > 500 ms / I < 1.2 In
Supply variation IEC 60255-6 Vn ± 20%
Vn+30% & Vn-25% for information
Overvoltage (peak IEC 60255-6 1.32 Vn max
withstand)
2 Vn during 10 ms (for information)
Ramp down to zero / From Vn down to 0 within 1 minute
From Vn down to 0 within 100 minutes
Ramp up from zero / From 0 up to Vn within 1 minute
From 0 up to Vn within 100 minutes
Supply interruption IEC 60255-11 From 2.5 ms to 1 s at 0.8 Vn
50 ms at Vn, no malfunction (for information)
Reverse polarity / Polarity – for the lower potential of the supply
Polarity + for the lower potential of the supply
Ripple (frequency IEC 60255-11 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 Vn ± 20%
AC Voltage dips & short EN 61000-4-11 2ms to 20ms & 50ms to 1s
interruptions
50 ms at Vn, no malfunction (for information
Frequency fluctuations IEC 60255-6 50 Hz: from 47 to 54 Hz
60 Hz: from 57 to 63 Hz
Voltage withstand / 2 Vn during 10 ms (for information)
7.6 EMC

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

IEC 61000-4-2 8kV contact / 15 kV air
Radiated Immunity IEC 60255-22-3 Class 3:
IEC 61000-4-3 10 V/m – 80 to 1000 Hz
and 1600 to 2000 Hz
IEEE C37.90.2 & spot tests
35 V/m – 25 to 1000 MHz
Fast Transient Burst IEC 60255-22-4 Class 4:
IEC 61000-4-4 4kV – 2.5kHz (CM)
IEEE C37.90.1
Surge immunity IEC 61000-4-5 Class 4:
4kV (CM) – 2kV (DM)
Class 3:
2kV (CM) – 1 kV (DM)
High frequency conducted IEC 61000-4-6 Class 3:
immunity
10 V, 0.15 – 80 MHz
Harmonics Immunity IEC 61000-4-7 5% & 10% de H2 à H17
Power Frequency Magnetic IEC 61000-4-8 Class 5:
Field Immunity
100A/m for 1mn
1000A/m for 3s
Pulse magnetic field IEC 61000-4-9 Class 5:
immunity
6.4 / 16 µs
1000A/m for 3s
Damped oscillatory magneic IEC 61000-4-10 Class 5:
field immunity
100 kHz & 1 MHz – 100A/m

Power Frequency IEC 61000-4-16 CM 500 V / DM 250 V via 0.1 µF
Conducted emission EN 55022 Gr. I, class A : from 0.15 to 30 MHz
Radiated emission EN 55022 Gr. I, class A : from 30 to 1000 MHz, 10m
BLANK PAGE
Functional Description C264/EN FT/A13
MiCOM C264/C264C
FUNCTIONAL DESCRIPTION
CONTENT

1.1 Software features 5
2. DIRECT PROCESS INTERFACE 7

2.1 Input Check 7
2.2 Output check 7
2.3 Time tagging 7
3. MiCOM C264/C264C MANAGEMENT 8

3.1 Mode management 8
3.1.1 Operating Mode management 8
3.1.2 Redundancy Mode management 8
3.2 Database management 8
3.3 Self tests 8
3.4 Time management 9
3.4.1 External clock 9
3.4.2 Clock message from a SCADA gateway 9
3.4.3 System master clock 10
3.4.4 Time set by an operator 10
4. COMMUNICATIONS 11
4.1 Telecontrol bus 11
4.2 Station bus 12
4.3 Legacy bus 12
4.4 SBUS PROTOCOL 13
4.4.1 UCA2 exchanges 13
4.4.2 UCA2 supported Common Class 13
4.4.3 UCA2 Controls 13
5. DIRECT PROCESS ACCESS 14

5.1 Digital input acquisition (DI) 14
5.2 Analogue input acquisition (AI) 14
5.3 Counters acquisition (CT) 14
5.4 Digital measurement (DM) 14
5.5 Digital outputs (DO) 14
C264/EN FT/A13 Functional Description
6. DATA PROCESSING 15
6.1 Binary Input Processing 15
6.1.1 Binary Input Acquisition 15
6.1.2 Binary Input Definition 15
6.1.3 Processing of Single Point Status 15
6.1.4 Processing of Double Point Status 16
6.1.5 Group processing 17
6.2 Processing of Multi Point Status 17
6.3 Measurement Input Processing 18
6.3.1 Analogue processing 18
6.3.2 CT/VT additional processing 19
6.3.3 Digital Measurement Processing 19
6.4 Accumulator Input Processing 19
7. CONTROL SEQUENCES 20
7.1 Type of control sequences 20
7.2 Control sequences checks 20
7.3 Operational Modes 21
7.4 Interlocking 21
7.5 Control Bypass 21
7.6 HV Control Sequences 22
7.6.1 Control of circuit breaker 22
7.6.2 Control of Isolator 22
7.6.3 Transformer control sequence 22
8. AUTOMATION 23
8.1 Build-in Automation functions 23
8.1.1 Synchrocheck 23
8.1.2 Auto-Recloser (AR) 25
8.1.3 Trip Circuit supervision 26
8.1.4 Automatic Voltage Regulation (AVR) 27
8.2 Fast automation (PSL) 29
8.2.1 Settable inputs of the PSL 31
8.2.2 Timers 31
8.2.3 Programmable gates 33
8.3 Configurable automation (PLC) 33
9. USER INTERFACE 35
9.1 Front Panel 35
9.2 LED’s Management 36
9.3 Local Control Display 36
9.4 Local/Remote push-button 36
9.5 Front serial Link 36
10. RECORDS 37
10.1 Permanent records storage 37
10.1.1 Data storage 37
10.1.2 Fast Waveform Recording 37
10.1.3 Disturbance Recording 38
10.2 Non-permanent data storage 40
10.2.1 Events 40
10.2.2 Alarm function 40
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
(Hardware) chapter and all connection diagrams in chapter CO. The product capabilities,
performances, environmental limits are grouped in TD (Technical Data) chapter.
1.1 Software features
The MiCOM C264/C264C computers belong to the new range of modular product at
hardware, software and functional levels. All functions are fully configurable following
customer needs and requirements. MiCOM C264/C264C computers assume:
• Direct Process interface through DIs, DOs, AIs, and CT/VTs boards
• Direct operator interface
• Embedded parameterised control of all common plant or device
• Excellent communication abilities to IED, Ethernet, and RTU
• User configurable automation modules
• Events, alarms, measurement display,
• Enhanced inner management with databases handling, self-test controls and

synchronisation means
RTU, SCADA PACiS System, UCA2 IED
T-BUS S-BUS
Telecontrol UCA2
Interface 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
C0003ENa
FIGURE 1: SOFTWARE FEATURES

The components of the software management are:
• Inputs/Outputs board (DI, DO, AI)
• Analogue Inputs (from CT/VT board - optional)
• Automatic functions (Build-in, PLC, PSL)
• Communications with TBus, SBus and LBus (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. DIRECT PROCESS INTERFACE

Several kind of boards can be used in MiCOM C264 and C264C. Digital Input & Outputs,
Measurement acquisitions are checked to validate information/action and time tagged on any
change of state or value.
2.1 Input Check
Input data coming from the physical MiCOM C264 boards or from the different
communication networks are periodically checked. Invalidity status of this data is internally
determined 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 sample)
• Over-range (AI, saturation of its transducer, or Counter value reaching limits)
• Open Circuit (AI kind 4-20 mA with current value under 4mA)
• Undefined (Digital Measurement or Counter with invalid DI coding)

2.2 Output check
Output boards are periodically checked at their logical level. In the event of a logical circuit
test fail the board is set faulty. Controls on this board or upon disconnected IEDs are
disabled.
2.3 Time tagging
All physical input data are time tagged at 1 ms accuracy. All internal logic data are time
stamped at 1 ms accuracy.
Analogues acquisition time tagging is done but driven by periodic polling of this kind of
board. Periods are based on multiple of 100ms for Direct Current/Voltage Acquisition.
Alternating Current/voltage from CT/VT acquisition is based on fundamental frequency
(50/60 Hz).
(Standard DI, DO, AI, and CT/VT acquisition)
• Embedded parameterised control of all common plant or device
• Direct operator interface
• Excellent communication abilities to IED, Ethernet, and RTU
• User configurable automations
• Events, alarms, measurement display, printing and archiving
• Enhanced inner management with databases handling, self-test controls and

synchronisation means
3. MiCOM C264/C264C MANAGEMENT

The computer manages its own mode, configuration (Data Bases), and time.
3.1 Mode management
3.1.1 Operating Mode management
The available operating modes on the computer are:
Operational: the equipment is working correctly (all the functions are executed)
Test: Computer is operational but DO are not set
Standby: Computer is operational, transmits supervisory data, but controls are disabled (this
mode is linked to computer redundancy management)
Maintenance: operator has requested this mode to switch between data bases
Faulty: the computer has detected a self test failure, it works but is degraded
Halt: the equipment is out of service
3.1.2 Redundancy Mode management
Equipment redundancy is managed using two identical computers with the same hardware
and data base. To manage conflict cases, especially at start-up, one is configured as main
and the other as backup. In run-time one is active, the other is in standby. Both units are
wired to each other, once the master fails the standby computer becomes operational.
3.2 Database management
The MiCOM Cx64 uses structured databases to store its application data and not setting
arrays. Databases are generated and versioned by PACIS SCE (System Configuration
Editor).
Computer stores 2 different databases, the current (used in real time) and a standby with
different DB versions. A standby DB can be downloaded when computer is operational using
PACIS SMT (System Management Tool).
A switch database control from SMT allows changing of the current database. The computer
will reboot to take in account the new structured data. A fundamental principle is that the
computer can only work with other computers if their current database versions are identical.
Note that the SMT can also upload a database from a computer if this database has had
some parameters changed via its LCD.
3.3 Self tests
At start-up and in runtime computer makes checks on itself:
• Hardware (hardware fault)
• Software (software fault)
• Database coherency
• Acquisition and output (see self-test)

3.4 Time management

The computer Real Time Clock has a small drift per day, therefore the operator should set its
time periodically or it should be synchronised to a master clock. If power is lost for a full
week the time will have to be set.
Time synchronisation of a computer can be done by three means:
• IRIG-B signal
• Clock message from a SCADA gateway (T-Bus)
• Clock message from the system master clock (S-Bus)

When the computer is synchronised all events and measurement have a time tag with
synchronised attribute. If synchronisation is lost, or has never been received, attributes
indicate 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
System Master
Clock
Which synchronises Operator

through station bus time setting
UCA2/IEC 61850
equipment
Which synchronises
through legacy bus
IEDs
C0004ENa
FIGURE 2: TIME MANAGEMENT

3.4.1 External clock
The external clock device (specific equipment or PCI board) receives the synchronisation
signal through several possible supports (GPS, DCF77, etc…) and then sent to the MiCOM
C264/C264C using IRIG-B standard. A specific input is dedicated for this application.
3.4.2 Clock message from a SCADA gateway
SCADA clock synchronisation is SCADA protocol dependent. The synchronisation message
is directly acquired by the MiCOM C264/C264C through the SCADA link.
3.4.3 System master clock

For the use of MiCOM C264/C264C in a Digital Control System, the clock synchronisation
can be received through the Ethernet protocol. The system master clock can be
implemented in any Ethernet connected equipment mainly in:
• MiCOM computer
• PACiS OI computer
• PACiS gateway computer

3.4.4 Time set by an operator
The user may set directly using the MiCOM C264/C264C local Operator Interface the time
and date.
4. COMMUNICATIONS
MiCOM C264/ C264C ensure up to three different type of communications:
• Telecontrol Bus (T-Bus),
• Station Bus (S-Bus),
• Legacy Bus (L-Bus).

Main characteristics are given below. Furthermore details on the S BUS protocol
implementation for MiCOM C264 is given.
RTU, SCADA PACiS System, UCA2 IED
T-BUS S-BUS
Telecontrol UCA2
Interface 61850
Computer Kernel
Legacy Gateway I/O boards
L-Bus
IED
C0005ENa
FIGURE 3: COMMUNICATIONS
4.1 Telecontrol bus
MiCOM C264/C264C behaves as a slave into master/slave protocol.
This bus is optional.
Protocols:
• IEC 60870-5-101 (T101),
• DNP3
Devices connected to:

• SCADA or RCP (also called RTU),
• Device via Modem
Link layer:
• RS 232
• RS422
• RS485
• Ethernet 10 or 100 Mbps

Physical support:
• Copper twisted pair (RJ45 connector)
• Optical fibre (multimode or monomode)

Number of communication links: Two can be used with two different protocols and data
destination or with the same mapping and protocol with redundancy factors.
4.2 Station bus
MiCOM C264/C264C behaves mainly as a server but it can be also a client of other C264
(distributed automation) or UCA2 IED.
This bus is optional.
Protocols:
• UCA2,
Devices connected to:

• PACiS devices (OI, SMT, PACiS Gateway)
• Other MiCOM C264/C264C
• UCA2 IEDs
Link layer: Ethernet 10 or 100 Mbps
Physical support:
• Optical fibre (multimode or monomode)

Number of communication links: one (MiCOM C264/C264C Ethernet switch board can be
plugged in the rack for redundancy Ethernet network or dual attachment).
4.3 Legacy bus
MiCOM C264/C264C behaves as a master.
Protocols:
• IEC 60870-5-103 (T103),
• ModBus MODICOM,
• DNP3
Devices connected to: IEDs
Link layer:
• RS 232,
• RS485
Physical support:
• Optical fibre (multimode)

Number of communication links: up to four able to support two different protocols.
4.4 SBUS PROTOCOL

As a server on Station BUS MiCOM C264 makes its database version available. If there are
other PACIS system devices connected, it checks their database version before subscribing
to them. It can be also client of protection on SBUS or another computer.
MiCOM C264 can be a client of Protection or Measurement IEDs on SBUS that provide it
with their specific functions. It can be a client of another PACIS computer to get data for:
distributed automation (uniqueness of control, AVR, Load shedding),
RTU/logging function.
4.4.1 UCA2 exchanges
The MiCOM C264 acquires and sends data on UCA2 Ethernet network using two
mechanisms:
• UCA2 REPORT
• UCA2 GOOSE
The UCA2 REPORT is specific between a server and one client, it provides:
• data value
• data state or quality attribute (validity and several kinds of invalid state)
• time tag of last data value change
• time tag quality attribute (server synchronised or not when event occur)
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 UCA2 GOOSE is a short message sent in multicast to all SBUS, this is quicker than
Report, but only the data value is sent.
Interested readers can refer to SII document for details.
4.4.2 UCA2 supported Common Class
MiCOM C264 computer exchange data using UCA2 Common Class. The following list gives
implemented ones:
Kind of information(UCA2 Class) UCA2 Class

Single-Point Status Single-point indication (SI)
Double-Point Status Double-point indication (SIT)
Transformer Position Indication Analogue Input (AI)
Measurement Value (AI, WYE, DELTA)
Single/Double Counter Accumulator (Accl)
Single Point Control Binary Output (BO)
Double Point Control Double Control Output (DCO)
Select Before Operate (SBO) Select Before Operate (SBO, SBOCF)
Regulating step control Analogue Output (AO)
Setpoint control (CF) Configuration (CF)
TABLEAU 1: DATA MANAGEMENT

4.4.3 UCA2 Controls
MiCOM C264 supports Common Class control expressed with BO, DCO, and SBO. For
received control from UCA2 it manages protocol control termination (possibly with NACK
codes). The Bypass controls is supported (through management of quality attributes).
5. DIRECT PROCESS ACCESS

The MiCOM C264/C264C acquires digital and analogue input, counters, digital
measurements, and analogue measurements from CT/VT. Configuration parameters,
filtering and triggering are applied to these inputs depending on their type.
5.1 Digital input acquisition (DI)
Acquisition of binary information is done via 16 DIs or 8 DIs+4 DOs boards.
5.2 Analogue input acquisition (AI)
Acquisition of voltage or current DC signals is done via 4 AIs board.
Acquisition of AC voltage and current coming from the electrical network is done via CT/VTs
board.
5.3 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 non-volatile memory.
The pulse frequency should be 20 Hz as a maximum. So, the deboucing and filtering values
must be chosen to suit.
5.4 Digital measurement (DM)
The digital measurements (DM) 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.
These DMs are used to process measurements and tap position indications.
5.5 Digital outputs (DO)
Two types of Digital Outputs can be integrated into the MiCOM C264:
• The command DOs from the 8 DIs+4 DOs boards.
• The signalling DOs from the 10 DOs boards.

This interface performs the application of a switching voltage to an external device in order to
execute single or dual, transient or maintained commands issued from the handling of
control sequence function.
Several types of Digital I/O boards are possible and the relays used to execute the
commands may be single (NO contact) or double (2 NO or NO/NC contacts) pole.
6. DATA PROCESSING
MiCOM C264/C264C raw input data 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)
6.1 Binary Input Processing

6.1.1 Binary Input Acquisition
These are binary information received from:
• from the internal protection and configured as binary inputs in the database: alarms,
signals, thresholds, etc …
• the automation algorithms and configured as binary inputs in the database.
• the IEDs and configured as binary inputs in the database: digital inputs, IED internal
indications, etc…
• internal functions of the computer

If these data are not time-stamped by the IEDs, the MiCOMC264/C264C will time stamp the
data, the time stamp is the time of reception (not the time of data change). This feature must
be configured in the database.
6.1.2 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 N 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.
By configuration, a BI could be transmitted using the two modes:
• Report based mode: for displaying, printing or archiving
• GOOSE based mode: for Ethernet UCA2devices purposes

6.1.3 Processing of Single Point Status
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 Logic *

RESET 01 False
SET 10 True
TOGGLING 11 Invalid
SELFCHECK FAULTY 11 Invalid
UNKNOWN 11 Invalid
SUPPRESSED 11 Invalid
FORCED RESET 11 False
FORCED SET 10 True
SUBSTITUTED RESET 11 False
SUBSTITUTED SET 10 True
* Logic is the state used in all automation (interlock, PSL, PLC, and build in functions)
6.1.4 Processing of Double Point Status
Preliminary treatment (filtering) for some DPS is applied to filter the MOTION state on a
certain period of time. This avoids the transmission of this (normally) transient state.
This treatment is said to be motion filtering.
The DP resulting states are:
States (report) Goose Logic

JAMMED 11 False
OPEN 10 True
CLOSE 01 False
UNDEFINED 11 Invalid
TOGGLING 11 Invalid
SELFCHECK FAULTY 11 Invalid
UNKNOWN 11 Invalid
SUPPRESSED 11 Invalid
FORCED JAMMED 11 False
FORCED OPEN 11 False
FORCED CLOSED 10 True
SUBSTITUTED JAMMED 11 False
SUBSTITUTED OPEN 11 False
SUBSTITUTED CLOSED 10 True
DPS are commonly used for all switchgear positions. 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 persistent filtering
6.1.5 Group processing

A group is a logical OR or AND or 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.
6.2 Processing of Multi Point Status
A Multiple Point is derived from N Digital Inputs. It is a kind of “1 among N” BIs. Transient
filtering is also added on acquisition. After this delay, the state UNDEFINED is applied to
cases of inconsistency between inputs.
The MP resulting states are:
States Goose Logic

STATE1 to STATE N True
UNDEFINED False
TOGGLING Invalid
SELFCHECK FAULTY Invalid
UNKNOWN Invalid
SUPPRESSED Invalid
FORCED STATE1 to FORCED False
STATE N
SUBSTITUTED STATE1 True
to SUBSTITUTED STATE N
N is fixed by MiCOM C264/C264C configuration from 2 to 32. There is no GOOSE

transmission mechanism.
6.3 Measurement Input Processing

Measurement Values can be Analogue Measurement, or Digital Measurement. Analogue
Measurements are acquired from communication or from computer boards (AIU200 for DC
or TMU200 for AC). Digital Measurement comes from Digital input.
6.3.1 Analogue processing
Preliminary treatments apply on a measurement (DC) can be:
• Filtering
• Scaling,
• Thresholds detection,
• Manual suppression,
• Substitution,
• Forcing.
The Measurement resulting states, following the various filters, which can be applied, are:
States Meaning
VALID
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 cross
UNDERSHOOT[1..3] One of the 3 undershoot values has cross
The measurement values and states are transmitted on a client-server basis on the Ethernet
UCA2 network, using only the report mechanism on UCA2 and classes AI, WYE and
DELTA.
Measurement values can be transmitted at fixed period, on variation (% of nominal), and
always on state change. Periodic transmission is based on multiple of 100 (fast) or 500 ms
(slow).
6.3.2 CT/VT additional processing

From the direct primary measurements (currents and voltages), MiCOM C264/C264C
calculates and transmits:
• RMS Values, current and voltage

• Active, Reactive and Apparent Power
• Power factor
• Network frequency
• Phase angles
• Harmonics contents (%THD) on voltage and (%TDD) on current up to 15th harmonic
• Phase Sequence (Id, Ii, Io, Vd, Vi, Vo)
With the additional synchrocheck option, following MV are computed:
• Slip frequency
• Amplitude, phase difference
• Synchrocheck voltage
The scanning period of the electrical network is 64 samples/period.
Transmission on network rules are the same as Analogue processing expressed before.
6.3.3 Digital Measurement Processing
A DM is a measurement derived from Digital inputs. It is used, for example, for TPI (Tap
Position Indication) of transformer, then in control sequence of transformer and Voltage
regulation.
Digital input acquisition defines special states like toggling. At processing level additional
treatments are persistent filtering and optional uses of a Read Inhibit digital input (when DI
set the DM is valid).
The supported coding of digital is the following:
BCD (Binary Coded Decimal)
Binary
Gray
Decimal
1 among N
6.4 Accumulator Input Processing
The accumulator stores its current value in non-volatile memory. At the configured sample
rate an accumulated value is extracted for inner computation and transmission (class Accl on
UCA2).
Digital Inputs are used to count pulses. There is Single counter (SCT) based on one DI and
double counter based on 2 DI which count complementary states.
At processing level special persistent and complementary filters eliminate non-stable pulses.
The integer counter (also transmitted) can be scaled (for valid pulse energy increment).
7. CONTROL SEQUENCES
A control sequence is a basic built-in function on a module (switch, relay, function). It
receives a control command, sending back acknowledgement. After checks, the control
sequence sends a command control (protocol or DO), and checks correct execution with
feed back from protocol or from DI.
7.1 Type of control sequences
The control sequences automation receives three types of input triggers (as a command
from a higher level) with selection, execution and unselection. A control command may have
a normal or abnormal termination with positive or negative acknowledgement to operator and
to communication.
By configuration, at PACiS SCE level a control sequence may be executed in one of the
following modes:
• Direct execute: Execution
• SBO once: Selection then Execution
• SBO many: Selection, several Execution, until Unselection

7.2 Control sequences checks
On receiving a command, the control sequences execute 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
Module conditions (switch transformer, inner or IED function…)
− Position valid
− 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
7.3 Operational Modes

This control sequence receives requests from the various control points:
Automation of higher level such as Auto Recloser
MiCOM C264 Local Control Display
MiCOM C264 TBUS communication from SCADA
Station BUS (other computer in distributed automation, PACiS Operator Interface, PACiS
Gateway)
To avoid conflict between the control points operating modes, Remote or Local are defined
for substation and for electric bay. 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 is also a switch that, when it is configured,
permits control on specific bay even if the 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.
7.4 Interlocking
The operating of a switching device (Circuit breaker, Traditional disconnecting switch,
Disconnecting switches load break switch with abrupt rupture, Ground disconnecting switch)
is directly related to its characteristics and its environment.
To operate these devices certain conditions must respected. These conditions, called
interlocking, are managed in the form of logical equations within the MiCOM C264/C264C
controlling the device(s).
The objective of interlocking is to prohibit a control sequence that may violate the device
operating condition (e.g. break capability, isolation…) or plant operating condition.
Linked to interlocking, uniqueness of control is defined into the MiCOM C264 for itself and/or
using data from other computers on SBUS. The mechanism is based on the GOOSE
7.5 Control Bypass
As stated earlier, various checks are required before control commands are issued.
However, using appropriate rights, the user or automation can bypass a configured check.
Then a specific control command is send to the control sequence.
7.6 HV Control Sequences

7.6.1 Control of circuit breaker
Several types 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.
7.6.2 Control of Isolator
The control sequence of disconnectors is identical to single non-synchronised circuit
breakers.
7.6.3 Transformer control sequence
Transformer tap position is determined using TPI (Tap Position Indication). TPI can be a
Digital Measurement (as seen previously) or Analogue Measurement (from DC Analogue
Input).
Transformer is the only device with supporting the SBO Many control sequences. It is linked
to voltage regulation, its Raise and Lower commands controlling secondary voltage (and not
tap position). For auto wound transformers, the raise/lower commands simply raise/lower tap
position..
8. AUTOMATION
MiCOM C264/C264C provides three different ways to perform automation functions:
• Build-in applications
• Programmable Scheme Logic
• Programmable Logic Controller.

The choice between these three solutions is time and complexity dependent.
8.1 Build-in Automation functions
Within the MiCOM C264/C264C 4 build-in automation functions are available and can be set
directly by the user:
• Auto-recloser
• Synchrocheck
• Trip-coil supervision
• Transformer Voltage regulation

8.1.1 Synchrocheck
MiCOM C264/C264C synchrocheck function 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.
The synchrocheck function can work in the following schemes:
• Automatic and manual network locking on both voltage presence and delta test,
• Automatic and manual network coupling on both voltage presence and delta test,
• Automatic and manual network connection on line voltage presence only,
• Automatic and manual network connection on busbar voltage presence only,
• Automatic and manual network connection on one voltage presence only,
• Automatic and manual network connection on both voltages absence.

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

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

with Vline and Vbusbar TRUE if the measured voltage is above the threshold V>, 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.
8.1.2 Auto-Recloser (AR)

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.
A B
(a) Network diagram
Protn. operated
(local or
intertrip)
AR lockout S Q AR
1 R Q in progress
CB closed
0 ti
1
AR inhibit
time
Reclaim timer
tR 0
Dead time
CB open td 0
Protn. reset CB close
CB healthy command
System healthy S Q
R Q
tR: reclaim time
ti: inhibit time (b) Autoreclose logic for each CB
td: dead time
C0007ENa
FIGURE 5: AUTO-RECLOSE SCHEME LOGIC

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-reclose (AR) schemes are implemented to carry out this duty automatically.
Instant of fault
Operates Resets
Protection
Operating
time
Transient Trip coil Contacts Arc Contacts Closing circuit Contacts Contacts
fault energised separate extinguished fully open energised make fully closed
Circuit
breaker
Opening Arcing Closing
time time time
Operating time Dead time
System disturbance time Relay ready to respond to further fault incidents
Reclose initiated by protection (after successful reclosure)
Auto-reclose relay
Dead time Closing

pulse time
Reclaim time
Time
C0008ENa
FIGURE 6: SINGLE SHOT AR SCHEME OPERATION FOR A TRANSIENT FAULT

8.1.3 Trip Circuit supervision
The purpose of this function is to supervise the continuity of the trip circuit of a CB.
Two options are available: two wires or four wires. The two-wire option permits verification of
continuity of the trip circuit only when the CB is closed. The four-wire option permits
verification of the continuity in either position.
If the CB has single tripping, it will be necessary to supervise the continuity of the trip circuit
for each phase separately.
PR 52a TC
(a) Supervision while circuit breaker is closed (scheme H4)
PR 52a TC
52b
(b) Supervision while circuit breaker is open or closed (scheme H5)
PR 52a TC
A B
Alarm
(c) Supervision with circuit breaker open or closed
with remote alarm (scheme H7)
Trip
Circuit breaker
Trip 52a TC
52b
(d) Implementation of H5 scheme in numerical relay

C0009ENa
FIGURE 7: TRIP CIRCUIT SUPERVISION CIRCUIT

8.1.4 Automatic Voltage Regulation (AVR)
To maintain a system voltage supply within finite limits, it is necessary to regulate the system
voltage. The On-line Tap Changing transformer maintains a stable secondary voltage by
selecting appropriate tapping on the secondary transformer windings. Selection orders are
issued from the Transformer Voltage Regulation function that continuously monitors the
transformer.
The motor-driven OLTC receive the "Raise" and "Lower" control commands from the
Transformer Voltage Regulation module. These commands change the OLTC position and
the transformer voltage value is adapted to the pre-set required voltage level.
Volt
RateMax
Time
T1 T2 T2
T0
Tap RAISE 1 Tap RAISE 2 Tap RAISE 3

C0010ENa
FIGURE 8: TVR VOLTAGE MANAGEMENT

The Transformer Voltage Regulation module assumes also the compensation of voltage-
dependent limits and the management of one or several transformers in parallel (secondary
poles interconnected.
Automatic Voltage Regulation module also provides:
• 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 to which it will be
connected
• Minimisation of circulating current

For each transformer, MiCOM C264/C264C acquires:
• Current, voltage, active and reactive powers of the transformer secondary
• Electrical topology of the transformer secondary, including busbar transformer

connection and busbar coupling
• OLTC states
The user may set the Automatic Voltage Regulation module:
• Automatic Voltage Regulation On/Off
• Five Target Voltages (5 floating pre-set values +/- 10%, resolution of 0.2 %).
The Automatic Voltage Regulation module displays specific alarms and indications such as:
• Substation alarms or indications
− homing On/Off (defined during the configuration phase)
− Target Not Achievable
− Error Log Indication
• Busbar alarms or indications
− Invalid voltage (when different values for parallel transformers)
− Under-voltage or over-voltage: FUNCTION INHIBITED
− A circuit breaker or a disconnector in an invalid state in the group
• Transformer alarms or indications
− Hunting
− Tap Position is not the expected one
− I > Overcurrent value
− Bay disconnected (this takes into account power supply fail)
− Bay in local mode
− Invalid voltage, current, MW and MVAR (if configured)

8.2 Fast automation (PSL)

MiCOM C264/C264C provides the user the capability to build his own Programmable
Scheme Logic (PSL) for Fast Automation modules. This is achieved through the use of
programmable logic gates and delay timers.
The input to the PSL is any combination of the status of the digital inputs, the outputs of the
MiCOM C264/C264C and issued from the various communications buses (T-BUS, L-BUS,
S-BUS).
The logic gates can be programmed to perform a range of different logic functions and can
accept any number of inputs.
The timers are used either to create a programmable delay, and/or to condition the logic
outputs, e.g. to create a pulse of fixed duration on the output regardless of the length of the
pulse on the input.
The outputs of the PSL are the LEDs on the front panel, the output contacts of the MiCOM
C264/C264C boards and the commands sent through the S-BUS.
The execution of the PSL logic is event driven; the logic is processed whenever any of its
inputs change, for example as a result of a change in one of the digital input signals. Also,
only the part of the PSL logic that is affected by the particular input change that has occurred
is processed. This reduces the amount of processing time that is used by the PSL.
This system provides flexibility for the users to create their own scheme logic design.
C0011ENa
FIGURE 9: PROGRAMMABLE SCHEME LOGIC

The fixed components are:
• the protection elements,
• the product scheme logic (default configuration).

The programmable components are:
• the logic gates:
− "AND" logic gates,
"AND logic" with relay scheme
"AND logic" with MiCOM C264

C0012ENa
FIGURE 10: PSL AND LOGIC GATE
− "OR" logic gates,
"OR logic" with relay scheme
1
"OR logic" with MiCOM C264
C0013ENa
FIGURE 11: PSL OR LOGIC GATE
− "NAND" logic and Majority of logic gates,
"AND logic" and Majority with

MiCOM C264 C0014ENa
FIGURE 12: PSL AND + MAJORITY LOGIC GATE
− "NOR" logic gates,
1
C0015ENa
FIGURE 13: PSL NOR GATE
• the output conditioners: timed or latched output contacts,
• the LEDs conditioners: configurable latched LEDs,
• the adjustable timers.

8.2.1 Settable inputs of the PSL

The input data of the PSL are:
• The opto-inputs: the mapping of these inputs is user settable. Each input may be
connected to more than one MiCOM C264 element or PSL input.
• The MiCOM C264/C264C elements settings, which are defined using the PACiS SCE.
8.2.2 Timers
8.2.2.1 Pick-up timer
When an input signal goes high the timer waits for a time indicated by the Pickup Time
before driving the output high. If the input drops off whilst the pick up timer is in the process
of expiring the timer immediately resets holding the output low.
100ms
Relay scheme
100
Pick-up
0
MiCOM C264
input
Pick-up delayed time
output
Principle of pick-up delayed time

C0016ENa
FIGURE 14: PSL PICK-UP TIMER

8.2.2.2 Drop-off timer
When the input signal goes high the timer output will be driven high. When the input drops
off the timer waits for the time indicated by the Dropoff Time before driving the output low. If
the input picks up again whilst the timer is in the process of expiring the timer immediately
resets and continues to time out holding the output high.
100ms
Relay scheme
100
Drop-off
0
MiCOM C264
Drop-off delayed
input
time
output
Principle of drop-off delayed time

C0017ENa
FIGURE 15: PSL DROP-OFF TIMER

8.2.2.3 Dwell timer
When the input signal goes high the dwell timer immediately drives the output high for the
dwell setting time. If after this period expires the input is low the dwell timer output can go
low. If, however, the input is not low the output of the dwell timer follows the input until it
resets.
input input
Stopping time delay time time

Stopping time delay
output output
time time
C0018ENa
FIGURE 16: PSL DWELL TIMER

8.2.2.4 Pulse timer
When the input signal goes high the pulse timer immediately drives the output high for the
duration of the pulse setting time, irrespective of the status of the input. After this period
expires the input is driven low.
8.2.2.5 Pick-up/Drop-off timer
This timer when selected combines the functionality of both timers to produce delay’s on
both pick up and drop off.
8.2.2.6 Transparent
The Output signal follows the Input signal.
8.2.2.7 Latch
When the input signal goes high the latch will immediately drive the output high until the latch
is reset by a global latch reset command.
8.2.3 Programmable gates

A programmable gate requires an entry in the Inputs to Trigger field.
Disabled: If this radio button is active, the gate will become disabled. The gate output will be
permanently low.
AND Gate: If this radio button in active, the gate will become an AND Gate.
OR Gate: If this radio button in active, the gate will become an OR Gate.
Programmable Gate: This radio button is active. The minimum number of inputs required to
enable this gate is defined in the ‘Inputs to Trigger’ case.
Always Enabled: If this radio button is active the gate output will always be high.
Invert Output: If this radio button is active the gate output is inverted.
8.3 Configurable automation (PLC)
The MiCOM C264/C264C allows the user to configure specific control sequences or
automations (e.g. switching sequences, busbar transfer, load shedding, and GIS-pressure
supervision) during the substation configuration phase.
The Programmable Logic Controls (PLC) or Configurable Automations are entered and build
onto a logic development workbench. A real time kernel that is located on the computer then
runs them. These PLCs give orders to the computer in order to realise some tasks
(information signalling, control orders, and so on).
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 used to create control logic programs.
It is a full-featured set of tools providing:
• Editing
• Code generation
• Simulation
• Project management
• Debugging
The Soft Logic package supports all five standard programming languages of the IEC 1131-
3:
• Sequential Function Chart, SFC (GRAFCET)
• Function Block Diagram, FBD
• Ladder Diagram, LD
• Structured Text, ST
• Instruction List, IL
The code generated by the Soft Logic package workbench is then uploaded to a target
system where a kernel, as pictured below, will run it.
Control logic
application
code
Soft Logic Target

package hardware
C0019ENa
FIGURE 17: WORKBENCH AND TARGET

9. USER INTERFACE
The user can receive information from the MiCOM C264/C264 front panel 4 different ways:
LEDs
− 5 reserved for MiCOM C264/C264C status
− 12 Configurable for any purpose

Local Control Panel (optional)
− Liquid Crystal Display (LCD)
− Push buttons
Local/Remote push-button (L/R)
Serial Link under the lower flap for maintenance operations
9.1 Front Panel
The MiCOM C264/C264C front panel exists in two versions:
• A simple FP with LEDs, L/R push-button and the serial link
• A graphical FP with LEDs, L/R push-button, the Local Control Display and the serial
link
LEDs
Key-pad
Local/Remote
Graphical push-button
LCD
RS 232 Serial port
C0020ENb
FIGURE 18: MiCOM C264C FRONT PANNEL

9.2 LED’s Management

The computer’s five status LED’s indicate “system” information such as computer is
powered, its operational mode, if alarm is present, if LCD is in edit mode (password
entered)…
12 red LED’s are fully configured by PACIS SCE.
These LED are linked to any Binary information: Single, Double, or Multi Point Status (1
among N) whatever the source of information:
• Computer board input,
• Inner function (Bay control running, AR, synchronisation, mode..),
• IED or UCA2 acquisition,
• PSL or ISAGRAF automation result.
Each LED can have 3 states: on, off, blinking.
Each LED’s state is linked to Data Point state. Usually blinking is reserved for all invalid
states, on for close or set, off for open disable.
The LED itself does not memorise a change of state that lights it on, therefore this feature is
only a state indication not an alarm.
9.3 Local Control Display
The Liquid Crystal Display has several kinds of screens or panels split in two families
protected by 2 levels of password for actions. The first set has bay panels and lists.
Bay panels are graphical representation of an electric bay showing plant items, transformers,
and textual information needed to control the bay (measurements, bay mode, inner closing
function like AR, Synchrocheck).
Lists panels include alarms, events, measurements, and computer status…
The second set is called menu tree. It allows access to settings, reports, and special controls
such as the different bypass, or Substitution of data point state/value.
The push buttons associated with the graphical LCD allow:
• Navigation between screens or panels,
• Select information
• Enter value or string (including password)
• Send Control (Bay Mode, switch gear, transformer …)
9.4 Local/Remote push-button
The Local/Remote push button manages the MiCOM C264/C264C operation modes:
• Local
• Remote
9.5 Front serial Link
The Front panel RS232 serial link is located under the lower flap.
This serial link is dedicated for maintenance purpose to connect a PC with the MiCOM
C264/C264C maintenance software tools:
• Hyperterminal
• MiCOM S1 (setting IED on LBUS using pass through)
10. RECORDS
Several kinds of records are stored into MiCOM C264.
10.1 Permanent records storage
They are stored on flash disk and are non-volatile (i.e.: records can be read after the partial
destruction of the computer if the flash is not destroyed).
10.1.1 Data storage
All parameters or settings that can be modified via front face LCD are stored in non volatile
memory.
Lists of system information reserved for maintenance purposes )such as hardware or
software faults) are also stored in the flash.
10.1.2 Fast Waveform Recording
MiCOM C264/C264C Waveform recording is available with the CT/VTs board only.
The inputs for the 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 measurement samples, with 32 samples
per cycle, can be stored, divided in 1, 2, 4 or 8 files saved in non-volatile memory.
For the digital channels, the values are stored internally. 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 Records 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
definable :
• Changes in state of binary inputs (SP, DP, MP, SI or Groups)
• Changes in state of digital outputs
• Measurement threshold violations
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.
Waveforms records are stored using COMTRADE 97 binary format.

10.1.3 Disturbance Recording

Disturbance recording can be performed:
• Directly by the MiCOM computers : see FST and SST features below. Records are
stored using COMTRADE 97 binary format
• By the IEDs which communicate with the MiCOM computers. In this case, the
computer uploads the disturbance record from the IED. Only one record can be stored
on a per IED basis (the storage policy at the IED level is not described here).
10.1.3.1 Fast Scan Triggered (FST)
960 cycles of data storage are provided for disturbance recording. For each cycle of data, as
well as (32 or 64) x 8 channels of samples, there will be a time stamp that indicates the time
at which the samples were received. Up to 128 logical data can be stored with the 8
analogue channels.
The number of samples 32 or 64 per period is defined in configuration.
The ninth channel is the timer channel. This timer information is needed to produce the
Comtrade format output. The time interval between samples is generated from the control
frequency.
Disturbance Record Format:
A maximum of 32 disturbance records can be stored simultaneously; the more records are
stored, the shorter each record is. The possible record configurations are outlined below :
Number of Records Maximum duration in cycles

32 30
16 60
8 120
6 160
4 240
3 320
2 480
1 960
Along with the raw samples stored in each channel the following information are also stored:
• The identifier of the information stored for each channel.

These information can be:
− Van, Vbn, Vcn
− Vab, Vbc, Vca, Vr
− Ia, Ib, Ic, Ir
• The scaling factor of each analogue channel

The trigger can come from :
• Changes of state of binary inputs (SP, DP, MP, SI or Groups)
• Changes of state of digital outputs
• Request from an operator

10.1.3.2 Slow Scan Triggered (SST)
The SST stores and identifies abnormal conditions on power systems and electrical
schemes.
15000 cycles of data storage are provided for slow disturbance recording. For each cycle of
data, as well as 8 channels of samples, there will be a time stamp that indicates the time at
which the samples were received. Up to 128 logical data can be stored with the 8 analogue
channels.
A maximum of 32 disturbance records can be stored simultaneously; the more records are
stored, the shorter each record is. The proposed possible record configurations are outlined
below:
Number of Records Maximum duration in cycles

32 465
16 930
8 1875
6 2500
4 3750
3 5000
2 7500
1 15000
Along with the raw samples stored in each channel the following information will need to be
stored:
• The identifier of the information stored for each channel.

The information can be:
− RMS values of phase voltage (Van, Vbn, Vcn).
− RMS values of line voltage (Vab, Vbc, Vca).
− RMS values of phase current (Ia, Ib, Ic).
− RMS values of residual voltage and current (Ir and Vr).
− Fundamental sequence component
− Active Power (Pa, Pb, Pc and Pt).
− Reactive Power (Qa, Qb, Qc and Qt).
− Apparent Power (Sa, Sb, Sc and St)
− Frequency
− Analogue input
• The scaling factor of each analogue channel

The RMS values are calculated on a configurable integration period:
• Minimum value: 1 cycle (20 ms in 50 Hz, 16.6 ms in 60 Hz)
• Maximum value: 1 hour

The trigger can be:
• Changes of state of binary inputs (SP, DP, MP, SI or Groups)
• Changes of state of digital outputs
• Request from an operator

10.2 Non-permanent data storage
10.2.1 Events
All data change or events declared in MiCOM C264/C264C configuration database « To be
logged » are stored in a circular list of 200 events.
The event records are available for viewing either via the front panel LCD or remotely, via
the communications ports. They can be printed by a computer printer.
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 may define the following circumstances as 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

10.2.2 Alarm function
An alarm is a visual annunciation of an event, within the controlled electrical process or
within the system itself, of an event defined during the configuration phase as « to be
alarmed ».
An alarm can be generated by the following events:
• Binary Input (SP, DP, MP, SI, IED input, Groups) state
• Measurement state
• TPI state or value
• Metering state
Alarms are stored in circular list like events. The main difference is that they can be
acknowledged by an operator, or be reset when alarm condition disappear (alarm is still in
the list but at reset state, until an operator acknowledges it, then the alarm disappears
definitively from the list).
Hardware C264/EN HW/A13
MiCOM C264/C264C
HARDWARE
CONTENT
2. HARDWARE DESCRIPTION 3
2.1 Concept 3
2.1.1 Components 3
2.1.2 Hardware Overview 4
2.2 MiCOM C264C 5
2.2.1 Hardware presentation 5
2.2.2 Modularity 6
2.2.3 I/O Capabilities 7
2.3 MiCOM C264 8
2.3.1 Hardware presentation 8
2.3.2 Modularity 9
2.3.3 Permissible configurations 10
2.3.4 I/O capabilities 10
2.4 Coding of board address 10
2.5 Modules description 11
2.5.1 Power auxiliary supply and legacy ports board – BIU241 11
2.5.2 Central Processing Unit and base communications board – CPU260 14
2.5.3 Digital Inputs Unit – DIU200 16
2.5.4 Digital Outputs Unit – DOU200 17
2.5.5 Circuit breaker Control Unit - CCU200 18
2.5.6 Analogue Input Unit – AIU200 19
2.5.7 Transducer less Measurements Unit – TMU200 20
2.5.8 Front panel - GHU240 21
C264/EN HW/A13 Hardware
BLANK PAGE

This document is a chapter of MiCOM C264/C264C documentation binders. It describes
product hardware not in the commissioning chapter.
2. HARDWARE DESCRIPTION
2.1 Concept
2.1.1 Components
The MiCOM C264C/C264 is based on a modular and scalable architecture to support
dedicated hardware modules adapted to the plant data interfaces.
Each MiCOM C264C/C264 rack is equipped with the following modules:
• GHU240: Graphical Human Interface, Standard Front Panel: Front Face Standard
including 17 Leds (12 free configurable) + 12 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.
• BIU241: Basic Interface Unit. This board includes the auxiliary power supply
converter, the watchdog relay, 2 digital outputs and 2 insulated RS485/RS232
interface.
• CPU260: Central Processing Unit and communications board

Each MiCOM C264C/C264 rack can be equipped with the following modules:
• DIU200: Digital Inputs Unit each with 16 digital inputs
• 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
• AIU200: Analogue Input Unit each with 4 analogue inputs low level
• TMU200: Transducerless Measurements Unit board for direct CT/VT measuring

acquisition with 4 CT and 4 VT
2.1.2 Hardware Overview
CT/VT - Board (TMU 200)
MIO - Mother Board

SWITCH - Board (SWU200)
SWITCH - Board (SWU200)

CPU - Board (CPU260) SWR201 - redundant 1x100BaseFx and 4x10/100BaseTx
FP - Board (FBP2x0)
PS - Board (BIU241)
MIO- Board
10/100BaseTx
I/O- Boards
Ethernet Links
100BaseFx
CT/VT -Board
SWU -Board
DI - Boards (DIU200)
CT/VT - Board (TMU200)
16 Digital Inputs (16 DI) Digital Inputs CT Inputs CT Currents

VT Inputs VT Voltages
DO - Boards (DOU200)
10 Digital Outputs Digital Outputs

(8NO+2NO/NC)
Mixed - Boards (CCU200)
Digital Inputs
8 Digital inputs (8DI)
4 Command Outputs (4CO) Command Outputs
AI - Boards (AIU200)
4 Analogue Inputs Analogue Inputs
IRIG - B link (optional) IRIG - B Time signal

Optional (*)
RS232 /RS422 / RS485
Comm. Link No.4
RS232 / RS422 / RS485
Comm. Link No.3
CPU - Board (CPU2x0)
Ethernet Link No.1 10/100BaseT

Ethernet Link No.2 100BaseF
Comm. Link No.1 RS232 /RS422 / RS485

Comm. Link No.2 RS232 / RS485
PS - Power Supply
Board (BIU241)
Auxiliary Supply Auxiliary Supply (24, 48/60, 110/125, 220/250 Vdc and 150-250 Vac
Watchdog Relay (1 NO/NC) Watchdog
Alarm Relay (1 NO) Alarm Output
Digital inputs (2 DI) Digital Inputs
(*) By jumpers on the board and BD configuration

FP - Front Panel
Board (FBP 2x0)
17 LED´s, 12 free configurable Maintenance
Keypad Interface
Graphical large LCD Interface Printer
Local Comm. Link
C0021ENa
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 bellow:
206
177
177
157.5
17.7 200
12 9.6
172.2
30
C0022ENa
There are 5 status LED

indicators, which are
permanently assigned to
signalling The MiCOM C26x has
an integrated HMI based on a
liquid crystal display (LCD,
resolution of 128 x 128 pixels /
16 lines of 21 characters each)
There are 12 LED indicators, and a keypad at the front plate.
which allow freely configurable
signalling function assignment
like:
Digital I/O Dedicated pushbuttons can be
Result of interlocking used for operation of devices or
equations other configurable functions like
Internal information coming Local/Remote (L/R).
from PLC, automatism
etc.
C0023ENb
FIGURE 2: MiCOM C264C – FRONT PANEL OVERVIEW

Case properties:
• Case degree of protection: IP52 in standard
• Front Face degree of protection: IP52
• Metallic case
• Available for flush or wall mounting
Ethernet 10 /100 Base T connector Power supply connector
DI, DO, A I, CCU boards connectors Optional connectors:

• Ethernet 100 BaseF;
CT/VT measurements connector • IRIG-B;
• RS232/485 serial ports
C0024ENa
FIGURE 3: MiCOM C264C – REAR PANEL OVERVIEW

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:
There are two bus versions for connecting boards:
• with CTVT the bus is 7 slots width: 1 slot for the BIU, one slot for the CPU and one
slot for the CTVT allows 4 slots for I/O boards.
• without CTVT the bus is 8 slots width: 1 slot for BIU one slot for CPU allows 6 slots for
I/O boards
MiCOM C264C without CT/VT
01 02 03 04 05 06 07 08
com munications (CPU260)

(BIU241)
CPU and base

Power supply
01 02 03 04 05 06 07 08
MiCOM C264C with CT/VT
01 02 03 04 05 06 07 08
com munications (CPU260)

(BIU241)
CPU and base

Power supply
01 02 03 04 05 06 07 08
C0025ENa
FIGURE 4: MiCOM C264C - MODULES ORGANISATION

2.2.3 I/O Capabilities
Case Without CCU200 (DI + DO mix board)
MiCOM Cx64C – I/O Capabilities

Case CT/VT AI DO DI
Standard 0/0 8 60 96
0/0 8 50 80
CT/VT dedicated
4/4 8 40 64
Case With CCU200 (DI + DO mix board)

Case CT/VT AI DO DI
Standard 0/0 8 24 48
0/0 8 20 40
CT/VT dedicated
4/4 8 16 32
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 below:
413.2
174.5
156.5
155.5
177
3
3
10.8
408,4
12.5 9.7
17.7
172.2
172.2
30
413.2
C0026ENa
There are 5 status LED

indicators, which are
permanently assigned to
signalling of: In option, the MiCOM C26x has
an integrated HMI based on a
liquid crystal display (LCD,
resolution of 128 x 128 pixels /
16 lines of 21 characters each)
There are 12 LED indicators, and a keypad at the front plate.
which allow freely configurable
signalling function assignment
like:
Digital I/O Dedicated pushbuttons can be
Result of interlocking used for operation of devices or
equations other configurable functions like
Internal information Local/Remote (L/R).
coming from PLC, automatism
etc.
C0027ENb
FIGURE 5: MiCOM C264 – FRONT PANEL OVERVIEW

Case properties:
• Case degree of protection: IP20 in standard
• Front Face degree of protection: IP20 in standard
• Metallic case
• Available for flush or wall mounting

Power supply connector
CPU standard Ethernet 10/100 Base T connector
Optional connectors:
DI, DO, A I, CCU boards connectors
• Ethernet 100 BaseF;
CT/VT measurements connector • IRIG-B;
• RS232/485 serial ports
C0028ENa
FIGURE 6: MiCOM C264C – REAR PANEL OVERVIEW

2.3.2 Modularity
The MiCOM C264 is available in two case version allowing flexibility and scalability in the
use of the I/O modules:
There is one bus versions 17 slots width for connecting boards:
• with CTVT: 1 slot for the BIU, one slot for the CPU and one slot for the CTVT allows
14 slots for I/O boards.
• without CTVT: 1 slot for BIU one slot for CPU allows 15 slots for I/O boards
MiCOM Cx64
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17
munications (CPU24x)
(BIU24x)
X X X X X X Y Y Y Y Y Y Y Y Z
and base
Power supply
com
CPU
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17
Legend:
X AIU200, DOU200, CCU200 or DIU200
Y DOU200, CCU200 or DIU200
Z TMU200 or DIU200
C0029ENa
FIGURE 7: MiCOM C264 - MODULES ORGANISATION

2.3.3 Permissible configurations
MiCOM Cx64 – Admissible modules

Case CT/VT AIU200 DOU200 DIU20x CCU20x
Without CT/VT 0 Up to 6 Up to 8 Up to 10 Up to 15
With CT/VT 1 Up to 6 Up to 8 Up to 10 Up to 14
2.3.4 I/O capabilities

Case Without CCU200 (DI + DO mix board)

Case CT/VT AI DO DI
Without CT/VT 0/0 24 80 160
With CT/VT 4/4 24 80 160
Case With CCU200 (DI + DO mix board)

Case CT/VT AI DO DI
Without CT/VT 0/0 24 60 120
With CT/VT 4/4 24 56 112
2.4 Coding of board address

Same rule is applicable to all boards:
Binary coding on 4 jumpers LSB at tap, max 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 also includes the auxiliary power supply converter, the watchdog relay, 2
command output units and an isolated RS485/RS422/RS232 interface.
The power auxiliary supply board has 2 legacy ports (RS232 or RS485 factory setted)
isolated and two digital inputs (2DI).
Port 1: RS232 or RS422 or RS485
Port 2: RS232 or RS485
The other capabilities of the BIU241 board are:
• Watchdog relay (NO/NC)
• Alarm relay (NO)
• Isolated RS485/RS232 interface (by ferrite or intern to the board)
• Two optically isolated digital inputs, 1 common contact for 2 inputs for redundancy
management
• Protection against reversal polarity
A watchdog relay is incorporated into the BIU241 board giving the indication that the product
is healthy. Software and hardware drive this relay on the CPU260 board.
C0031ENa
FIGURE 8: MiCOM C264 - BIU241 BOARD

The BIU241 board provides two insulated serial links in base.
This following figure shows where to find the jumpers used to configure the serial links.
C0032ENa
FIGURE 9: BIU HARDWARE SCHEME

By zooming the upper right corner of the BIU board, jumpers can be found, the possible
configurations are explained below.
C0033ENa
FIGURE 10: ZOOM ON BIU JUMPERS

2.5.1.1 Configurable communication Port 1 - RS232/422/485
Can be used for communication with SCADA, Sub-MiCOM C264 or with IEDs.
The communication link characteristics are:
• Asynchronous full duplex serial protocol
• Transmission rate: 300 to 64000 bps (settable)
Configuration:
The hardware jumpers arrangement is shown in the figure below.
• In RS232 set the jumpers S5, S6 and between S9 and S3 diagram
• In RS485 set the jumpers S7, S8, S2. It is possible to end the line with a 124Ω resistor
by setting the jumper S11.
• In RS422 set the jumpers S7, S8 and between S4 and S2 diagram. It is possible to
end the line with a 124Ω resistor by setting the switch S10 and S11.
2.5.1.2 Configurable communication Port 2 - RS232/485
Can be used for communication with IEDs or Sub-MiCOM C264.
The communication link characteristics are:
• Asynchronous full duplex serial protocol
• Transmission rate: 300 to 64000 bps (settable)
Configuration:
The hardware jumpers arrangement is shown in the figure below.
• 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 the switch S17.
2.5.2 Central Processing Unit and base communications board – CPU260
• The CPU260 board is based on a PowerPC processor includes the 10/100BaseT

Ethernet communication in base. This board is interfaced with all other boards through
the main computer’s bus.
The CPU 260 board includes the following capabilities:
• Two additional based communication serial RS232 non isolated or RS485 ports
Port 3: RS232 (non isolated) or RS485 or optical
Port 4: RS232 (non isolated) or RS485 or optical
• One IRIG-B input
• One 100BaseF Ethernet port (ST connector)
• Control the Front panel information
• The CPU260 is based on a PowerPC-based microprocessor
• 64 Mbytes Dynamic memory DRAM
• 16 Mbytes Flash memory
• 256 Kbytes static memory SRAM
• Internal watchdog command (watchdog relay on BIU241 board)
• Calendar saved
• Ethernet-based 10/100BaseT (RJ45 interface)
• 2 serial interfaces RS232/485
• IRIG-B interface (optional)
• Ethernet-based 100BaseF (optical)
• Floating-Point Digital Signal Processor (DSP) - (optional)
• Control the Front panel large graphical LCD

C0034ENa
FIGURE 11: MiCOM C264 - CPU260 BOARD

2.5.3 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 common contact for 2 inputs
• Protection against reversal polarity
• The digital inputs can be configured in single or double remote signalling, pulse or
digital measurement input on the same module.
C0035ENa
FIGURE 12: MiCOM C264 - DIU200 BOARD

2.5.4 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 function for the output control procedure is provided (address check, state
monitoring)
The +5V bus voltage is monitored to avoid issuing inadvertent commands.
The digital outputs can be configured in single or double remote control or set point outputs
on the same module.
C0036ENa
FIGURE 13: MiCOM C264 - DOU200 BOARD

2.5.5 Circuit breaker Control Unit - CCU200

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

The digital inputs can be configured in single or double remote signalling inputs on the same
module.
The digital output (DO) capabilities of the CCU20x boards are:
• 4 double pole relays with one normally open (NO) contact
• 1 common contact for 2 outputs

A self-monitoring function for the output control procedure is provided (address check, state
monitoring)
The +5V bus voltage is monitored to avoid issuing inadvertent commands.
The digital outputs can be configured in double remote signalling only.
C0037ENa
FIGURE 14: MiCOM C264 - CCU200 BOARD

2.5.6 Analogue Input Unit – AIU200

The Analogue input module (AIU200) capabilities are the following:
• 4 independent analogue inputs. Each AI can be configured in voltage or current range

individually between:
− ± 1mA, 0-1 mA
− ± 2 mA, 0-2 mA
− ± 5 mA, 0-5 mA
− ± 10 mA, 0-10mA
− ± 20 mA, 0-20mA
− 4-20 mA
− ±1V
− ± 2,5 V
− ±5V
− ± 10V
− 16-bit resolution A/D Converter (15 bits + sign)
• Sampling period: <40 ms
• Gain range: 1, 2, 4, 10 adjustable
• Zero suppression adjustable

The analogue inputs can be configured to be either voltage or current inputs on the same
module. Jumpers (factory set) can select three hardware configurations.
The analogue input impedance is:
Range Input impedance

Voltage inputs 10 KΩ
Low current inputs : ± 1mA to ± 10mA 500 Ω
Other current inputs: ± 2 mA to ± 20mA 250 Ω
C0038ENa
FIGURE 15: MiCOM C264 - AIU200 BOARD

2.5.7 Transducerless Measurements Unit – TMU200
The transducersless measurement capabilities are the following:
• 4 measurement Current Transformers (4 CT) inputs
− Transformers have two ranges 1 and 5 amperes
• 4 measurement Voltage Transformers (4 VT) inputs
− Nominal AC voltage (VN): 57.73 Veff to 500 Veff
• Frequency operating range: 50 or 60 Hz ± 10%

2.5.8 Front panel - GHU240

Local HMI Front panel equipped MiCOM C264 computer as shown below:
C0039ENb
FIGURE 16: MiCOM C264 GENERAL VIEW WITH FRONT PANEL
C0040ENb
FIGURE 17: MiCOM C264C GENERAL VIEW WITH FRONT PANEL

BLANK PAGE
Connections C264/EN CO/A14
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 (EARTH CONDUCTOR) 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.2 Central Processing Unit – CPU260 15
4.3 Digital Inputs module – DIU200 21
4.4 Digital Outputs module – DOU200 23
4.5 Circuit breaker Control Unit - CCU200 25
4.6 Analogue Input module – AIU200 27
4.7 Transducerless Measurements Unit module –TMU200 29
4.8 Front panel 31
C264/EN CO/A14 Connections
BLANK PAGE

This document is a chapter of MiCOM C264/C264C documentation binders. It describes the
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.
An example of this reference of the female connector from Entrelec is:
• Entrelec L 245 424 31 000/24-G-5.08

and boards are equipped with a male connector, the reference is:
• Entrelec L 255 324 01 000/24-G-5.08

Please note that I/O connections may be equipped with any other compatible connectors.
I/O connector block characteristics:
Parameter Value
Continuous rating 10 A
Connection method Screw M3
Cable size 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: ENTRELEC L 245 424 31 000/24-G-5.08 CONNECTOR

NOTE: The connector is fixed to the rack (CASx6x) by 2 screws M3 located at
top and bottom of the connector.
2.2 CT/VT Connector Block

MiCOM C264 uses a standard MiDOS 28 connector block for transformer connection.
CT connection requires 2 dual terminal groups to allow for dual rated transformer (1A/5A).
Each group has shorting contact to allow disconnection of CTs.
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 * 2.5 mm2
CT connection
Cable size 2 * 2.5 mm2 / 1 * 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 (CASx6x) through the intermediary
of 4 Phillips screws M4; 2 are located on the top part and 2 on the
bottom part.
2.3 Serial communications connections

For a serial communications interface a termination is necessary on the bus for each last
device, i.e. termination resistors must be connected. These are variants with RS485 or
RS422 interfaces.
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 multiplexer or if the cables run through a noisy area, optical
communication should be used to interconnect the IEDs and the communication equipment.
For RS485, a cable with a characteristic impedance of 120 ohms is recommended, the cable
should be terminated at each end with a 120 ohm, quarter watt (or greater) 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
C0043ENa
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 RS485/4 wires or 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.
If equipment's are located at a long distance (>10 m for RS232, >100 m for RS422 and
>1000 m for RS485) from the communication equipment or multiplexer or if the cables run
through a noisy area, then optical communication should be used to interconnect the IEDs
and the communication equipment.
3. CONNECTION OF THE PROTECTIVE (EARTH CONDUCTOR)

3.1 Earthing
MiCOM C264/C264C must be connected to the earth according to the EN61010-1(2001) –
clause 6.5.1.4 electrical safety standard using the earthing terminals located on the rear
panel.
The screw terminal diameter is 5 mm. A washer and a crimp connector are also provided.
The earth wire must be as short as possible. All cautions have to be taken to ensure the best
electrical conductivity, particularly the contact quality, stainless conductor. The impedance
between the MiCOM C264/C264C Earthing terminal and the Earth must be less than 10 mΩ
under 12 Volt, 100 Hz.
Good conductor surface
Hold tight the cable
Copper cable at
least 5 mm
diameter
C0047ENa
FIGURE 7: EARTHING CABLE EXAMPLE

If the protective (earth) conductor terminal is an M4 stud, which may also used to terminate
cable screens, the protective conductor must be mechanically terminated using a lock nut, or
other means, such that connection or removal of functionally earthed cable screens cannot
disturb the protective conductor connection.
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. The
screen is connected to the earth by two cable ends.
• 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 plan or to an
element of an earth wire-mesh.
First example: MiCOM C264/C264C fitted without metallic cubicle.
Mechanical Earth
MiCOM C264 - Rear panel
Mechanical Earth
Power supply cable earth should be connected to

Signal cable earth should be connected to
the suitable functional earth connector
the suitable functional earth connector
C0048ENc
FIGURE 8: FIRST EXAMPLE OF EARTHING PLAN

Second example: MiCOM C264/C264C fitted in a metallic cubicle with other devices.
Metallic cubicle
Other device
Earthing braid as
short as possible
Earth Earth
Earth
Earth
Mount cables with Mount cables with

fixings attached to MiCOM Cx64 fixings attached to
the cubicle metallic
or other device the cubicle metallic
surface surface
Earth
Auxiliary power
Earth
Digital boundary
connector
Power Analogue
connector boundary
connector
C0049ENc
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, the alarm relay
(NO contact), 2 optically insulated Digital Inputs (1 common for 2 DI) 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

NOTE: For full IEC Compliance emission a coil should be install on the serial
port N°2 with above reference: WE-742-7113 from Würth Elektronik.
Connector description:
Pin N°. Signal

1 Alarm relay 2 (NO contact)
2 Alarm relay – common 1-2
3 Alarm relay 1 (NO contact)
4 Watch-dog relay (NO contact)
5 Watch-dog relay (NC contact)
6 Watch-dog relay – common
7 Digital Input 1+
8 Common Digital Input 1 / 2
9 Digital Input 2+
10 NC
11 NC
12 RS232: RxD, RS485: B – Port 2
13 Ground – Port 2
14 RS232: TxD, RS485: A – Port 2
15 Ground – Port 1
16 RS232: CTS – Port 1
17 Receive Data (RxD / T+) – Port 1
RS232: RxD, RS485 : B, RS422 : TB
18 Transmit Data (TxD / T-) – Port 1
RS232: TxD, RS485 : A, RS422 : TA
19 Request to Send (RTS / R+) – Port 1
RS232: RTS, RS422: RB
20 R422: RA – Port 1
21 RS232: DCD – Port 1
22 Ground (GND)
23 AC/DC (+) voltage input
24 AC/DC (-) voltage input
TABLE 4: BIU241 BOARD - CONNECTOR DESCRIPTION

Block diagram:
Power auxiliary supply BIU24x

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

WARNING: FOR SAFETY REASONS, WHEN THE BIU241 COMMUNICATION PORT
IS CONNECTED TO DEVICES, IT IS MANDATORY TO EARTH SOME OF
THE "GND PIN" OF THE COMMUNICATION PORT, ACCORDING TO THE
FOLLOWING APPLICATIONS:
RS232:
− If the C264/BIU241/Port 1 is used -> Pin No 13 (GND) is to be earthed
− If the C264/BIU241/Port 2 is used - > Pin No 15 (GND) 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:

Remark: In this case, the GND signal of the daisy chain extremity is not to be
earthed.
4.2 Central Processing Unit – CPU260
This board in it’s base form includes the 10/100BaseT Ethernet interface (RJ45 connector),
and two non-insulated RS232 interfaces (two additional legacy ports).
As options, this board can also include:
• The 100BaseF Ethernet interface (ST connector),
• The IRIG-B interface,

An external module can assume the translation between the two RS232 interfaces and a
insulated RS485 or an insulated RS422 or an optical link.
The factory configuration options for the two additional legacy ports are:
Option Port N°3 Port N°4

0 Without Without
1 Non insulated RS232 Non insulated RS232
2 Non insulated RS232 RS485
3 Non insulated RS232 Optical
4 RS485 Non insulated RS232
5 RS485 RS485
6 RS485 Optical
7 Optical Non insulated RS232
8 Optical RS485
9 Optical Optical
TABLE 5: OPTIONAL LEGACY PORTS (PORTS N°3 / N°4) - CAPABILITIES

Connector description & Block diagram:
Central P rocessing Unit, CPU260

Ethernet-based
communication board
CONNECTORS
1 2 3 456 7 8
10/100 Base-TX
Ethernet-based link
RJ-45
(female)
C0051ENa
FIGURE 11: CPU260 BASE BOARD – CONNECTOR DESCRIPTION / BLOCK DIAGRAM

Central Processing U nit, CPU260

Ethernet-Based
communications board
CONNECTORS
1 23 456 7 8
10/100 Base-TX
Ethernet-based link
RJ -45
(female)
OPTIONAL LINK:
100 Base-FX
Ethernet-based link
ST
(female)
C0052ENa
FIGURE 12: CPU260 BOARD WITH ETHERNET-BASED COMMUNICATIONS – CONNECTOR

DESCRIPTION / BLOCK DIAGRAM

with optional IRIG-B link
board
CONNECTORS
1 23 456 7 8 10/100 Base-TX

Ethernet-based link
RJ -45
(female)
OPTIONAL LINK:
IRIG-B link
C0053ENa
FIGURE 13: CPU260 BOARD WITH IRIG-B INPUT – CONNECTOR DESCRIPTION / BLOCK DIAGRAM

with optional legacy
CONNECTORS
1 23 456 7 8
10/100 Base-TX
Ethernet-based link
RJ -45
(female)
OPTIONAL LINKS:
1 DCD
RS232
2 RXD / T-
1
3 TXD / T+
6
2
5 GND Serial
3
8
4
link 3
9
7 RTS
5
8 CTS #
1 DCD
RS232
2 RXD / T-
1
3 TXD / T+
6
2
5 GND Serial
3
8
4
link 4
9
7 RTS
5
8 CTS
#
C0054ENa
FIGURE 14: CPU260 BOARD WITH LEGACY PORTS – CONNECTOR DESCRIPTION / BLOCK
DIAGRAM
Central P rocessing U nit, CPU260

base and optional
CONNECTORS
1 2 3 456 7 8
10/100 Base-TX
Ethernet-based link
RJ-45
(female)
OPTIONAL LINKS:
100 Base-FX
Ethernet-based link
ST
(female)
1 DCD
RS232
2 RXD / T-
1
3 TXD / T+
6
2
Serial
7
5 GND
3
8
4
link 3
9
7 RTS
5
8 CTS
#
1 DCD
RS232
2 RXD / T-
1
3 TXD / T+
6
2
5 GND Serial
3
8
4
link 4
9
7 RTS
5
8 CTS
#
IRIG-B link
C0055ENa
FIGURE 15: CPU260 BOARD WITH ALL OPTIONS – CONNECTOR DESCRIPTION / BLOCK DIAGRAM
4.3 Digital Inputs module – DIU200

The Digital Input module provides 16 optically isolated digital inputs (with 1 common for 2DI).
Pin N°. Signal

1 Digital Input 1+
2 Digital Input 2+
4 Digital Input 3+
5 Digital Input 4+
7 Digital Input 5+
8 Digital Input 6+
10 Digital Input 7+
11 Digital Input 8+
13 Digital Input 9+
14 Digital Input 10+
TABLE 6: DIU200 BOARD - CONNECTOR DESCRIPTION

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 16: DIU200 BOARD – BLOCK DIAGRAM

NOTE: Different voltage ratings of DIU200 boards exist in the MiCOM
C264/C264C catalogue. Special care must be takes with wetting
voltage for the DI, as there is no hardware protection on the
connector.
Range: Version A01 for 24VDC, A02 for 48/60 VDC, A03 for 110/125VDC
and A03 for 220 VDC
4.4 Digital Outputs module – DOU200

The Digital Outputs Unit (DOU200) board provides 10 outputs (10 DO) using integrated
relays.
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 7: DOU200 BOARD - CONNECTOR DESCRIPTION

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
C0057ENa
FIGURE 17: DOU200 BOARD – BLOCK DIAGRAM

4.5 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.
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 8: CCU200 BOARD - CONNECTOR DESCRIPTION

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 18: CCU200 BOARD – BLOCK DIAGRAM

NOTE: Different voltage ratings of CCU200 boards exist in the MiCOM
C264/C264C catalogue. Special care must be taken with wetting
voltage for the DI, as there is no hardware protection on the
connector.
Range: Version A01 for 24VDC, A02 for 48/60 VDC, A03 for 110/125VDC
and A03 for 220 VDC
4.6 Analogue Input module – AIU200

The Analogue input module (AIU200) provides 4 independent Analogue inputs (4AI).
The AIU200 board is equipped with a 24-way 5.08 mm pitch connector.
Pin N°. Signal

1 Ground
2 NC
3 NC
4 Analogue Input 1+
5 Analogue Input 1-
6 NC
7 NC
8 NC
9 Analogue Input 2+
10 Analogue Input 2-
11 NC
12 NC
13 NC
14 NC
15 NC
16 Analogue Input 3+
18 NC
19 NC
20 Analogue Input 4+
22 NC
23 Receive Data (RxD) – Serial link for
calibration tests only
24 Transmit Data (TxD) – Serial link for
calibration tests only
TABLE 9: AIU200 BOARD - CONNECTOR DESCRIPTION

Block diagram:
Analogue Input U nit AIU200

board
PIN Signal inputs
1
GND
2
3
4 + U
5 - mA/V AI 1
#
6
7
8
9 + U
10 - mA/V AI 2
#
11
12
13
14
15
16 + U
17 - mA/V AI 3
#
18
19
20 + U
21 - mA/V AI 4
#
22
23 RXD RS232
Serial link for
24 TXD calibration te st
only
#
C0059ENa
FIGURE 19: AIU200 BOARD – BLOCK DIAGRAM

4.7 Transducerless Measurements Unit module –TMU200

The Transducerless Measurements Unit module (TMU200) provides 4 transducerless
voltage inputs (VT) and 4 transducerless current inputs (CT).
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 10: TMU200 BOARD - CONNECTOR DESCRIPTION

Block diagram:
Transdurcerless 1A TCU 201 Transdurcerless 5A TCU 200

Current and Voltage + Current and Voltage +
U nit board U nit board
TVU 200 TVU 200
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
C0060ENa
FIGURE 20: CT/VT BOARD – BLOCK DIAGRAM

NOTE: When connecting the system transformers, check to make sure that
the secondary nominal currents of the system and the MiCOM C264
device agree.
4.8 Front panel

The front panel includes the TTL interface (for the communication to the CPU260 module)
and one non-insulated RS232 interface.
This serial port is dedicated to a PC for maintenance and settings.
The properties of the serial link for the maintenance dialogue are:
• Baud rate: 9600
• Databits: 8
• Parity: No
• Stop bit: 1
5 4 3 2 1
9 8 7 6
C0061ENa
FIGURE 21: 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 11: FRONT PANEL - CONNECTOR DESCRIPTION

MiCOM C264C Front panel:
RS232 port: This serial port is

dedicated to a PC for
Maintenance and Settings.
C0062ENb
FIGURE 22: MiCOM C264C FRONT PANEL

MiCOM C264/264C
INSTALLATION
MiCOM C264/264C Page 1/18
CONTENT
2. REQUIREMENT 3
2.1 MiCOM C264 3
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 Front Panel removal 6
4.2 Rack mounting 6
4.3 Front Panel Reinstall 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. POWER UP DELIVERED MiCOM C264 8
7. SETTING COMPUTER 8
7.1 Checking default settings: p command 8
7.2 Settings to enter 9
7.3 Input new settings: c command 9
7.4 Checking communication setting 10
7.5 Installing new software version 10
8. DOWNLOADING DATABASE 11
8.1 Checking connection 11
8.2 Loading DB under SMT 11
8.3 Download DB unto C264 11
8.4 Switch to downloaded data base 11
9. AFTER COMPUTER INSTALLATION 12
10. SOFTWARE INSTALLATION PROCEDURE ON THE HOST PC 12

C264/EN IN/A13 Installation
Page 2/18 MiCOM C264/264C
11. COMPUTER PERIPHERAL INSTALLATION 17

11.1 External master clock connection 17
11.2 Printer installation 17

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 chapter and the
C264/EN RS record sheet.
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 CPU 260 (at least)
• Power board BIU 241

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 chapter C264/EN SA (Safety Handling).
The CPU260 as delivered has installed default factory testing software and database.
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. At start-up when DB is loaded, the
computer software checks that these parameters are identical.
2.2 Personal Computer

A Personal Computer is used for setting and download. Any Windows operating system can
be used. The PC hardware requirement is:
• COM port in RS232C (setting)
• Ethernet port 10 Mb/s or 100 Mb/s (database and software download)
• 100 Mo of free space on hard disk

The PC software's needed is:
• Serial COM terminal (TeraTerm, HyperTerminal…) for Boot Setting
• FTP server for Software download
• PACiS SMT (System Management Software) for database Download

The Serial COM terminal is configured for serial communication with:
• TTY mode
• 9600 Baud/s
• 8 bits no parity
It should be care of selecting into PC application the PORT 1 or 2 that is physically wired to
the computer.
2.3 Communication wiring
The serial link between PC PORT and MiCOM C264 Maintenance port is made via RS232C
straight line.
DB 9 DB 9
5
1 1
5
6 9 1 1
2 2 9 6
3 3
4 4
5 5
Computer 6 6 PC serial PORT
MiCOM C264C 7 7
8 8
9 9
OR
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
C0076ENa
FIGURE 1: SERIAL LINK

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 inspect the packaging for any signs of damage, if there is inform the
delivery agent. Unpack the unit and check for any visible signs of damage.
Check the box for documentation, or computer hardware option added in the delivery form
like ribbon, screws, port extension etc.
Place the computer on a flat surface and remove the front panel has defined in C264/EN HW
chapter.
Without removing the bus PCB, it is possible to see the boards. Their identification is written
on front edge (DIU, DOU…) close to the jumpers used for addresses.
3.2 Delivery form checking
The delivery form is based on the order form issued from CORTEC. It lists computer type,
boards (with supply) and options.
Computer is delivered with all required connectors.
Record in the RS document that all checks have been completed, and record all serial
numbers, the number and type of any boards, plus any additional items supplied with the
ordered.
4. MECHANICAL MOUNTING
The chapter C264/EN HW gives the dimension of MiCOM C264 rack, the fixation diameters
and their position.
If electric screw driver is used the torque limitation should be set to the small diameters of
the screws.
4.1 Front Panel removal
The front face is removed for all assembly and to control board positioning. Front face is to
be replaced before any power-up tests.
Front face is fixed to the rack by 4 (C264C) or 6 (C264) screws (use screwdriver type POZ
1). First loosen all the screws, then remove them one by one. Before removing the last
screw, support the front panel, to avoid to dropping it.
The front panel is connected to the CPU board by a ribbon cable.
4.2 Rack mounting
The rack mounted unit is fixed to a panel assembly by 4 or 6 screws with head POZ 2. The
fixing centres are located under the flaps located at the top and bottom of the unit.
It is possible to install two C264C side by side on the assembly panel or one C264. When
screwing computer rack to the assembly panel it is mandatory to put a washer (and possibly
remove some paint) to ensure a good earth contact.
When computer(s) are screwed to the rack, the rack can be fixed to the panel.
Ensure that the computers are earthed, using the screw terminal on the rear of the unit.
Tighten the screws in a cross pattern (e.g. top left, then bottom right etc), take care not to
over torque the screws.
4.3 Front Panel Reinstall
It is recommended to only fully replace the front panel just prior to energising the computer,
as several checks need to be carried out first.
To re-connect the front panel connect the wire between CPU board and front panel. Tighten
the screws in a cross pattern (e.g. top left, then bottom right etc), take care not to over torque
the screws.
5. WIRING INSTALLATION
Wiring has to be prepared before installation. The MiCOM C264 is delivered with all required
connectors. 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.
On the back of the C264 rack each board and its type should be identified.
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.
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 switch 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 the nominal signal input before plugging
connector to the computer.
DOU, and CCU board generate Digital Output with a defined inductive characteristic. On the
other side of the wire the inductance should be compliant. To avoid damage to the DO board
connected to inductive circuits it may be necessary to connect an anti-surge diode.
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 Legacy
bus (with IED mounted in daisy chain) the correct resistor, at both ends, should be fitted
(120 ohms for RS485 and 150 ohms for RS422).
6. POWER UP DELIVERED MiCOM C264

The MiCOM C264 as delivered has the following installed:
• BOOT PROM start-up software
• Exploitation Software
• Factory Start-up Setting
• Factory Test database

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
DB and settings have not suffered damage during transport.
7. SETTING COMPUTER
The computer has a default factory IP address and alias, these need to be changed to the
application specific values.
Connect the RS cable between the MiCOM C264 and the PC, and run the hyper-terminal
program. If the parameters and wiring are correct, the connection is established, press enter
and a prompt is displayed on terminal:
>
The following chapter explains the operation to configure IP parameters. This is needed to
download the application database (as described in the next chapter). For a standalone
computer IP should be 127.0.0.1.
7.1 Checking default settings: p command
CR is the Carriage Return done with “Enter” key of the PC keyboard.
At the prompt type the following:
>p CR
The following information should be displayed:
“boot device : tffs=0,0
“processor number :0
“host name : <factory host PC name>
“file name : /flash/bin/vxWorks
“inet on ethernet : <factory C264 IP addres xxx.xxx.xxx.xxx>
“inet on backplane : CR
“host inet : <factory host IP adresse xxx.xxx.xxx.xxx>
“gateway inet : 0.0.0.0
“user : <user name>
“ftp password : <password>
“flags : 0x0
“target name : <factory target name>
“startup script :
“other : motfec
>
7.2 Settings to enter

The settings to enter are: -
• factory host PC name: your maintenance laptop network name
• factory host IP address: your maintenance laptop IP@
• factory target name: should be the Computer name defined by SCE for its database
• factory C264 IP address: should be the Computer IP address defined by SCE for its
database
• user name and ftp password: FTP user name, defined for the FTP server - it is good
practice to keep factory setting and to define on the PC user vxWorks with the
password vxWorks
Other parameters should not be modified
7.3 Input new settings: c command
It is now time to configure with the “c” command the communication settings of the MiCOM
C264 Computer.
Enter the Configuration Command:
>c CR
Each parameter is displayed one by one with each CR. If a mistake is press CR several
times, then restart the operation again.
The stored value is displayed. If nothing is entered, pressing CR will keep the stored
parameter.
Only <..> parameter should be entered.
>
>p CR
The following information should be displayed:
“boot device : tffs=0,0
“processor number :0 CR
“host name : <Enter host PC name> CR
“file name : /flash/bin/vxWorks CR
“inet on ethernet : <Enter C264 IP addres: xxx.xxx.xxx.xxx> CR
“host inet : <Entrer host IP adresse: xxx.xxx.xxx.xxx> CR
“gateway inet : 0.0.0.0 CR
“user : <user name> CR
“ftp password : <password> CR
“flags : 0x0 CR
“target name : <target name> CR
“startup script : CR
“other : motfec CR
>
Now restart the computer with the new parameters, either with a power reset, or by typing:
> @ CR
After the reboot the computer C264 will switch into maintenance mode (LED). Computer is
ready for receiving the application database.
7.4 Checking communication setting
If the parameters have been correctly entered, it is possible to communicate, via the terminal
program, using the Ethernet port and the IP address entered above.
At the prompt:
>
type the following (to check the Ethernet parameters)
> p CR
If connection cannot be established, check the parameters on MiCOM C264 via the serial
link. Verify that the PC parameters, host name, IP address, and domain are correct. Refer to
the MF Maintenance faultfinding document for further help.
7.5 Installing new software version
To install new software version refer to the C264/EN MF Maintenance chapter.
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. Data and Structures are defined with
PACiS SCE. When data are entered, PACiS SCE generates a versioned database.
PACiS SMT (System Management Tool) is an application program that can be installed on
any PC, and is used to download the database into computer, then to switch it on. Details of
the PACiS SMT are given in its documentation binders.
8.1 Checking connection
Before downloading the database it is recommended to check the Ethernet link between the
PC_SMT and the MiCOM C264. This is done using a windows DOS session by typing: -
Ping xxx.xxx.xxx.xxx (where xxx is the IP address of the target computer).
If there is no answer, the user should check the communication wiring and/or IP driver
installation.
8.2 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 comms
wiring and settings should be checked.
8.3 Download DB unto C264
Still using right buttons chose the “download all” option and wait for the acknowledgement of
a successful transfer.
8.4 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.
The commissioning procedure can now continue, remember to update the RS record sheet.
In the event of any problems refer to the chapter C264/EN MF Maintenance and faultfinding.
10. SOFTWARE INSTALLATION PROCEDURE ON THE HOST PC

To install a new software version into the computer you need first to have all the necessary
files on a host PC as well as a communication tool to transfer the computer’s software and
the necessary configuration files into the C264 computer.
While you have insert the PACiS CD-ROM System installation into your CD-reader you will
find the install software of the computer into the following directory:
\System\Delivery\PACiS V2.0.1\C264 V2.08A
The install procedure name is:
Computer_2.08A.exe
Double click on this executable and follow the procedure:
FIGURE 2: SETUP PROCEDURE

Check the number of the right version of the computer’s you need to install and click on the
next button:
FIGURE 3: LICENSE AGREEMENT

Choose the “I accept the agreement” radio button then click on the next button:
FIGURE 4: DESTINATION DIRECTORY

Check that you have enough disk space.
If you choose an another install directory take good care that you will need to configure the
FTP tool to communicate with the computer with the proper place.
Then click on the next button:
FIGURE 5: SELECT COMPONENT

Choose the components you want to install, you may have already an FTP tool or other
components you don’t want to erase.
Then click on the next button:
FIGURE 6: START MENU

Choose if you want an item in your start menu.
FIGURE 7: ADDITIONAL TOOL

Choose if you want a PACiS FTP desktop icon. Otherwise you ca the choice to launch this
tool from the start menu.
FIGURE 8; READY TO INSTALL

Click on the next button at this time a progress dialog box will appear. Wait for the
installation to be completed.
FIGURE 9: INSTALL COMPLETED

Now you have the choice to launch the PACiS FTP Server. The connection with the
computer needs to be established to make this operation success.
To see the files that have installed otherwise to check the installation is completed see the
chapter Commissioning (C264/EN CM).
11. COMPUTER PERIPHERAL INSTALLATION

Additional options to be installed.
Check the delivery form for any options that should be installed, software options are
integrated into the software version but are activated from PACiS SCE.
Optional hardware modules are:
• IRIG B connection
• Printer
11.1 External master clock connection
With the option of the CPIU board, an external standard BNC connection is used to receive
external master clock synchronization. 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 C264/EN IN chapter.
External IRIG B synchronization should be configured in the computer database.
11.2 Printer installation
A printer can be installed permanently for the SOE, or temporally for
commissioning/maintenance use. Data labeling is defined with PACiS SCE.
The printer should be connected to either port 2 or port 4 of the computer (ports 1 and 3 are
used for LBUS or TBUS communication).
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 (include in database) has to be installed onto the computer
with the printer communication parameters.
BLANK PAGE
MiCOM C264/C264C
APPLICATION
CONTENT
2. REQUIREMENTS 3
3. COMPUTER DEFINITIONS 4
3.1 Kind of computers 4
3.2 Computer definitions 4
3.3 Adding a computer 4
3.4 Default components 5
3.5 Adding objects to the computer component 6
3.6 Computer’s component relations 7
3.6.1 Standard relation definitions 7
3.6.2 Right relations 7
3.6.3 Redundancy relation 7
3.7 Computer boards general 8
3.8 Computer specific board 9
4. COMPUTER ATTRIBUTES 10
4.1.1 General 10
4.1.2 Binary input (BI) filtering 10
4.1.3 Measurement values 11
4.1.4 Counter attributes 12
5. COMPUTER PROFILES 13
5.1 Profile definition 13
5.2 Profile location 14
5.3 Profiles of SPS, DPS, MPS 14
5.3.1 General 14
5.3.2 State labels 15
5.3.3 State treatment 16
5.3.4 Interlocking 16
5.3.5 Alarms 17
5.4 Profile of Measurement values 17
5.4.1 General 17
5.4.3 Interlocking 18
C264/EN AP/A13 Application
5.4.4 Alarms 19
5.4.5 Mean value 19
5.5 Profile of Counter 20
5.5.1 General 20
6. SITE 21
6.1 Bay Specific 21
6.2 Models 21
6.3 Build-in functions 21
6.4 Data Point 21
7. SUBSTATION CONTROL SYSTEM 22

7.1 Computer System Information 22
7.2 UCA2 Mapping 23
7.3 Legacy Bus (L-BUS) 23
7.3.1 Configure a physical port 24
7.3.2 LBUS Communication 26
7.3.3 IED on legacy bus 27
7.3.4 IED on T103 28
7.3.5 IED on Modbus 37
7.4 Telecontrol Bus (T-BUS) 42
7.4.1 Adding a SCADA protocol 42
7.4.2 Configure a physical port 43
7.4.3 TBUS Communication 44
7.4.4 System data information 48
7.4.5 SCADA communication addresses 49
7.4.6 SCADA link addresses 50
8. USE CASES 52
8.1 Standalone computer 52
8.2 Bay computer 52
8.3 PLC computer 52
9. APPLICATION CASES 52
9.1 Consignment of a Data Point 52
9.2 Transmission of GOOSE 52

The present document is a MiCOM C264/C264C chapter of the documentation binder. This
document is intended to present you how to configure the Computer. It is the chapter
Application (AP) of this Product.
This document is divided in tree main parts. The first part: Computer definition describes all
kind of computers and introduces a general presentation for each one. The second part is
composed of the Use cases of computers and a description of all the objects that are to be
configured in a presentation that looks like the sub-tree presentation of the SCE application.
And finally the third part presents some specific cases of application.
Notation used in this document: all the menus, items or any text that appear in the SCE
Application windows will be surrounded by quotation marks like: “File” menu.
2. REQUIREMENTS
First, if it is not already done, you will need to install the PACiS SCE (System Configuration
Editor), see the chapter IN (Installation) of this product.
This document presents you the objects and the attributes of a referenced database made
with the PACiS SCE. For understanding this document you first need to be familiar with
PACiS SCE.
To add an UCA2 computer into an existing system you need to have the mapping of the
system (UCA 2 bricks name, IP address, Network names of equipment, …).
To generate a template, for an existent UCA2 computer, see the chapter of the SCE product.
3. COMPUTER DEFINITIONS
3.1 Kind of computers
There are two models of computers: C264 and C264C.
The C264 is a large size computer (80TE) and C264C is the compact one (40TE). The
height for the both computers is 4U.
The following chapters are discussing about a general presentation of these computers.
3.2 Computer definitions
The different kinds of computer have the following features:
Type Width Hardware Bus width Input/Output

C264C 40TE BIU: 2 serial ports 4/6 free slots DIU, DOU,
CPU: 2 serial ports optional CCU, TMU
GHU: LCD + leds
C264 80TE BIU: 2 serial ports 14/15 free slots DIU, DOU,
CPU: 2 serial ports optional CCU, TMU
GHU: LCD + leds
The configuration system of these computers is located in the Ethernet Network.
Computer is located on Ethernet station bus.

3.3 Adding a computer
An addition of a computer definition is done under SCE via the “Object entry” area by clicking
on mouse’s right button as the following:
FIGURE 1 : ADDING A COMPUTER

3.4 Default components
When you add from the “Objects Entry” view, for example a C264C computer you will obtain
the following sub-tree of the computer definition with the default components as follow:
Bin der Hardware

BIU
CPU Port definition
GHU Led, LCD
(include board statu s)
Binder System Information

Computer System Data Point
(DB status, device mode…)
Binder UCA2 Mapping

Mandatory LD0 + user LD
(LD0 of Cx6x System Information)
Program m ing Logic Chart

ISAGRAF project directo ry
FIGURE 2 : DEFAULT COMPONENTS OF THE COMPUTER
To make a real working computer you will to add several other components coming from the
“Object entry” area.
3.5 Adding objects to the computer component

To get this view you need to select the C264 object in the Substation Control System (Scs)
sub-tree of the Object view, the Objects entry view contains the objects you need to add into
your computer definition depending on the application you want.
(1)
(4)
(3)
(2)
(5)
(6)
FIGURE 3 : ADDING OBJECTS

(1) Specific I/O boards: AIU, CCU, DIU, DOU, SCU, and TIU
(2) Computer SBUS Mapping for communication in the Sub-station
(3) Datapoint profiles definitions for profiling I/O
(4) LBUS Mapping, Legacy network with different protocols DNP3, Modbus, T101, T103
for IED communication
(5) TBUS Mapping, telecontrol bus for SCADA communication
(6) Computer printer
Those names are the default ones but all can be customised.
3.6 Computer’s component relations

3.6.1 Standard relation definitions
This relation allows you to locate the computer in a specific “Substation” at the “Site” level.
is located in: <null>
3.6.2 Right relations
These relations are inherited from the upper level.
has for command right: Command right
has for Forcing/Sub./Sup right: Command right
has for ind. AckClear right: AI ack right
has for UCA2 server: UCA2 physical device

3.6.3 Redundancy relation
is backup of: another UCA2 physical device

3.7 Computer boards general

After adding a DIU200 board you will get the following sub-tree for this board definition:
(1)
(2)
(3)
(1) Computer’s relation: has for profile: <null> need a MPS board profile with for example
the following Labels:
0 OK defined
1 Faulty
2 Missing
3 Not defined
4 OK not defined not present
(2) This relation appear when you will make the UCA2 mapping using the “Relation link
editor” by double click on C26x UCA2 Map\LDO for C26x\…\DIUSt0. Take good care
that board numbers are equal.
(3) Name to be customised using for example the following name: DIU_00 (that is a good
practice). Idem for names of the DI # 0 that you can rename DI # 00 to have names in
the order.
3.8 Computer specific board

Computer’s boards have the following features:
DIU : 16 DI
DOU : 10 DO
AIU : 4 AI (AI range +short/long acquisition cycle)
CCU : 8 DI, 4 DO (take good care the DO 4,5,6,7 are defined but not used)
TIU : 4 I, 4 U (Acquisition attribute AC at TIU
Recommended:
Use board names that include number and slot reference like: C, D, E, F…
4. COMPUTER ATTRIBUTES
4.1.1 General
This view contains the general attributes of the computer, Ethernet address, Network name
for the computer.
(1)
(2)
(3)
FIGURE 4 : GENERAL ATTRIBUTES

(1) Name used for logging, alarms, …
(2) Indicate if the computer has a CPU 260 with IRIG B option synchronised by the S-
BUS. The relation at Scs level “Has for master clock” defines which device is the
synchronisation source.
(3) Computer network alias name for TCP/IP
4.1.2 Binary input (BI) filtering
Digital Input and Binary Input are debouncing then filtering (for all SPS/DPS)
(1)
(2)
(3)
FIGURE 5 : BI FILTERING
(1) Debouncing delay: debouncing time in ms, range [0..10] by step of 1 ms
(2) Filtering delay >= Stabilisation time if Debouncing time > 0
in ms range [0..20] by step of 1ms
DI Voltage
~40%
Filtering time
Deboucing
time
t0 t1 t2
C0113ENa
FIGURE 6 : EVENTS
Event time tag: t0
Transition time: t2
(3) Toggling delays are defined as the following:
Invalid State TOGGLING

xPS State
Changes
Toggling Delay Toggling End New Valid State
1 2 3 4 Delay
t0 t1 t2 t3
C0114ENa
FIGURE 7 : TOGGELING DELAY

4.1.3 Measurement values
(1)
(2)
(3)
(4)
FIGURE 8 : MEASURMENTS VALUES ATTRIBUTES

(2) Analogues measurements AIU, acquisition samples ranges [500..10000] by 500 ms or
[100..1000] by 100 ms
(3) TMU board with CTVT fundamental 50, 60 or 16 2/3 Hz number of harmonics fixed to
16
(4) UCA2 transmission period [100..60000] by 100 ms or [1..600] by 1 s other
transmission definition into profile
4.1.4 Counter attributes
(1)
(2)
FIGURE 9: COUNTER ATTRIBUTES

(2) Number of software faults allowed in period else Computer remains in HALT mode
(safety: something goes wrong)
5. COMPUTER PROFILES
5.1 Profile definition
For several Data Points profile defines the same treatment. It means that if you define the
DPS of all Switch Gears with the same profile to be logged they all will be logged.
In the same way all alarm indication can be logged and alarmed.
The goal is to have only few profiles for substation’s DP and also to reduce the size, errors
and easy modification of Databases.
Defined into a profile you will have for all DP:
• common sates labels:
− open/close, set/reset, on/off, order open/order close
• common treatment
− archived
− logged on printing
− acquisition,
− FSS and SBMC options
− Direct execute or SBO control options
• common sate treatment:
− alarms by sate
− Boolean value by state

The kind of Profiles you can have is the following:
• Supervision profiles for: SPS, DPS, MPS, MV and Counter
• Control profiles for: SPC, DPC, MPC and SetPoint

Reminding definition of FFS:
− Forced: a DP in invalid state can be set to a valid value/state Automatically or

Manually defined at the Datapoint level
− Suppressed: a DP in any valid state can be set to an invalid value/state

Reminding definition of SBMC:
Site Based Maintenance Control facilities for RPC. When in a Bay the SBMC is set:
1. DP are transmitted to SCADA in configured Substitute SBMC state
2. Even if station is remote, on this bay: OI control are accepted and Gateway control are
refused
When reset current value/state are restored to SCADA.
5.2 Profile location

As all system treatments profiles are defined in the Scs hierarchy.
The Relations involved are “has for profile” from all DP (in Site or Scs hierarchy) to a special
profile.
5.3 Profiles of SPS, DPS, MPS
5.3.1 General
(1)
(2)
(3)
FIGURE 10 : DPS PROFILE

(1) Allow FSS on DP value: Yes/NO
(2) Allow SBMC on DP when the bay has SBMC set
(3) Toggling Filtering for SPS DPS value: Yes/No
SBMC Substitute value to RCP:
• SPS: Set/Reset/Suppressed
• DPS: Jammed/Open/Close/Suppressed
• MPS: Undefined/Suppressed
5.3.2 State labels

The state labels of a DPS is as the following, with to parts one is specific to the kind of DP
(single, double or multiple) and one is for invalid states:
(1)
(2)
FIGURE 11 : STATE LABELS

(1) for SPS: Set/Reset, for MPS: I among N (<16) state0 to state15/undefined
(2) Invalid states or FSS labels
Labels are business language dependent and can be customised.
On OI printer and viewers a label is a concatenation of Force/Substitute &Value
(open/close).
Profile is linked to a DP then words can change:
DPS for Switch gear: Open/Close
DPS for R/S Substation: Remote/Local
For a MPS N and the associate DP impact labels.
5.3.3 State treatment
FIGURE 12 : STATE TREATMENT

Treatments can be:
• No archive, No logging
• Archive and Logging
• Archive only
Archived means send to OI server and the LCD display.
Printing relation can be used several times with different printers:
• Has Alarm Logged On
• Has Events Logged On

5.3.4 Interlocking
FIGURE 13 : PROFILGING INTERLOCKING

For each state of MPS you must define a Boolean value that will be used in Interlocking
equations and PSL.
To an invalid state case a third value is introduced “Invalid”.
Invalid state is automatically invalid state for Interlocking equations.
5.3.5 Alarms
(1)
(2)
(3)
(4)
(7)
(5)
(6)
FIGURE 14 : ALARMS
(1) Alarm generation: Appearance only mean 1 alarm, Appearance and disappearance
means 2 alarms
(2) Defined means the state is alarmed
(3) Spurious: the DP is Set and never Reset
(4) The alarm is not generate if state follows a control (RFI UCA2)
(5) Gravity level
(6) Alarms are acknowledged by operator, but clearing can be manual or automatic
(7) All this features are repeated for each valid or invalid sate
5.4 Profile of Measurement values
5.4.1 General
(1)
(2)
(3)
FIGURE 15 : MV PROFILE GENERAL

(1) Allow FSS on MV
(2) Allow SBMC on MV (when bay in SBMC set) Substitute value is suppress
(3) MV value displayed on OI Mimic
5.4.2 State labels
(1)
(2)
(3)
(4)
(5)
FIGURE 16 : MV PROFILE STATE LABEL

(1) IED is disconnected
(2) Board acquisition is saturated
(3) Digital measurement coding error
(4) 4 to 20 mA DC input when under 4 mA
(5) 4 to 20 mA DC input when under 4 mA
5.4.3 Interlocking
The goal is to include MV validity and MV threshold into Boolean acquisition.
FIGURE 17 : MV PROFILE INTERLOCKING

(1) True means the MV is available.
(2) False means the MV is valid but not into the “Nominal range”.
(3) Invalid means invalid into equation then the result is invalid and finally false.
(4) Another example: you can use L and H bounds to create informations like Dead or
Live for V Line and V Busbar.
5.4.4 Alarms
Alarm management is as the xPS management you can define the same features for each
valid or invalid sates.
FIGURE 18 : MV PROFILE ALARMS

5.4.5 Mean value
PACiS OI archive computation mean per hour/day/week/month/years.
FIGURE 19 : MEAN VALUE

5.5 Profile of Counter

5.5.1 General
(1)
(2)
FIGURE 20 : COUNTER PROFILE GENERAL

(1) Counter (Accl on UCA2) is an integer then the coefficient to get energy on the OI.
(2) Activate pulse conversion or not on the OI.
Energy metering can be issued from Computer (then into a DP) or from the OI (then those
attributes).
5.5.2 State labels
(1)
(2)
FIGURE 21 : COUNTER PROFILE STATES LABEL

(1) Saturation of accumulator
(2) DCT: Double counter when there is no complementary of inputs
6. SITE
Configure voltage level
Bay level
− Define a bay BusBar, BusSectioner, BusCoupler, Feeder, Transformer, Generator and

Motor…
Voltage level
L/R substation
6.1 Bay Specific
L/R bay
SBMC
Order running
6.2 Models
Switch gear
Circuit Breaker
Transformer
Motor
Generator
6.3 Build-in functions
AR
Synchro-check
ATCC
6.4 Data Point
ST CO
Profile process
Relations
7. SUBSTATION CONTROL SYSTEM

7.1 Computer System Information
By default you will get this system informations:
FIGURE 22 : SYSTEM INFORMATION

DB compatibility (SPS)
DB incoherency SPS
DB switch control (SPC)
Device link (SPS)
Device mode (DPS)
DI acquisition stopped (SPS)
Local/Remote control (DPC)
Local/Remote control (DPS)
Log Queue (SPS)
Mode control (DPC)
Software error (SPS)
Software compatibility (SPS)
Synchronisation (SPS)
Test control (DPC)
Watchdog (SPS)
Add an UCA SPS datapoint in case of controlling an UCA2 distance protection.
7.2 UCA2 Mapping

Is mandatory system information.
FIGURE 23 : UC2 MAPPING

7.3 Legacy Bus (L-BUS)
Defining a legacy network depending on the use to be done with the computer you need to
configure a communication port.
The objectives of this chapter is to show you how to:
• Configure a physical port
• Configure the legacy bus communication
• Configure LBUS with IED
• See the acquisition on T103 IED

7.3.1 Configure a physical port

This port can be configured on the CPU or the BIU board.
(1)
(2)
(3)
(4)
FIGURE 24 : PHYSICAL PORT

(1) System UCA2 device: Computer
(2) Hardware binder inside of which there are all boards
(3) port 1&2 on BIU board RS232 or RS485
(4) port 3&4 on CPU RS232 only
Port 2 is used by LBUS this is a relation from LBUS
An external converter to RS485 copper/optical can be used
7.3.1.1 LBUS port attributes
General
(1)
(2)
(3)
FIGURE 25 : LBUS PORT ATTRIBUTES

(1) With BIU you can select the kind RS232 or RS485
(2) With CPU the kind is always RS232
(3) Computer inner port name (used in run-time for expert level
Port transmission parameter
(1)
(2)
(3)
FIGURE 26 : PORT TRANSMISSION PARAMETER

This port is configured as is: RS485 T103 Modbus
(1) Common transmission parameters

speed: 1200 to 64000
parity: NO/Even/Odd
stop: 1/1.5/2 (bit duration)
byte: 7/8
(2) Tx soft or switched (RS485)
(3) Not used, reserved for TBUS communication with SCADA
7.3.2 LBUS Communication

7.3.2.1 Definition
(1)
(2)
(3)
(4)
FIGURE 27 : LBUS COMMUNICATION DEFINITION

(1) Legacy network binder
(2) One LBUS definition for each physical port (or channel)
(3) Relation “has for main comm. port” for each legacy protocol filled with : “RS232/485
port 2”
(4) For each IED Acquisition type + disturbance, IED definition + mapping
7.3.2.2 Communication port attributes
(1)
(2)
(3)
(4)
(5)
FIGURE 28 : LBUS ATTRIBUTES

(1) Retry after failure [1..10]
(2) TO for IED answer [1..300]
(3) Time synchronisation
(4) Delay before disconnecting IED [10..100]
(5) Kind of synchronisation: T&D EAI or None
7.3.3 IED on legacy bus
• Typical Template Case Why...
− Big IED-LBUS Mapping
− Data to be linked to UCA2 (OI archives, prints, GTW)
− Data to be linked to Process (profiles, automation)
• Template definition
− Kind of Legacy BUS
− Mapping size
− Association to sub-templates (graphic)

IED definition
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 29 : IED DEFINITION

(1) Process data profiles AI, print
(2) IED data on UCA2, Bricks
(3) IED LBUS Acquisition +DREC definition
(4) IED system information IED Diag: connection, synchronisation, DREC
(5) LBUS mapping
(6) Linked features, graphic for IO
7.3.4 IED on T103
7.3.4.1 Attributes
(1)
(2)
(3)
FIGURE 30 : IED ATTRIBUTES

(1) System object naming
(2) IED @ on legacy bus
(3) DREC: disturbance recording with basic file name upload by SMT on OWS hard disk:
BayName_Dname_N°) DREC is parameterised in IED acquisition
7.3.4.2 Hierarchy
(1)
(2)
(3)
FIGURE 31 : IED HIERARCHY

(1) System information upon IED LBUS
− Communication
− Disturbance
− Synchronisation
(2) System Information on UCA2
− IEDDIAG
− RDRE (disturbance)
(3) Legacy BUS Mapping
− to be linked to Site_DP
− Site_DP linked to UCA2 Mapping

7.3.4.3 T103 - Recall
68h
Lenght 1
Lenght 2 10h
68h
C Control Flow control (Class / Function send ack confim)
A Adress 1/2 @ GTW from SCADA

Link User Data or ASDU Identifier Protocolar :
1,2,65,66,67,68SPS,DPS
Application 3,4,9,73,77 MV
20,45,46 SPC, DPC
Service Id Structure 81h
COT Cause Of Transmission
Data Cyclic
Spontaneous
Unit Common @ ASDU = IED @ except differential
Function Number Wasinitially protective function number
Can be resereved
Information Number
Information Value 1=OFF 2 ON
Time (with synchronisationattribute)
(Sequence pointer) 1 first
Information …
CRC CRC
16h 16h
C0115ENa
FIGURE 32 : T103 RECALL

7.3.4.4 T103 - SPS mapping
(1)
(2)
(3)
(4)
(5)
FIGURE 33 : T103 SPS MAPPING

(1) Mapping name Relation to “Site” SPS for any treatment: “has for IED address”
(2) T103 ASDU
(3) T103 Function Number
(4) T103 Information Number
(5) T103 Common Address of ASDU. Usually IED address (-1) with exception like
differential @+1 for function on primary secondary
T103 Valid ASDU for SPS: 1,2,65,66,67,68
7.3.4.5 T103 - DPS mapping

Two single information to create Double DPS.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 34 : DPS MAPPING

(1) Mapping name Relation to “Site” DPS has 2 relation (if public ASDU): “has for IED
address”
(2) T103 ASDU
(5) T103 Common Address of ASDU. Usually IED address (-1)
(6) Unused for private ASDU DPS Open/Close 2 public ASDU (IED_SPS) to create DPS
T103 Valid ASDU for DPS: 1,2,65,66,67,68
7.3.4.6 T103 - MV mapping

Same goal MV rank + MV protocol format
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 35 : MV MAPPING
(1) Mapping name to Site MV, relation “has for IED address”
(2) T103 ASDU
(5) T103 ASDU MV 3, 9rank (several MV)
(7) T103 MV (format signed or not … )
Associate Site MV has a MV_Profile with scaling (CT/VT, RMS…)
T103 Valid ASDU for MV: 3, 4, 9, 73, 77
7.3.4.7 T103 - SPC mapping
(1)
(2)
(3)
(4)
(5)
FIGURE 36 : SPC MAPPING

(1) Mapping name to Site , relation “has for IED address”
(2) T103 ASDU
(5) T103 ASDU MV 3, 9rank (several MV)
(7) T103 MV (format signed or not … )
T103 Valid ASDU for SPC: 20,45,46
7.3.4.8 T103 - DCP mapping

Open/Close SPC in DCP
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 37 : T103 DCP MAPPING

(1) Mapping name to Site , relation “has for IED address”
(2) T103 ASDU
(6) Direct Execute / SBO private
(7) Open / Close control
T103 Valid ASDU for DPC: 20,45,46
7.3.4.9 T103 - IED Acquisition
(1)
(2)
(3)
(4)
(5)
FIGURE 38 : IED ACQUISITION

(1) IED Type: Standard,Px3x, Px4x
(2) IED Main function type T103 (DREC)
(3) General Interrogation Sampling
(4) T103 special acquisition parameters, MV are Normalised (% Nominal) MV coefficient
1.2 2.4
(5) Mainly ASDU 3 (Measurement), For each IED Setting group
MV Value = 1.2
• Nominal
• Transmitted value
7.3.4.10 Disturbance Channels definition
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
FIGURE 39 : DISTURBANCE CHANNEL DEFINTION

(1) Digital channel (on/off) contact, function
(2) Name given in Disturbance File
(3) T103 corresponding @
(4) Analogue channel (Measurement)
(5) Name to give in Disturbance File
(6) Name into disturbance file
(7) Channel number (implicit with DI)
(8) Channel number (implicit with DI)
(9) ?
(10) ?
(11) ?
7.3.5 IED on Modbus

7.3.5.1 Attributes
(1)
(2)
(3)
FIGURE 40 : IED MODBUS ATTRIBUTES

(1) System object Naming
(2) IED @ on LBUS
(3) DREC (Disturbance Recording) with basic file name uploaded
7.3.5.2 IED on ModBus Recall
Query Device @ Function @ in IED Number CRC

Xxh 03h xx xxh Xxh xx xxh
Response Device @ Function Counter Value … CRC
xxh 03h 0..Number Xx xxh Xx xxh
@IED Function
Mapping @ Value format
number
Function MODICON ALSTOM Master

01 0x01 Read Coil Status R. n bits
02 0x02 Read Input Status R. n bits
03 0x03 Read Holding Registers R. n words
04 0x04 Read Input Registers R. n words
05 0x05 Force Single Coil W. 1 bit
06 0x06 Preset Single Register W. 1 word
07 0x07 Read Exception Status Fast R. 1 byte
08 0x08 Diagnostics
Sub-Func
15 0x0F Force Multiple Coils W n bits
16 0x10 Force Multiple Regs W. n Words
C0116ENa
FIGURE 41 : MODBUS RECALL

7.3.5.3 Modbus - SPS Mapping
(1)
(2)
(3)
(4)
(5)
FIGURE 42 : MODBUS SPS MAPPING

(1) Mapping Name => Relation to Site SPS for any treatment “has For IED Address”
(2) Word/Bit @ (depend of reading function)
(3) Bit number (with read function 3,4,7)
(4) Modbus reading function
1,2 bit
3,4 Word
7 Status byte
(5) Not used
7.3.5.4 Modbus - DPS Mapping
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 43 : MODBUS DPS MAPPING

(1) Mapping Name => Relation to Site DPS
(2) Word/Bit @ (depend of reading function)
(3) Bit number (with read function 3,4,7)
1,2 bit
3,4 Word
7 Status byte
(5) Not used
(6) Open or Close contact
7.3.5.5 Modbus - MV Mapping
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 44 : MODBUS MV MAPPING

(1) Mapping Name => Relation to Site MV
(2) Word @
(3) Not used
3,4 Word
(5) Not used
(6) Not used
(7) Modbus MV format (see later)
7.3.5.6 Modbus – SPC Mapping
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 45 : MODBUS – SPC MAPPING

(1) Mapping Name => Relation to Site SPC
(2) Word @
(3) Bit @
(4) Modbus Writing function
6, 7 W 1, n bit
(5) Not used
(6) Direct/Execute or SBO
7.3.5.7 Modbus – DPC Mapping
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 46 : MODBUS – DPC MAPPING

(7) Mapping Name => Relation to Site DPC
(8) Word @
(9) Bit @
(10) Modbus Writing function
6, 7 W 1, n bit
(11) Not used
(12) Direct/Execute or SBO
(13) Open or Close contact
7.3.5.8 Modbus - IED Acquisition
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 47 : MODBUS IED ACQUISITION

(1) Name given to acquisition object
(2) Standard Modbus MODICON
(3) M300 Pseudo Modbus T&D EAI
(4) S20 Standard Modbus MODICON
(5) Acquisition polling to SPS connected
(6) Function 7: fast diagnose byte reading
7.4 Telecontrol Bus (T-BUS)

Defining a SCADA network depending on the use to be done with the computer you need to
configure a communication port with the SCADA.
Available protocols:
• IEC 60870-5-101 (T101 serial link)
• DNP3 (serial link)
• IEC 60870-5-104 (T104 Ethernet link)

7.4.1 Adding a SCADA protocol
You need to add a specific object to configure the SCADA communication.
FIGURE 48 : ADDING A SCADA COMMUNICATION

Once you click on the “Add” button the following object appear in the definition of the
computer:
FIGURE 49 : SCADA COMMUNICATION OBJECT

This object “C26X SCADA networks will manage SCADA communication.
7.4.2 Configure a physical port
For DNP3 and T101 protocols a connection with a serial port is needed.
This connection will be configured by filling the relation “has for main comm. port” by double
clicking on this relation:
FIGURE 50 : CONFIGURE A PHYSICAL PORT

Once a serial port on the BIU board is selected click on the “Ok” button.
7.4.3 TBUS Communication

7.4.3.1 Definition
The “C26X SCADA prot” object as the following definition:
(1)
(2)
(3)
FIGURE 51 : C26X SCADA PROTOCOL DEFINITION

(1) System data profile definition
(2) UCA2 mapping
(3) Communication port relation
7.4.3.2 Communication port attributes

Depending on the communication protocols chosen for SCADA communication. You have
different attributes to configure.
T101 SCADA Communication attributes:
FIGURE 52: T01 PROTOCOL ATTRIBUTES

interlocking protocol:
Interlocking protocol Management of the taking control

No Interlocking protocol No management of the taking control
link address length: in range [1..2]

link address: in range [1..255] or in range [1..65534]
redundant link address: in range [1..255] or in range [1..65534]
ASDU common address length:
ASDU common address:
information object length:
Address on 8 bits (1 byte) 1 byte

Address on 16 bits (2 bytes) 2 bytes
Address on 8 bits 8 bits 2 bytes
Address on 8 bits 16bits 3 bytes
Address on 8 bits 8 bits 8bits 3 bytes
frame max length: in range [0..255]

cause of transmission length: length of the field cause of transmission (COT). This
information is important to decode the frame
Address on 8 bits 1 byte

Address in 16 bits 2 bytes
MV periodic cycle (in s): in range [0..65534], duration cycle in seconds for sending
measurements. 0 means non-periodic
binary time size: indicate in which size the date of events is coded, two formats:
CP24Time2A time code on 3 bytes

CP56Time2A time code on 7 bytes
number of event record: in range [0..99], maximum number of event records

event record max size: in range [10..65535], size maximum of an event record in bytes
background scan cycle (s): in range [0..65535], duration of a background cycle in seconds
for sending measurements.
DNP3 SCADA Communication attributes:
FIGURE 53 : DNP3 PROTOCOL ATTRIBUTES

Interlocking protocol management of the taking control

No Interlocking protocol no management of the taking control
link address length: in range [1..2]

link address: in range [1..255] or in range [1..65534]
address structure:
Address on 16 bits (2 bytes)

Address on 32 bits (4 bytes)
SPS/DPS class: class of priority associated to the TS
1 most
2 middle
3 less
MV class: class of priority associated to the AI
1 most
2 middle
3 less
counter class: class of priority associated to the Meters
1 most
2 middle
3 less
SCADA synchronisation: Affect the management of the synchronisation message coming

form the SCADA
Yes management of the synchronisation message

No no management of the synchronisation message
T104 SCADA Communication attributes:
FIGURE 54 : T104 PROTOCOL ATTRIBUTES

Interlocking protocol management of the taking control

No Interlocking protocol no management of the taking control
TCP/IP address:
ASDU common address:
information object length:
Address on 8 bits 16bits 3 bytes

Address on 8 bits 8 bits 8bits 3 bytes
MV periodic cycle (in s): in range [0..65534], duration cycle in seconds for sending
measurements. 0 means non-periodic
number of event record: in range [0..99], maximum number of event records

event record max size: in range [10..65535], size maximum of an event record in bytes
background scan cycle (s): in range [0..65535], duration of a background cycle in seconds
for sending measurements.
T0: connection time-out (s):
T1: APDU time-out (s):
T2: acknowledgement time-out (s):
T3: test frame time-out (s):
K: sent unack. frames (window size):
W: ack. received frames (window size):
max command delay (s):

7.4.4 System data information
7.4.4.1 Definition
System data has the following definition:
FIGURE 55 : SYSTEM INFORMATION DEFINITION

7.4.4.2 Attributes
To configure System information you will to deal with the following attributes:
FIGURE 56 : SYSTEM INFORMATION SPS ATTRIBUTES

7.4.5 SCADA communication addresses
7.4.5.1 Definition
SCADA communication addresses has the following definition:
FIGURE 57 : SCADA COMMUNICATION ADDRESS

7.4.5.2 Attributes
SCADA communication addresses has the following attributes:
FIGURE 58 : SCADA COMMUNICATION ADDRESS ATTIBUTES

7.4.6 SCADA link addresses
To get information on an electrical data point trough the SCADA communication link you
need to configure a relation for this electrical data point. Under the “Substation” tree select
the “Comp. swit. pos.” as the following:
FIGURE 59 : SCADA LINK ADDRESS

Right-click on the “Add” button to add a relation “has for SCADA address” under the “Comp.
swit. pos.” object. Then double-click on the relation to make appear the Relation link editor:
FIGURE 60 : FILLING HAS FOR SCADA ADDRESS RELATION

Once you’ve selected the “Gtw DPS addr” object in the C264 computer object sub-tree click
on the “Ok” button.
8. USE CASES
Here are explanations of different types of utilisation for computers.
8.1 Standalone computer
For this kind of Computer UCA2 mapping can be skipped.
8.2 Bay computer
Computer aim is to manage specific bay like Feeder Transformer Generic and Busbar.
8.3 PLC computer
A Generic bay must be defined at the Site level that deals with Input/Output.
9. APPLICATION CASES
9.1 Consignment of a Data Point
If you want to consign a DP it needs to have a profile with a printing relation with an existing
printer.
Don’t forget to check that the printer is connected to a computer that has a port configured
as a printer port.
Check that the OI is a client.
9.2 Transmission of GOOSE
A computer is a client of a GOOSE by the relation as for server. From the client point of view
nothing can indicate that the computer is not going to receive all the GOOSE but a filter is
realised by the SCE at the generation time the GOOSE is remove from the data model of the
computer when he is not needed.
MiCOM C264/C264C
SETTINGS
CONTENT

1.1 Tree Panel Navigation 3
1.2 Tree Panel Organisation 4
2. CONFIGURATION OF VIEW PANELS 5

2.1 Bay display 5
2.2 Synchrocheck 5
2.3 Communication display 5
2.4 Devices display 6
2.5 Counters 6
2.6 Measurements 7
2.7 Transformer Tap Position 7
3. PARAMETERS/HMI PANELS 8
3.1 Bay Panel 8
3.2 Main LCD settings 8
3.3 Display options bay panel 9
4. PARAMETERS/TREATMENT PANELS 11
4.1 Synchrocheck 11
4.2 Serial Communication 12
4.3 Devices control timers 13
4.4 Measurements acquisition 13
4.5 Tap Changer Control Delays 14
C264/EN ST/A13 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 Cx64 computers. The
setting is done through the LCD Local Control Display which is defined in C264/EN HI
(Human Interface) part.
This Chapter defines settings with default and range values. The above chapter is extracted
from the C264/EN HI chapter and summarises operator actions. These operations are found
in the set part of display panel referenced as "Tree Panels".
1.1 Tree Panel Navigation
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. For control, setting and edit modes allow 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 Organisation

At this hierarchy level, only the left part setting is considered in this chapter.
BAY_01
C264 C264 C264

Configuration Report Command
C264 C264
Configuration Configuration
/ View / Parameters
C264 C264
Configuration Configuration
/ Parameters / Parameters
/ HMI / Treatment
C264 C264 C264 C264 C264

Configuration Configuration Configuration Report Command
/ View / Parameters / Parameters / Bay 01 / Bay 01
/ Bay 01 / HMI / Treatment
/ Bay 01 / C/S 01
Select
datapoint Cancel
+ password Select Choice
C264 C264 C264 C264

Configuration Configuration Configuration Command
/ View / Parameters / Parameters / xxxx
/ xxxx / HMI / Treatment SELECTED
SELECTED / xxxx / xxxx
Validate
SELECTED SELECTED
C0077ENa
FIGURE 1: MENU TREE FOLDER ORGANISATION

2. CONFIGURATION OF VIEW PANELS

2.1 Bay display
• BAY01=>08
Label Select action Comment

Visible master Configured
Not configured
Loc/rem command type Software loc/rem cmd
Wired loc/rem cmd
2.2 Synchrocheck
• SCK01=>08

Synchrocheck name Not assigned
Synchrocheck1*
Synchrocheck2*
Synchrocheck3*
Synchrocheck4*
Synchrocheck5*
Synchrocheck6*
Synchrocheck7*
Synchrocheck8*
Associated device Not assigned
Q1*
Q2*
Q3*
…*
Q72*
Not configured
2.3 Communication display
• COM01=>10

Not configured
2.4 Devices display
• DEV01=>72

Device name Not assigned
Q1*
Q2*
Q3*
…*
Q72*
Device type Not assigned
Circuit breaker
Switch disconnector
Information type Not assigned
Signal
Command
Signal with command
Not configured
2.5 Counters
• RCT01=>10

Bay Not assigned
Bay1*
Bay2*
Bay3*
Bay4*
Bay5*
Bay6*
Bay7*
Bay8*
Not configured
2.6 Measurements
• RM001=>256

Bay Not assigned
Bay1*
Bay2*
Bay3*
Bay4*
Bay5*
Bay6*
Bay7*
Bay8*
Not configured
2.7 Transformer Tap Position
• TAP01=>08

Tap changer name Not assigned
TAP1*
TAP2*
TAP3*
TAP4*
TAP5*
TAP6*
TAP7*
TAP8*
Min. position <numeric value> min value
Max. position <numeric value> max value
Not configured
3. PARAMETERS/HMI PANELS
The differents setting panels define.
3.1 Bay Panel
• BAY01=>08

Bar display type No bar display
Vertical bar
Horizontal bar
Fct.asg. num. displ. <list of measurments and
counters>
Fct.asg. bar displ. <list of measurments and
counters>
Fct.asg. scal. bar <list of measurments and
counters>
3.2 Main LCD settings
• MAIN

Auto. MT return time <numeric value> Min value = 5
Max value = 300
Increment = 1
Default value = 60
Unit : seconds
Language English
English
Decimal delimiter Dot
Comma
Fct.asg. meas. panel <list of measurments and
counters>
Illumin. return time <numeric value> Min value = 5
Max value = 300
Increment = 1
Default value = 60
Unit : seconds
Select. return time <numeric value> Min value = 5
Max value = 300
Increment = 1
Default value = 60
Unit : seconds
Password loc/rem ********
Password MT ********

Hold-time meas. pan. Min value = 1
Without function No
Yes
Scale 0-1.2 No
Yes
Scale 0-2 No
Yes
Assignment read key <1 specific configured datapoint of
the menu tree>
3.3 Display options bay panel
• SUBST

Displ. modules names No
Yes
Inlock off timeout <numeric value> Min value = 20
Max value = 120
Increment = 1
Default value = 90
Unit : seconds
Synchk off timeout <numeric value> Min value = 20
Max value = 120
Increment = 1
Default value = 90
Unit : seconds
Character set Character set 1
Character set 2
Character set 3
Display bar scale No
Yes
Displ. loc/rem state No
Yes
Displ. inlock state No
Yes
Display SBMC state No
Yes

Displ. synchk state No
Displ. autrec state No

Yes
4. PARAMETERS/TREATMENT PANELS
4.1 Synchrocheck
• SCK01=>08

Scheme Not assigned
V AND Vref
V AND NOT Vref
NOT V AND Vref
NOT V AND NOT Vref
NOT V OR NOT Vref
Delta <numeric value> Min value = 200
Max value = 10000
Increment = 1
Unit : mseconds
Thres. pres. volt. <numeric value> Min value = 0.5
Max value = 1.1
Increment = 0.01
Unit : .Un V
Thres. abs. volt. <numeric value> Min value = 0.1
Max value = 0.6
Increment = 0.01
Unit : .Un V
Thres. voltage diff. <numeric value> Min value = 0.01
Max value = 3
Increment = 0.01
Unit : .Un V
Thres. freq. diff. <numeric value> Min value = 0.01
Max value = 1
Increment = 0.01
Unit : Hz
Thres. phases diff. <numeric value> Min value = 5
Max value = 70
Increment = 1
Unit : Degrees
Time delay <numeric value> Min value = 0
Max value = 5000
Increment = 1
Unit : mseconds
4.2 Serial Communication
• COM01=>10

Baudrate Not assigned
50 Baud
100 Baud
200 Baud
300 Baud
600 Baud
1200 Baud
2400 Baud
4800 Baud
9600 Baud
19200 Baud
38400 Baud
56000 Baud
64000 Baud
Parity No parity
Even parity
Odd parity
Stop bit number 1 bit
1.5 bits
2 bits
Bits per char number <numeric value> Min value = 7
Max value = 8
Increment = 1
Unit : bits
Transmission mode Synchronous
Asynchronous
4.3 Devices control timers
• DEV01=>72

Opening duration <numeric value> Min value = 0
Max value = 1000
Increment = 1
Unit : mseconds
Closing duration <numeric value> Min value = 0
Max value = 1000
Increment = 1
Unit : mseconds
4.4 Measurements acquisition
• RM001=>256

Hyst <numeric value> Min value = 1
Max value = 50
Increment = 1
Unit : configured with the
SCE
Deadband <numeric value> Min value = 0
Max value = 50
Increment = 1
SCE
Low low low thr. val <numeric value> Min value = 0
Max value = 1
Increment = 0.01
SCE
Low low thres.val. <numeric value> Min value = 0
Max value = 1
Increment = 0.01
SCE
Low thres.val. <numeric value> Min value = 0
Max value = 1
Increment = 0.01
SCE
High thres.val. <numeric value> Min value = 0
Max value = 1
Increment = 0.01
SCE

High high thres.val. <numeric value> Min value = 0
Max value = 1
Increment = 0.01
SCE
Hi hi hi thres val. <numeric value> Min value = 0
Max value = 1
Increment = 0.01
SCE
4.5 Tap Changer Control Delays
• TAP01=>08

Closing duration <numeric value> Min value = 0
Max value = 1000
Increment = 1
Unit : mseconds
Opening duration <numeric value> Min value = 0
Max value = 1000
Increment = 1
Unit : mseconds
MiCOM C264/C264C
LOGIC DIAGRAMS
CONTENT
2. PLANT DATA INTERFACE 3

2.1 Digital Input Treatment 3
2.1.1 DI Treatment main parts 3
2.1.2 Digital Input Filtering Principle 3
2.1.3 DI Debouncing & Filtering 4
2.1.4 Toggling of Binary Input 4
2.2 Analogue Input Treatment 5
2.2.1 Principle 5
2.3 Binary Input Processing 5
2.3.1 Principle 5
2.3.2 Double Point Processing 6
2.3.3 Multiple Points Processing 6
2.3.4 HV Three phases breaker 6
2.4 Digital output treatment 6
2.5 Measurement Input Processing 7
2.6 Counters Input Processing 7
3. GENERIC CONTROL SEQUENCES 8

3.1 Generic control checks 9
3.2 Generic modes control 11
3.3 Selection control sequence 12
3.4 Execution control sequence 13
3.5 Execution control sequence for SBO many mode 14
3.6 Unselection phase for SBO many mode 15
4. DEVICE CONTROL SEQUENCES 16

4.1 Circuit breaker 16
4.2 IED 17
4.3 Disconnectors device 17
4.4 Transformers 17
5. SLOW CONFIGURATION AUTOMATION (PLC) 18
6. FAST CONFIGURABLE AUTOMATION (PSL) 18

C264/EN LG/A13 Logic Diagrams
7. BUILT-IN AUTOMATIC FUNCTIONS 19

7.1 Automatic Voltage regulation (AVR) 19
7.2 Synchrocheck 19
7.3 Autorecloser (AR) 20
7.4 Trip Circuit Supervision (TCS) 23

This document is a chapter of MiCOM C264/C264C documentation binders. It describe the
Logical functions and automations (coded LG for Logic Diagrams) of this computer.
Because of a strong interaction between programming functions into the MiCOM
C264/C264C computer and the tools that enable this. Giving access to these specific
functions is done using the PACiS SCE. For further details concerning the configuration of
certain functions you should see the application chapter.
2. PLANT DATA INTERFACE

2.1 Digital Input Treatment
2.1.1 DI Treatment main parts
CPU C264
Systeme UCA2
SPS SI
DI board Debouncing BI DPS SIT

DIU Filtering
& Processing
CCU MPS SIG
Time Stamping
SCT ACL
DCT
C0078ENa
FIGURE 1: DIGITAL INPUT PROCESSING CHAIN
Parameters:
Board kind, Board Number, Voltage, Channel number
2.1.2 Digital Input Filtering Principle
Debouncing & Binary Input SPS

Filtering & Processing DPS
Toggling for BI
Hardware Software Time stamping Debouncing & Measurement

acquisition acquisition Filtering for DM Input Processing DM
Debouncing & Counters Input SCT

Filtering for Processing DCT
Counters
C0079ENa
FIGURE 2: PROCESSING CHAIN OF DI
Parameters:
Datapoint kind BI: SPS, DPS or DM SIG or Counter SCT DCT
2.1.3 DI Debouncing & Filtering
0.7 Nom
Filtering time
Debouncing
time
t0 t1 t2
C0080ENa
FIGURE 3: DEBOUNCING AND FILTERING

Without any filtering DI is SET when input getting over 0.7 Nominal.
The debouncing is a special filtering of mechanical phenomenon (similar to electronic
overshoot). A short time delay is given to keep a stabilised state of the input and transmit the
new state. Time tag is given by t0 with the delay given in configuration. If new state is not
stable, the new state is not taken in account. Each time input cross again the new state level
timer is restarted.
Filtering is here an optional filtering added to debouncing. It starts after debouncing delay. It
transmits a new valid state after t2 if signal remains stable. Time tag is t0.
Parameters:
• Debouncing delay
• Filtering delay (if debouncing delay > 0)

2.1.4 Toggling of Binary Input
BI is said toggling when its input changes more then N times in a given period T. After
switching in toggling state, if during the toggling sample the state remains stable the BI
leaves toggling state to the current state.
Parameters:
• Shot numbers
• Toggling Period
2.2 Analogue Input Treatment

2.2.1 Principle
CPU C264
Systeme UCA2
AI AI
BI DELTA
AI board Acquisition cycle
Measureme nt
AIU &
Input Proce ssing WYE
CT/VT Time Stamping
C0081ENa
FIGURE 4: MEASUREMENT INPUT PROCESSING CHAIN
• AIU boards
Two acquisition cycles based on base time 100ms for short cycle or 500 ms for long cycle
Parameters:
Short cycle or Long cycle
Period (N* base time)
• CT/VT board
Standard acquisition at 48 of fundamental frequency. This frequency is used at start-up then
tracked by algorithm to the real frequency.
Parameters:
Fundamental frequency 50-60HZ
Primary voltage A, B, C (for frequency tracking)
2.3 Binary Input Processing
2.3.1 Principle
RCP
Group processing, LCD...
and other inner Computer treatment via C264 RTU
including Fast PSL protocol
From Board Computer data
Persistance
acquisition Forcing logging
Motion (DPS)
Suppression PACIS Gateway
From IED UCA2 PACIS OI
Filtering Report
Acquisition Substitution System Data Logging
System Archive
System
UCA2 To Fast automation on
Inputs
GOOSE other MiCOM Computers
C0082ENa
FIGURE 5: PROCESSING OF A SP
2.3.2 Double Point Processing
Close contact Toggle

from filtering
acquisition Group
processing
Manual
suppression Motion
Open contact Toggle filtering
from filtering
acquisition Substitution To RCP
Persistance Transmission To HMI (views, lists)
filtering Report based To Data Logging
To archive
IED Forcing
From IED inputs
Transmission
System
GOOSE based To automation
Inputs
C0083ENa
FIGURE 6: PROCESSING OF A DP
2.3.3 Multiple Points Processing
Toggle
Contact 1
filtering
From acquisition
Manual
suppression
Toggle To RCP
Contact N To HMI (views, lists)
From acquisition filtering
Substitution MP filtering Transmission To Data Logging
Report based To archive
To automation
Forcing
System
Inputs
C0084ENa
FIGURE 7: MP PROCESSING
2.3.4 HV Three phases breaker
Is managing by software DSP that is computed by association of the 3 or 4 phase DSP.
2.4 Digital output treatment
SPC, DPC
DO can be simple or double and be latched or pulsed
Digital measurement output: MPC
A special signal is provided that is the Read Inhibit signal
2.5 Measurement Input Processing
From IED
acquisition
Manual suppression
Open Circuit Scaling Thresholds
From analogue Manage ment Substitution
acquisition detection
Forcing
From digital
acquisition Transmission
From CT /VT acquisition CT/VT To RCP T o HMI (views, lists)

Calculations To Data Logging
To archive
To automation
C0085ENa
FIGURE 8: MEASUREMENT PROCESSING
2.6 Counters Input Processing
Continuous register Scaling
+
To RCP
+1
From counters Accumulator To HMI (views, lists)
acquisition Transmission
To archive
To automation
=
Periodic register Scaling
in
24h - FIFO
C0086ENa
FIGURE 9: COUNTER PROCESSING

3. GENERIC CONTROL SEQUENCES

The goal of a control sequence is to modify the state of a Module. Module is a global name
given to function, an external auxiliary, and an HV device. Basically a feedback via Digital
Input tells if the module control has succeed. The basic scheme of a control sequence is
then decomposed in two main parts as defined in the following scheme:
When receiving order the global control sequence starts. The order might come from:
• Higher level inner automation (built in),
• Operator from Local Control Display, or
• Other device through Station BUS (PACiS OI, other Computer) or Telecontrol BUS
(RCP).
Several kind of order can enter into control sequence with several level of bypass. The
bypass is the ability to short cut (with given rights) some control checks.
Control sequence is done into computer by two main parts:
• Control preliminary checks that accept order
• Module control that servo the execution

3.1 Generic control checks

Those tests are fully configurable from PACiS SCE. They are checks before any execution of
module control.
Beginning of execution
phase
1
no
Inter-control delay
expired Not configured
2
yes
Computer faulty or in
maint
no 3
Substation and bay
no mode OK
Bypass mode checks yes Not configured
no 4
Interlock checks
no OK
Bypass interlock yes Not configured
checks
5
yes
Automatism running
no Not configured
Bypass automatism
6
no
Device selectable
(SBO only)
7
yes
Device locked
no no
Not configured
Bypass locked device
8
no
Current status of the
device OK
Not configured
yes
9
no Uniqueness
OK
no
Not configured
Bypass uniqueness yes
check
Abort
selection Continue execution
phase phase
C0087ENa
FIGURE 10: GENERIC CHECKS

1. Inter control delay: A user-selectable delay can be defined in which a new order in the
same device is forbidden. If this delay is configured and not expired since the last
order the request is refused with negative acknowledgement.
2. Computer mode: In maintenance mode, control’s requests are not accepted except for
some system controls.
3. In faulty mode, none control is accepted in this mode
4. Substation bay control 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)

1. Interlock control: Process allows to assign or not a logical equation to each order.
2. Automatism running control: Is used to prevent manually control execution in case an
automatism is active for device monitoring (e.g. ATCC).
3. Device selectable: This control is done for SBO once and SBO many control modes
only.
4. Device locked: If this control concern a locked device the request is refused.
5. Current status of the device: If the device is already in the requested position or in
invalid position the request is refused with negative acknowledgement.
6. Uniqueness: This control is done to prevent to have more than one control at time into
the whole substation or into the bay.
3.2 Generic modes control

Management of controls can be made in one, two or three phases: Selection, Execution and
Unselection.
By configuration, at SCE level a control may be executed in one of the following mode:
• Direct execute: Execution
• SBO once: Selection, Execution (Unselection is automatically done by the computer)
• SBO many: Selection, Several Execution, Unselection
Direct Execute SBO once SBO many
Selection
Execution request
Execution
Direct execute Deselection re quest SBO many
Deselection
End of control
sequence
C0088ENa
FIGURE 11: GENERIC MODE CONTROL

3.3 Selection control sequence
Beginning of control
sequence
Selection request
no
Device selectable ?
yes
Device Already
selected
Perform Selection
checks
no
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
C0089ENa
FIGURE 12: SELECTION CONTROL SEQUENCE

3.4 Execution control sequence
Execution phase
yes
Execution in progress
execution in progress
to the device
Perform execution
checks
send negative
acknowledge
no
All checks OK
Operator
Cancel request
Perform execution
no Execution OK
send negative send positive

acknowledge acknowledge
Reset execution in
progress
Deselect device
for SBO once
End of control
sequence
C0090ENa
FIGURE 13: EXECUTION CONTROL SEQUENCE

3.5 Execution control sequence for SBO many mode
Execution phase
SBO many
Wait request
Unselect request Cancel request Execution request
no
Device selected
Execution
control
sequence
End of control
sequence
Unselection
phase
C0091ENa
FIGURE 14: EXECUTION CONTROL SEQUENCE FOR SBO MANY MODE

3.6 Unselection phase for SBO many mode
Unselection phase
hardware selection
Error during
Not configured
deselection
Deselect the device
Send negative Send positive

acknowledge acknowledge
Set « device
deselected »
End of control
sequence
C0092ENa
FIGURE 15: UNSELECTION PHASE FOR SBO MANY MODE

4. DEVICE CONTROL SEQUENCES

4.1 Circuit breaker
In case of controlling a circuit breaker different types are to be considered:
• Non synchronised circuit breaker
• Synchronised circuit breaker:
− Circuit breaker with external synchrocheck
− Circuit breaker with internal synchrocheck

The control sequences of these devices can be resumed as follow:
C264
XCBR ODCommand CB (DCO) Open
SBO mode CB
Close
Close synchro CB
Open
RSYNC Enalbe Synchro (DCO)
SYNC
DE mode Close
C0093ENa
FIGURE 16: CIRCUIT BREAKER CONTROL SEQUENCE, SYNCHRO IN MANUAL MODE
In the case where the Synchro is enable the command is a; Close Synchro, in the case
where the Synchro is disable the command is an Open/Close classical.
C264
XCBR ODCommand CB (DCO) Open
SBO mode CB
Close
ODEnable Synchro (BO) Execution

Close synchro CB
SBO mode
Select
Open
SYNC
Close
C0094ENa
FIGURE 17: CIRCUIT BREAKER CONTROL SEQUENCE, SYNCHRO IN AUTOMATOC MODE

In the Synchro is in Automatic mode during the selection phase a SBO window is pop up on
the OI HI to let the user choice between Open, Close classical or Close with Synchro.
4.2 IED
This control sequences will be described in future release of this document.
4.3 Disconnectors device
• Busbar disconnectors
• Disconnectors
• Bypass disconnectors
• Transfer busbar disconnectors
• Earthling switch
4.4 Transformers
• with TCIP
• without TCIP
5. SLOW CONFIGURATION AUTOMATION (PLC)

Using the SCE for defining this kind of automaton you first need to load the DB into the SCE.
When your are in mode Object (not Template) select the Voltage Level in the tree view, in
the Object Entry window click on the user function. A Slow automation item is added on the
Voltage level for you to define your automaton. Then, by right clicking on the slow automaton
item, you can choose to edit your automaton with ISaGRAF.
6. FAST CONFIGURABLE AUTOMATION (PSL)

By using the SCE you will be able to directly edit PSL equation. When your are in mode
Object. Add a Fast automaton item into the tree view. You can define inputs, outputs and
logical functions for this automaton. By right clicking on Fast automation item in the tree view
you will be able to visualise your automaton similar to the one in the scheme bellow:
I1
& DO1
setting
I2
& DO2
setting
1 t
&
BI1
≥1
setting
1
I3
1
I4
C0095ENa
FIGURE 18: EXAMPLE OF PSL

7. BUILT-IN AUTOMATIC FUNCTIONS

7.1 Automatic Voltage regulation (AVR)
The Automatic Voltage Regulation (AVR) function is used to automatically maintain the
correct voltage at the lower voltage of transformers. Controlling the tap changer of
transformers changes secondary voltage.
AVR is able to manage one transformer or several transformers in parallel. Transformers are
in parallel if their secondary poles are interconnected.
AVR also provides:
• 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 to which it will be
connected
• Minimisation of circulating current

7.2 Synchrocheck
Absence system 1 voltage 0

&
2 Reclosing authorization
Presence system 2 voltage
C0096ENa
FIGURE 19: V AND NOT VREF AND NOT V AND VREF SCHEMES
Absence system 1 voltage θ3 0 Reclosing authorization

&
Absence system 2 voltage
C0097ENa
FIGURE 20: NOT V AND NOT VREF SCHEME
F min < Fref < Fmax

F min < F < Fmax
Presence of V
Presence of Vref &
1 0 Reclosing authorization
F <Efreq
< Ephase
V < Evect
C0098ENa
FIGURE 21: V AND VREF SCHEME

F min < Fref < Fmax

F min < F < Fmax
Presence of V
1 0 Reclosing authorization in
&
Presence of Vref order to give authorization
F <Efreq
V < Evect
C0099ENa
FIGURE 22: V AND VREF SCHEME

7.3 Autorecloser (AR)
BI associated with CB
DO for recloser & AR_Enable
Function enabled
C0100ENa
FIGURE 23: RECLOSER ENABLED
CB closed Determinate which opening First monophased cycle
TRIP signal (DEC)

1 has to be waited for.
Increment of the cycle
counter. First triphased cycle
Set of the active cycle.
Test of the cycle
( ≤ 4)
Second triphased cycle
Third triphased cycle

Recloser locked
Recloser in service
& RESET
Fourth triphased cycle
progressservice
Max try exceeded
C0101ENa
FIGURE 24: ANALYSIS OF THE RECEIVED TRIP

Recloser lockout
Recloser in service
& S
Analysis Over
Q 0 AR_Wait_for_open_cb
T1
All waited CB Opening has R
happened
AR_trip_3Ph
C0102ENa
FIGURE 25: RECLOSER WAITING FOR CB OPENIG
All waited CB Opening

has happened
First monophased
cycle
AR_Enable
&
DEC_1P
AR_Cycle_3P
& S
CBA_Disc AR_First_cycle_1P
(Option)
Q
R
Lock
t
1
DEC_3P 0
1P_DTIME
AR_Enable
C0103ENa
FIGURE 26: SINGLE PHASE CYCLE
AR_Enable
First triphased
fast cycle &
DEC_3P
S
All waited CB Opening Q AR_First_cycle_3P
has happened
R
Lock 1
t
0
AR_Enable
DTIME1
C0104ENa
FIGURE 27: THREE PHASE FAST CYCLE

AR_Enable
DEC_3P
&
S
XXX triphased
cycle
Q AR_XXX_cycle_3P
R
All waited CB Opening
has happened
t
1 0
Lock
DTIME
AR_Enable
C0105ENa
FIGURE 28: THREE PHASE SLOW CYCLE
Synchrocheck’s
use configured
End of the fast

&
cycle timer
End of the slow 1 AR_Close

cycle timer &
Synchrocheck’s
authorisation
End of the 1P
cycle timer 1
All concerned &

CB Opened
S
Q AR_Wait_for_closed_cb
AR_Enable &
Lock R
1 1
CB_HEALTHY
DEC_3P
1
DEC_1P
All concerned 1
CB Closed
NOK
acknowledgement
of closing order
C0106ENa
FIGURE 29: CB CLOSING

CB Close S
Q AR_Reclaimc
DEC_3P R
1
DEC_1P
0
t
RC Time
C0107ENa
FIGURE 30: RECOVERING TIMER AND SUCCESSFUL RECLOSING
R
CB manual close
Q AR_Fail
Hardware failure S
1
Interlocking
Autorisation NOK
Synchrocheck
Authorisation &
NOK
End of the slow

cycle timer
1
Synchrocheck's
use configured
&
End the fast cycle
timer
C0108ENa
FIGURE 31: DIAGRAM OF THE RECLOSING FAILURE

7.4 Trip Circuit Supervision (TCS)
The trip Coil Supervision function allows raising an alarm into the PACiS OI if a circuit
breaker is still closed after a relay trip order.
BLANK PAGE
MiCOM C264/C264C
COMMUNICATIONS
CONTENT
2. SCP COMMUNICATION 3
2.1 Communication on Station bus 3
2.1.1 Finality 3
2.1.2 Inputs 3
2.1.3 Outputs 4
2.1.4 Supported services 4
2.1.5 Supported data objects 5
3. SCADA COMMUNICATION 7
3.1 Overview 7
3.2 SCADA common functionality 7
3.2.1 Interface 7
3.2.2 Behaviour and specific treatments 10
3.2.3 Data sent to SCADA 12
3.2.4 Data sent to MiCOM C264 14
3.2.5 Configuration 14
3.3 DNP 3.0 Communication 15
3.3.1 Finality 15
3.3.2 Interface 15
3.4 IEC 60870-5-101 communication 17
3.4.1 Finality 17
3.4.2 Interface 17
3.4.3 Behaviour 17
3.4.4 Data sent to SCADA 18
3.5 IEC 60870-5-104 communication 20
3.6 MODBUS communication 20
C264/EN CT/A13 Communications
4. IED COMMUNICATION 21
4.1 Overview 21
4.2 IED Common functionality 22
4.2.1 Interface 22
4.2.2 Behaviour 24
4.2.3 Data received from IEDs 28
4.2.4 Data sent to IEDs 29
4.2.5 Limits and Performances 29
4.3 MODBUS communication 31
4.3.1 Finality 31
4.3.2 Reference documents 31
4.3.3 Interface 31
4.3.4 Behaviour 32
4.3.7 Error management 34
4.4 DNP 3.0 Communication 36
4.4.1 Finality 36
4.4.2 Interface 36
4.4.3 Behaviour 37
4.5 IEC 60870-5-103 Communication 39
4.5.1 Finality 39
4.5.2 Interface 39
4.5.3 Behaviour 40

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 UCA2 or IEC 61850
• SCADA Communication: communication with an upper level SCADA system over

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

considered as a master (IEC 60870-5-103, DNP3.0, MODBUS)
2. SCP COMMUNICATION
2.1 Communication on Station bus
2.1.1 Finality
This function performs the interface between the MiCOM C264 software and the UCA
agency.
2.1.2 Inputs
2.1.2.1 Information: MiCOM C264 application ! SCP
The information’s that can be transmitted are:
• Changes of state of binary inputs
• Measurements (Analogue or CT/VT)
• General requests responses
• Control acknowledgements
• Records (Event, fault, disturbance or power quality)
• MiCOM C264 information (Init. report, Operating mode, control mode, Date)
• Database uploading
2.1.2.2 Information SCP ! MiCOM C264 application
The information’s that can be transmitted are:
• Controls on device
• Specific control (DO, change of operating mode, change of control mode, for the date
of the MiCOM C264)
• Request for records
• General requests
• Acknowledgements of control sequence
• Time synchronisation message
• Database downloading
2.1.3 Outputs
2.1.3.1 MiCOM C264 ! SCP
Depending on the information that is to be transmitted, specific logical nodes and logs will be
updated and then sent to the SCP via the transmission links.
2.1.3.2 SCP ! MiCOM C264
Depending on the information that is to be transmitted a specific operation has to be
performed. Each treatment has to be fully compliant with the SII, System Internal Interface
document [39].
The information received from the UCA agency (i.e. from the SCP) will be translated into the
MiCOM C264 internal message format. These internal messages will be detailed in the
conception document.
2.1.4 Supported services
The following table describes the services supported by the UCA2 agency integrated in the
MiCOM C264:
Client Server
UCA Service MMS PDU
support support
Data Object Model Named Variable
GetDataObjectValues Read YES YES
SetDataObjectValues Write YES YES
SetDataObjectValues (Unconfirmed) InformationReport YES YES
GetDataObjectAttributes GetVariableAccessAttributes YES YES
DataSet Model Named Variable List
GetDataSetElementNames GetNamedVariableListAttributes YES YES
GetDataSetValues Read YES YES
Server Model VMD
GetLogicalDeviceList GetNameList class domain YES YES
GetCapabilities GetCapabilityList YES YES
Association Model Association
Initiate Initiate YES YES
Conclude Conclude YES YES
Abort Abort YES YES
LogicalDevice Model Domain
GetDataObjectsList GetNameList YES YES
GetDataSetsList GetNameList YES YES
Device Control Model
Select Read YES YES
DeSelect Write YES YES
Operate Write YES YES
Client Server
UCA Service MMS PDU
support support
Reporting Model
Report InformationReport YES YES
File Transfer Model
FileOpen FileOpen YES YES
FileClose FileClose YES YES
FileRead FileRead YES YES
FileDir FileDir YES YES
FileDelete FileDelete YES YES
Time Synchronisation Model Station Management Protocol (not
MMS)
Prepare for Time Sync Request Prepare for Time Sync Request YES YES
Measurement request Measurement request YES YES
Time sync request Time sync request YES YES
GOOSE Model
Send GOOSE InformationReport YES YES
2.1.5 Supported data objects

The following table describes the common class supported by the UCA2 agency integrated
in the MiCOM C264:
Client Server
Common Class Comment
support support
Status
SI Single input status YES YES
SIT Double input status YES YES
SIG Status input group YES YES
ISI Integer input status YES YES
Measurements
AI Analogue input YES YES
WYE 3 phase + N measurement YES YES
DELTA Phase to phase measurement YES YES
Counters
ACCI Accumulator input YES YES
Control
BO Binary output YES YES
DCO Double control output YES YES
AO Analogue output YES YES
Client Server
Common Class Comment
support support
Configuration
CCF Control configuration YES YES
SBOCF SBO configuration YES YES
Settings
AISP Analogue input setting YES YES
WYESP WYE setting YES YES
Report Control Block
BasRCB Basic report control block YES YES
GOOSE
PACT Protection action YES YES
3. SCADA COMMUNICATION
3.1 Overview
A MiCOM C264 can be connected to a SCADA through networks using various legacy
protocols.
The legacy protocols which it is planned to develop are the following:
1. DNP3
2. T101
3. T104
4. Modbus
All these networks use either a serial link or a TCP/IP link to communicate with SCADA. 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 Slave. So,
there are two kinds of exchange:
• Request / reply
Slave MiCOM C264 receives a request emitted by a SCADA and responds to it.
• Broadcast
Slave MiCOM C264 can receive a message addressed to it. MiCOM C264 performs it
without sending a response.
Common features to all SCADA communication and all protocols are specified below.
Features specific to each protocol are specified in subsequent paragraphs.
3.2 SCADA common functionality
3.2.1 Interface
3.2.1.1 Interface to internal functions of MiCOM C264
This paragraph describes the exchange of data between the “SCADA communication”
function and the other functions of the MiCOM C264. It is split into two sub-paragraphs:
• Inputs: data received from other functions to the “SCADA communication” function.
• Outputs: data sent from the “SCADA communication” function to other functions.
For each kind of protocol, it is indicated if the data is treated or not:
• Treated: indicates the data is treated
− Not Treated: indicates the data is NOT treated
− Partially: indicates the data is partially treated

3.2.1.1.1 Input
Sender Data DNP3 T101 T104 Modbus
Binary input Digital input state Treated Treated Treated Treated

processing Dated Digital input change Treated Treated Treated Not Treated
Measurement Events Measurement Treated Treated Treated Not Treated

treatment Cyclical Measurement Treated Treated Treated Treated
Tap position Treated Treated Treated Treated
Non tariff metering Counter Treated Treated Treated Partially
Archiving Events records Treated Treated ? Not Treated
Handling of control Control acknowledgement Treated Treated Treated Not Treated

sequences Setpoint acknowledgement Treated Treated Treated Not Treated
Download database
Supervision Treated Treated ? Not Treated
acknowledgement
MiCOM C264 Disturbance Treated Treated Treated Not Treated
IED
IED Disturbance Treated Treated Treated Not Treated
communication
3.2.1.1.2 Output
Receiver Data DNP3 T101 T104 Modbus

Single Control Treated Treated Treated Treated
Dual Control Treated Treated Treated Not Treated
Handling of SBO Treated Treated Treated ?
control sequences
Not Not
1 among N Not Treated Not Treated
Treated Treated
Setpoint Treated Treated Treated Treated
Connection state Treated Treated Treated Treated
Server UCA2 Not Not
Redundancy state Not Treated Not Treated
Treated Treated
Supervision Download database Treated Treated ? Not Treated
clock
Synchronisation Treated Treated Treated Treated
synchronisation
3.2.1.2 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:
• Treated: indicates the data is treated
• Not Treated: indicates the data is NOT treated
• Partially: indicates the data is partially treated
• X: indicates that the function doesn’t exist for the protocol

3.2.1.2.1 Input
Data DNP3 T101 T104 Modbus

Remote link initialisation Treated Treated Treated X
General interrogation Treated Treated Treated Treated
Control Treated Treated Treated Treated
Setpoint Treated Treated Treated Treated
Time synchronisation Treated Treated Treated Treated
Database (download) Treated Treated ? Not Treated
3.2.1.2.2 Output
Data DNP3 T101 T104 Modbus

Digital input Treated Treated Treated Treated
Dated Digital input Treated Treated Treated Not Treated
Measurement (Events) Treated Treated Treated Not Treated
Measurement (Cyclical) Treated Treated Treated Treated
Counter Treated Treated Treated Treated
Tap position Treated Treated Treated Treated
Control acknowledgement Treated Treated Treated Not Treated
Setpoint acknowledgement Treated Treated Treated Not Treated
MiCOM C264 Disturbance Treated Treated ? Not Treated
Sequence Of Event File Treated 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
3.2.2.1.1 Initialisation of the running database
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.1.2 Initialisation of the line
Before being able to communicate on the network, the link must be initialised.
For serial links, parameters of initialisation include the following (non exhaustive list):
• Port number to be used
• baud rate
• parity
• number of start and stop bits
• carrier management
For TCP/IP links, parameters of initialisation include the following (non exhaustive list):
• TBC
• …
3.2.2.1.3 Remote initialisation of the MiCOM C264
After receiving a remote reset link command, the MiCOM C264 performs a cold restart of the
link management. Any messages pending transmission are discarded.
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 its process variables.
The MiCOM C264 marks the end of the general interrogation procedure by sending an
indication to the controlling station when the protocols allow it.
The outstation interrogation procedure can be interrupted by events, which may occur in the
MiCOM C264. Care is taken to avoid any confusion, which may be caused by receiving
interrogated information, which has been made redundant by an event.
3.2.2.3 Clock synchronisation

Clock in MiCOM C264 may be synchronised by the controlling station. The clock is initially
synchronised by the controlling station after initialisation and then re-synchronised
periodically.
NOTE: the clock can be synchronised by other means: external clock, SCP,
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 can calculate the propagation delay. The controlling station must
perform the correction made on the time sent in synchronisation commands.
3.2.2.4 Database downloading and switching
The MiCOM C264 has two databases, the current one and the reserve one. The controlling
station can download a reserve database to the controlled function - if the protocol allows it -
and perform a switch to make the reserve database current.
The downloading is initiated by the controlling station, which sends a request. The MiCOM
C264 sends a positive or a negative response. If the response if positive the controlling
station can send the database by using the file transfer mechanism. The controlling station
must mark the end of transmission. The MiCOM C264 must check the integrity of the
received database and send a positive or a negative indication to the controlling station. The
controlling station can then send a switch request [digital command] to the MiCOM C264,
which sends a response and reinitialises its application. The response can be negative if the
MiCOM C264 can not perform the switch.
3.2.2.5 Local/remote mode
A substation, a bay or a device 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.
Depending upon the protocol used, there must exist a binary input per substation, bay or
device in the configuration to indicate this mode, or specific messages are sent to indicate
the mode.
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 has previously the
control
− Set the “Taking Control Binary input” of the SCADA which asks the control
If the take control command is set, MiCOM C264 should refuse all commands from other
SCADA’s, except the one that has taken control.
3.2.2.7 SBMC mode
This mode is used to test a bay 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 request slave 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 command a synchrocheck.
First, it sends a command to the circuit breaker. After synchrocheck activation, SCADA
receives a DI indicating that it can force the command on the circuit breaker.
Second, SCADA will send another command to force the circuit breaker. Communication
task should then recognise this specific command, and send a message – to the MiCOM
C264 application -tagged with bypass 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 Digital inputs
Digital inputs can be sent as states or as changes of state. The choice between state and
change of state depends on the protocol. If the protocol allows both, the choice is done by
configuration.
A digital input can be associated with a single point or a double point.
NOTE: Multipoint status (SIG) 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 (TPI or SPI) inputs can be sent as states or as changes of state. The choice
between state and change of state depends on the protocol. If the protocol allows 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 IED disturbance Files
The disturbance Files of the IEDs are stored in the MiCOM C264 in an owner format
(depending on the protocol and kind of IED). Programs functioning under Windows [NT4 or
2000] make it possible to convert these files to COMTRAD format (after uploading of the files
- in the owner format - on a PC through SCADA link).
As IED disturbance Files are in an owner format, the up loading of these files is done with
generic file transfer (not specific disturbance File transfer).
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 single or double Binary Input. The choice of BI
to store in SOE is done by configuration.
Following information in MiCOM C264 configuration are used to manage SOE file:
• for each SCADA link
− 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
− A flag indicating if the BI 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 should inform the controlling station about its synchronisation status.
According to the protocol, this may be done by a specific message of the protocol or by a DI.
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
A control is transmitted to the handling of control sequences function.
Some SCADA do not manage selection of control. In order to avoid non-compatibility
between some SCADA and system definition, “SCADA transmission” task will tag each
execute order with Bypass Select.
At the end of the control sequence an acknowledgement is sent to SCADA if protocol allows
it.
If the command is a “select before operate” command, the application must send two
acknowledgements to the transmission software: the first one for the selection and the
second for the execution.
3.2.4.2 Counter commands
The commands allowed on counters are:
• Reset of a group of Counters
• Reset of all Counters
• Read of a group of Counters
• Read of all Counter

3.2.4.3 Synchronisation
Depending on the configuration, MiCOM C264 can be synchronised by a SCADA.
3.2.5 Configuration
• Number of networks
• For each network:
− Port identification
− Transmission characteristics ( baud, parity, …)
− Protocol
− Address of Slave MiCOM C264
− Management of Taking Control option (Y/N)
− Number and table of DI
− Number and table of Measurements
− Number and table of controls
− Number and table of setpoint

3.3 DNP 3.0 Communication

3.3.1 Finality
The purpose of this chapter is not to describe the DNP3 standard but to specify the use of
the DNP3 protocol on a SCADA link of the MiCOM C264.
As the MiCOM C264 is the slave on the network - regards to SCADA - this protocol is
referenced as “Slave 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

3.3.2 Interface
Interface with SCADA is developed with DNP3 Level 3 Implementation.
3.3.2.2.1 Input
Object Variation Data Function Note

01 0 Static BI [22] ASSIGN CLASS Treated
12 1 Command: Control [3] SELECT Treated
Relay Output Block
[4] OPERATE Treated
[5] DIRECT OPERATE Treated
[6] DIRECT OPERATE - NO ACK Treated
20 0,1,2,5,6 Static Counter [9] FREEZE & CLEAR Treated
[9] FREEZE & CLEAR - NO ACK Treated
[22] ASSIGN CLASS Treated
41 1 Setpoint: 16-bits [3] SELECT Treated
analogue output block
[4] OPERATE Treated
41 2 Setpoint: 32-bits [3] SELECT Treated
analogue output block
[4] OPERATE Treated
51 1 Time and Date CTO [2] WRITE Treated
(Common Time
Occurrence)
60 1 Class 1 [20] Unable spontaneous Treated
[21] Disable spontaneous Treated
[22] Assign Class Treated
70 1 File Not treated for
the moment
3.3.2.2.2 Output
Object Variation Data Function

01 0,1,2 Static BI [1] READ
02 0,1,2,3 BI Event [1] READ
20 0,1,2,5,6 Static Counter [1] READ
22 0,1,2,5,6 Counter change event [1] READ
30 0,1,2,3,4 Static Measurement [1] READ
32 0,1,2,3,4 Measurement Event [1] READ
60 01 Class 0 [1] READ
60 02,03,04 Class 1,2,3 [1] READ
3.4 IEC 60870-5-101 communication

3.4.1 Finality
The purpose of this chapter is not to describe the T101 protocol [see IEC 60870-5-101
documentation for that] but to specify the use of the T101 protocol on a SCADA link of the
MiCOM C264.
As the MiCOM C264 is the slave on the network - regards to SCADA - this protocol is
referenced as “Slave T101” in the MiCOM C264.
Here are described:
• Specific behaviours attached to the protocol T101
• Part of the T101 protocol used and not used

3.4.2 Interface

The interface with the SCADA is defined in § Slave T101 interoperability.
3.4.3 Behaviour
3.4.3.1 SBMC mode
Specific treatment: Suppressed state does not exist in T101. So when bay turns to SBMC
mode, MiCOM C264 will tag data with “Substituted” state with configured value.
3.4.3.2 Balanced mode
Slave T101 manages both balanced and unbalanced modes.
3.4.4 Data sent to SCADA

3.4.4.1 Concept of group
BI, MEAS and SPI may be assigned to a “GI group” [group number from 1 to 16].
CT may be assigned to a “CT group” [group number from 1 to 4].
“GI group” and “CT group” are completely independent.
The same data can be:
• Affected to no group
• Affected to one group (and only one).

The configuration of the MiCOM C264 allows assigning each BI, MEAS, SPI and CT to a
group.
A BI can be sent in the following case:
• On cyclic BackGround scan Not dated COT = 2
• Spontaneously on change of state Dated COT = 3
• In response to a general interrogation command Not dated COT = 20
• In response to a group interrogation command Not dated COT = 21 to 36

The configuration of the MiCOM C264 allows:
• The kind of time tag to use for spontaneous data (the same for all data)
• In which case each BI must be sent

A MEAS can be sent in the following case:
• Periodically (Measurement cycle) Not dated COT = 1

For a MEAS, “Measurement cycle” and “BackGround scan” are exclusive.
The configuration of the MiCOM C264 allows indicating:
• The format to use for Measurement transmission (the same for all measurements)
• In which case each MEAS must be sent

3.4.4.4 Counters
A CT can be sent in the following case:
• In response to a general counter interrogation command Not dated COT = 37
• In response to a group counter interrogation command Not dated COT = 38 to 42

• In which case each counter must be sent

3.4.4.5 Tap position
A SPI can be sent in the following case:

• In which case each SPI must be sent

3.4.5 Configuration
Specific configuration data for “T101 Slave” are as follows:
• For each T101 network:
− Lengths to use for variable fields of T101 frame
− Transmission mode (UnBalanced, Balanced)
− Link address of the MiCOM C264
− Common address of ASDU of the MiCOM C264
− Kind of time tagging to use for spontaneous messages (CP24Time2A,

CP56Time2A)
− MEAS format (Normalised, 1: Scaled, 2: Float)
− Period of the cyclical emission of measurements
− Period of the BackGround emission of BI, MEAS and TPI
• Description of a BI:
− T101 address of the BI
− Spontaneous Dated Management (Y/N)
− SOE Management (Y/N)
− BackGround emission of the BI (Y/N)
− "T101 GI group" to which the BI is assigned

• Description of a Measurement:
− T101 address of the MEAS
− Variation
− Kind of cyclical emission of the MEAS (none, periodic, BackGround)
− "T101 GI group" to which the MEAS is assigned
• Description of a Counter:
− T101 address of the CT
− "T101 CT group" to which the CT is assigned
• Description of a SPI:
− T101 address of the SPI
− BackGround emission of the SPI (Y/N)
− Variation
− "T101 GI group" to which the SPI is assigned
• Description of a Control:
− T101 address of the CO
− Time out
• Description of a Setpoint:
− T101 address of the SP
− Time out
3.5 IEC 60870-5-104 communication
3.6 MODBUS communication
4. IED COMMUNICATION
4.1 Overview
Different types of IEDs are connected to a MiCOM C264 through networks using various
legacy protocols.
The legacy protocols which it is planned to develop are as follows [sorted in the order of
development]:
1. T103
2. Modbus
3. DNP3
4. 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 4.2
Features specific to each protocol are specified in subsequent paragraphs.
4.2 IED Common functionality

4.2.1 Interface
4.2.1.1.1 Input
Sender Data Notes

Single Control Treated
Dual Control Treated
Handling of control
SBO Treated
sequences
1 among N Not Treated for the moment
Setpoint Not Treated for the moment
Alarm function Alarm acknowledgement Not Treated for the moment
Command to Enable / Disable Will be treated as soon as it will
automatic upload of Disturbance be implemented in the upper
upper transmission file of an IED transmission
Command to get Disturbance file
Treated
of an IED
Tunnelling Legacy Frames Treated
DB management Configuration of transmission Treated
4.2.1.1.2 Output
Receiver Data Note

Digital input state Treated
Binary input processing
Dated Digital input change
Measurement treatment Measurement Treated
Non tariff metering Counter Not Treated for the moment
Measurement treatment Tap position Not Treated for the moment
Archiving Events records Not Treated for the moment
Handling of control
Control acknowledgement Treated
sequences
Setpoint acknowledgement Not Treated for the moment
Alarm function Alarm Not Treated for the moment
A disturbance file of an IED is Treated or not, Depending on
available the protocol
upper transmission
Treated or not, Depending on
Disturbance record file
the protocol
Tunnelling Legacy Frames
the protocol
Communication state of IED
Application Treated
(connection, disconnection)
Measurement treatment Default position
the protocol
4.2.1.2 Interface to IEDs
4.2.1.2.1 Input
Data Note
Digital input Treated
Measurement Treated
Default position Depending on the protocol
Counter Not Treated for the moment
Tap position Not Treated for the moment
Control acknowledgement Treated
Setpoint acknowledgement Not Treated for the moment
Alarm Not Treated for the moment
Treated or not, Depending on the
Disturbance record
protocol
Tunnelling Frame response
protocol
4.2.1.2.2 Output
Data Note
Control Treated
Setpoint Not Treated for the moment
Alarm acknowledgement Not Treated for the moment
Tunnelling Frame question
protocol
Time synchronisation
protocol
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 off:
• 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 Initialisation of the line
Before being able to communicate on the network, the link must be initialised. The
parameters of initialisation are as follows (non exhaustive list):
• Port number to be used
• baud rate
• parity
• number of start and stop bits
• carrier management
• …
4.2.2.3 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.
NOTES: 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.
It is to the IED scope to know if it must take into account the network’s
synchronisation or another external synchronisation.
4.2.2.4 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(1) questions without answer, an IED becomes

Disconnected]
• Maximum time to wait for a response
• Minimum time between two frames on the network
• Sending applicative requests to IEDs

Optimisation of polling maybe 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 have 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 broken 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 begins again where it was
abandoned.
• Remote control to transmit to a slave

Control is priority request. So, when a control must be sent to an IED, the polling is
stopped, the control is sent and the polling begins again where it was abandoned.
1
The number of attempts to connect an IED before saying it DISCONNECTED depends on the
protocols and the implementation.
4.2.2.5 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 : Idem 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.
General interrogation
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:
• There is place reserved in the RAM of the MiCOM C264 to store Disturbance Files
uploaded from IEDs
• 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 have 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.
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 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.
1. 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:
1. 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.
2. 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.5 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.2.6 Configuration
• Number of networks
• For each network:
− Port identification
− Transmission characteristics ( bauds, parity, …)
− Protocol
− Number of IEDs
− For each IED:
− Address
− Enable / Disable of automatic upload of Disturbance file
− Number and table of DI
− Number and table of Measurements
− Number and table of controls

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 – i.e. CO,
MEAS, DI, disturbance files – 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.
4.3.2 Reference documents
• “Communication’s rules on an AREVA MODBUS network” issue F document

4.3.3 Interface
4.3.3.1.1 Output
Precision:
Receiver Data Note

Measurement treatment Default position Not Treated [no specific treatment is
implemented in order to manage this
information]

4.3.3.2.1 Introduction
The main difficulty of implementing the MODBUS protocol is that this protocol does not
define an application layer. So for each device you want to connect to a MODBUS network,
you will have to perform specific developments.
Nevertheless, AREVA as developed rules that should be common to every AREVA devices.
This is described in the AREVA rules
As a result, the approach for implementing the MODBUS protocol is the following one: if a
new device that has to be connected to a MODBUS network does not conform to the AREVA
rules, either you develop the specificity of the device or you consider it as a generic
MODBUS device.
In a first step, here is what will be implemented:
• Generic MODBUS: this MODBUS implementation should allow to connect any type of
IEDs to a MODBUS network;
• Specific MODBUS: P127, M300 for the moment;
• MODBUS that conforms to the AREVA rules.

4.3.3.2.2 Implemented function numbers

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.4 Behaviour
4.3.4.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 DIs
• 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.

4.3.5.1 MEAS
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.5.2 DIs
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 sate of each DI with the previous state of this DI. So the MiCOM C264 itself
performs the dating of a change of state of a DI.
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.
Other
Specific developments should be performed.
4.3.5.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.6.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 (MODBUS
function nb7).
4.3.6.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 will be
performed through a broadcast frame.
There will be 3 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;
• Other: The format and the address must be known.

No calculation of the transmission delay is performed.
4.3.6.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.7 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

The performances depend a lot on the number of devices connected on the network. It is
advised to connect devices that have quiet the same performance level on a given network,
i.e. the same reply time for instance.
Notice that each device on a MODBUS network must have the same synchronisation mode.
Specific behaviours corresponding to other devices will be treated through the generic
MODBUS implementation or through specific MiCOM C264 developments.
4.3.9 Configuration
Specific configuration data for Modbus are the following ones:
• For each MODBUS network:
− Synchronisation period
− Synchronisation type
− Answer timeout
− Number of retries
− For each IED on the network:
− IED address on the MODBUS network
− Polling frame (status byte, mirror frame...)
− IED type (M300, P127, Px2x, Divers (generic))
• Description of a DI:
− DI address in the IED mapping (word or bit address)
− DI number: bit number in a word if the read N words function is used
− Modbus function to be used (function Nb 1-2-3-4)
− MEAS address in the IED mapping (word address)
− Modbus function to be used (function Nb 3-4)
− Format of the measurement (e.g.: INT8, INT16, UNIT8, UINT16...)
• Description of a Command:
− CO address in the IED mapping (bit address)
− Modbus function to be used

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
• Part of the DNP3 protocol used and not used

4.4.2 Interface
4.4.2.1.1 Output
Precision:
Receiver Data Note

Non tariff metering Counter Treated

4.4.2.2.1 Input
Precision:
Tunnelling and Disturbance management are not treated in DNP3 Protocol.
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 exploited.
4.4.2.2.2 Output
Object Variation Data Function Note

12 01 Command: Control [3] SELECT Treated
Relay Output Block
[4] OPERATE Treated
[4] 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 SPI,
− 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 Measurements 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 Configuration
Specific configuration data for DNP3 are the following:
• For each DNP3 network:
− For each IED:
− The Polling Mode: by class (class 1/2/3) or by object type (bi, measurement,
counter)
− The type of synchronisation of the IED: Network Synchronisation or External

Synchronisation
− Description of a DI: Index
− Description of a Measurement: Index
− Description of a Counter: Index
− Description of a Control: Index

4.5 IEC 60870-5-103 Communication
4.5.1 Finality
The purpose of this chapter is not to describe the T103 protocol [see IEC 60870-5-103
documentation for that] 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 Interface
4.5.2.1.1 Output
Precision:
Receiver Data Note

Measurement treatment Default position Treated

4.5.2.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 exploited
6 Time synchronisation acknowledgement Treated
8 End of GI Treated
9 Measurement Treated
10 General Data Not treated
11 General Identification Not treated
23 … 31 Disturbance file management Treated
45 Acknowledge of Single Command Px3x only
46 Acknowledge of Double Command Px3x only
65 Single Point Px3x only
66 Single Point with Time Tag Px3x only
67 Double Point Px3x only
68 Double Point with Time Tag Px3x only
73 Measurement, Normalised value Px3x only
77 Measurement Px2x only
4.5.2.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 Px3x only
46 Double Command Px3x 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 lose information [DI and
AI change]
For security raison, at the end of a tunnelling session, a GI is done
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 Measurements 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.5.1 Controls
• An ASDU Number plus 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
The implementation of the “Master T103” is limited to the ASDU indicated in § 4.5.2.2 which
is a subset of the ASDU described in the official documentation of the IEC 60870-5-103
protocol, and “ ACA Part 4: Communication based on IEC60870-5-103 ” and “ ACA Part 5:
Communication for the Subsystem Control and Monitoring ” for Private range.
That implies that ASDU with private number and/or private formats, which are not listed, are
not managed.
The configuration allows to manage Private information by indicating the couple (Function
Type, Information Number) of each information, providing that information are transmitted
through standard ASDU.
4.5.7 Configuration
Specific configuration data for T103 are the following:
• For each T103 network:
− For each IED:
− The type of the IED (standard, S20 or S30)
− The Function type of the IED [allow to identify special DI]
− The 4 configurations. Each configuration includes:
− Nominal Voltage
− Nominal Current
− Nominal Frequency
• Description of a DI:
− ASDU number
− Function type
− Information Number
− Common Address of ASDU

− ASDU Number
− Function type
− Rank of the measurement in the ASDU
− Kind of measurement
− Common Address of ASDU
• Description of a Control:
− ASDU number
− Function type
BLANK PAGE
MiCOM C264/C264C
COMMISSIONING
CONTENT

1.1 Introduction 3
1.2 Definition 3
1.3 Commissioning the product 3
1.4 Responsibility 4
1.5 Setting familiarisation 4
2. REQUIREMENTS 4
3. COMMISSIONING TESTS 4
3.1 Preparation 4
3.2 Check version & number 5
3.3 Checking the boards 6
3.4 Checking the binary signal inputs 7
3.5 Checking the output relays 7
3.6 Checking the current-measuring inputs 7
3.7 Testing the connection of the phase current and voltage transformers with load current for
correct phase 8
3.8 Testing the communication 8
3.8.1 Ethernet UCA2 8
3.8.2 MODBUS 8
3.8.3 IEC 60870-5-103 8
3.8.4 IEC 60870-5-101 8
3.9 Testing the control functions 8
3.10 Switching from local to remote control 8
3.10.1 Local control 8
3.10.2 Remote control 9
3.11 Switchgear unit not responding 9
3.12 Checking limit value monitoring 10
3.13 Completion of commissioning 10
C264/EN CM/A13 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) and all 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 LCD (Local Control Display) 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.
Commissioning and the validation tests should only be carried out by qualified and
competent persons.
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
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 startup, various start-up tests are carried out (see section entitled ‘Diagnose level1’ in
Chapter C264/EN MF (Maintenance)).
The LED indicator labelled ‘HEALTHY’ (H4) and the LED indicator labelled ‘OUT OF
SERVICE’ (H3) will light up.
After approximately 5 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:
• Is the setting version compatible with MiCOM C264 hardware and software?
• 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, 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 his 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 – maintenance, operational, or stand-by – indicates whether the
device is in a standby or working mode.
S E R V . I N F O <time>
C O M P U T E R S E R I A L N B :
S O F T W A R E V E R S I O N :
D A T A B A S E 1 V E R S & S T A T E :
D A T A B A S E 2 V E R S & 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 :
3.3 Checking the boards

By using the MiCOM C264 front panel, it is possible to determine whether the C264 boards
that are present are recognised correctly by the MiCOM C264 (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 has:
• GHU Graphical Human Unit
• BIU Basic Interface Unit (power converter)
• 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 the number of boards
configured in the settings – the following messages are generated depending on the results:
• OK Board configured present and operational
• FAILURE Board configured present and faulty
• MISSING Board configured not present
• TOO MANY Board not configured but present (spare)
• ABSENT Board not configured and not present
B O A R D S <time>
<Board Label>
<Number>
<Board Status>
<Board Label>
<Number>
<Board Status>
D I U 0 1
O K
D O U 0 1
F A I L U R E
↑ ↓
3.4 Checking the binary signal inputs

By using the MiCOM C264 front panel, it is possible to determine whether the input signal
that is present is recognised correctly by the MiCOM C264 (refer to chapter C264/EN HI).
The messages displayed have the following meanings:
• Low: Not energised.
• High: Energised.
• Without function: No functions are assigned to the binary signal input.

This display appears regardless of the binary signal input mode selected.
3.5 Checking the output relays
It is possible to trigger the output relays for a settable time period for test purposes (time
setting at O U T P : H o l d - t i m e f o r t e s t in 'Oper/CtrlTest/' folder). First select the output
relay to be tested (OUTP: R elay assign. f.tes t, ‘Oper/CtrlTest/’ folder). Test triggering
then occurs via OUTP: R e l a y t e s t (Oper/CtrlTest/' folder). It is password-protected (see
the section entitled ‘Password-Protected Control Operations’ in Chapter 6).
BEFORE STARTING THE TEST, OPEN ANY TRIGGERING CIRCUITS TO
! EXTERNAL DEVICES SO THAT NO INADVERTENT SWITCHING
OPERATIONS WILL TAKE PLACE.
3.6 Checking the current-measuring inputs
By applying appropriate analogue signals as ‘measuring variables’ to the measuring inputs,
the user can check via the operator display (see Chapter ‘Information and Control
Functions’) whether the protection and control unit detects the analogue signals with the
specified accuracy (folder ‘Oper/Cycl/Data/’).
• M AIN : Cu rre n t A p .u .: Display of the updated phase current A referred to the

nominal device current Inom
• M AIN : Cu rre n t B p .u .: Display of the updated phase current B referred to the

• M AIN : Curre n t C p .u .: Display of the updated phase current C referred to the

• M AIN : C urre n t IN p .u .: Display of the updated phase current IN referred to the

APPLICATION OF ANALOG SIGNALS TO THE MEASURING INPUTS

! MUST NOT EXCEED THE MAXIMUM PERMISSIBLE RATING OF THE
MEASURING INPUTS (SEE THE CHAPTER ON TECHNICAL DATA).
3.7 Testing the connection of the phase current and voltage transformers with load
current for correct phase
The user can check to make sure connection to the system's current and voltage
transformers involves the correct phase by consulting the operating data displays for load
angle (M A I N : L o a d a n g l e p h i A , M A I N : L o a d a n g l e p h i B , M A I N : L o a d
a n g l e p h i C in the 'Oper/Cycl/Meas/' folder).
To this end, it is necessary for the connection to be standard in accordance with the
standard schematic diagram shown in Chapter ‘Installation and Connection’ and for the
setting of MAIN : Conn. meas . c irc . IP to be ‘standard’. In the case of a purely resistive
load, the load angles of all three phases must be 0° in line direction. The load angles are
only determined if at least 5% of the nominal device current is flowing.
3.8 Testing the communication
3.8.1 Ethernet UCA2
The Ethernet UCA2 links to connected MiCOM C264 can be tested using Ethernet ping.
3.8.2 MODBUS
The serial links to connected MODBUS IEDs can be tested using logical state signals.
3.8.3 IEC 60870-5-103
The serial links to connected MODBUS IEDs can be tested using logical state signals.
3.8.4 IEC 60870-5-101
The serial links to connected MiCOM C264 to a SCADA can be tested using logical state
signals.
3.9 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.10 Switching from local to remote control
Switchgear units can be controlled locally using the keys on the local control panel, remotely
through the communication interface, or through appropriately configured binary signal
inputs.
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.10.1 Local control
The switchgear unit to be controlled is selected by pressing the Selection key on the local
control panel and then controlled by pressing the Open or Close key.
If the switchgear units are to be controlled through binary signal inputs, then the appropriate
signal input must be triggered.
3.10.2 Remote control

The switchgear units can be controlled via the communication interface or appropriately
configured binary signal inputs.
3.11 Switchgear unit not responding
If a switchgear unit does not respond to a switching command, it could be due to the
following factors:
• The general control enable – if configured – has not been set. (configuration at
M A I N : I n p . a s g . c t r l . e n a b l . , 'Par/Func/Glob' folder)
• Interlocking has been triggered. (This can be checked at MAIN: I n t e r l o c k e q u .

v i o l . , 'Oper/Cycl/Log/'.)
• For bays with direct motor control only: Motor monitoring has been triggered. (This can
be checked at MAIN: M o n . m o t . d r i v e s t r . , 'Oper/Cycl/Log/'.)
To determine which interlocks are activated, check as follows:
• For bay interlock (BI) check: M A I N : B a y i n t e r l o c k . a c t . , 'Oper/Cycl/Log/' folder
• For substation interlock (SI) check: M A I N : S u b s t . i n t e r l . a c t . , 'Oper/Cycl/Log/'

folder
• For local control: It is possible to deactivate the interlock through appropriately

configured binary signal input.
Configuration through MAIN: In p . a s g . i n t e r l . d e a c t , 'Oper/Func/Glob' folder)
NOTE: Substation interlocking is only active when there is communication
with the substation control level through the communication interface.
In the event of a communication error, the unit will switch
automatically to ‘bay interlock without station interlock’. To determine if
there is a communication error, check at MAIN: Co mm un ica tion
er ror , ‘Oper/Cycl/Log/’ folder.
Substation interlocking can be deactivated selectively for each switchgear unit and each
control direction – Open or Close. (This can be checked at Devil: O p e n w / o s t a t . i n t e r
or DEVxx: C l o s e w / o s t a t . i n t . , 'Oper/Cycl/Log/' folder.)
3.12 Checking limit value monitoring

The limit value monitoring function can only be checked if limit value monitoring has been
activated. This can be determined via the logic state signal L I M I T : E n a b l e d
(‘Oper/Cycl/Log/’ folder).
By specifying the appropriate measured variables; it is possible to check the over- and
undercurrent stages and the over- and undervoltage stages as well as the associated timer
stages.
APPLICATION OF ANALOG SIGNALS TO THE MEASURING INPUTS
! MUST NOT EXCEED THE MAXIMUM PERMISSIBLE RATING OF THE
MEASURING INPUTS (SEE THE CHAPTER ENTITLED 'TECHNICAL
DATA').
3.13 Completion of commissioning
Before the MiCOM C264 is released for operation, the user should make sure that the
following steps have been taken:
• All memories have been reset.

(Reset at MAIN: G e n e r a l r e s e t (password-protected) and MT_ R C : R e s e t
r e c o r d i n g , both in 'Oper/CtrlTest/ folder.)
• Blocking of output relays has been cancelled.

(O U T P : O u t p . r e l . b l o c k U S E R in 'Par/Func/Glob/' folder, setting 'No')
• The device is on-line.

(M A I N : D e v i c e o n - l i n e , 'Par/Func/Glob/' folder, setting 'Yes (on)')
• The correct control point – Local or Remote – is activated.
• The desired interlocking conditions are activated.

After completion of commissioning, only the green LED indicator signalling ‘Operation’ (H1)
should be on.
Record Sheet C264/EN RS/A13
MiCOM C264/C264C
RECORD SHEET
CONTENT
2. COMMISSIONING TEST RECORD 3

2.1 Product checks 4
2.1.1 Visual inspection 4
3. SETTING RECORD 4
C264/EN RS/A13 Record Sheet
BLANK PAGE

This document is a chapter of MiCOM C264 documentation binders. It describes the
Commissioning record sheet and the Setting Record (RS) of this computer.
2. COMMISSIONING TEST RECORD

By connecting a PC with a hyperterminal application to the serial port on the front of the
computer, you will be able to send a command to make the computer return this
commissioning record sheet.
Date : Engineer :
Station : Circuit :
System : Frequency :
Front Plate Information
Computer type
Model number
Serial number
Rated current In
Rated voltage Vn
Auxiliary voltage Vx
Test equipment used

This section should be completed to allow future identification of devices that have been
commissioned using equipment that is later found to be defective or out of tolerance.
Overcurrent test set Model:

Serial No:
Phase angle meter Model:
Serial No:
Phase rotation meter Model:
Serial No:
Insulation tester Model:
Serial No:
Setting software Type:
Version:
*Delete as appropriate
Have all relevant safety instructions been followed? Yes/No*
2.1 Product checks

With the computer de-energized
2.1.1 Visual inspection
Relay damaged? Yes/No*

Rating information correct for installation? Yes/No*
Case earth installed? Yes/No*
3. SETTING RECORD
By connecting a PC with a hyperterminal application to the serial port on the front of the
computer, you will be able to send a command to make the computer return this
commissioning record sheet.
Date : Engineer :
Station : Circuit :
System : Frequency :
Front Plate Information
Computer type
Model number
Serial number
Rated current In
Rated voltage Vn
Auxiliary voltage Vx
Setting groups used * Delete as appropriate
Group 1 Yes/No*
Group 2 Yes/No*
Group 3 Yes/No*
Group 4 Yes/No*
0000 SYSTEM DATA
0001 Language English/Français/Deutsch/Español*

0003 Sys Fn Links
0004 Description
0005 Plant Reference
0006 Model Number
0007 Firmware Number
0008 Serial Number
0009 Frequency
000A Comms Level
000B Relay Address
0011 Software Ref. 1
00D1 Password Control Level 0/Level 1/Level 2*
00D2 Password Level 1
00D3 Password Level 2
BLANK PAGE
MiCOM C264/C264C
MAINTENANCE
CONTENT
2. STANDARD MAINTENANCE OPERATION 3

2.1 Level 1 diagnosis facilities 3
2.1.1 Front panel fixed MiCOM C264/C264C LED 3
2.1.2 Front panel indications 4
2.2 Maintenance period 6
2.3 Maintenance checks 6
2.3.1 Alarms 6
2.3.2 Opto-isolators 6
2.3.3 Output relays 6
2.3.4 Measurement accuracy 6
2.4 Method of repair 7
2.4.1 Replacing the complete MiCOM C264/C264C 7
2.4.2 Replacing a board 8
2.5 Cleaning 18
3. ENGINEERING MAINTENANCE OPERATION 19

3.1 Level 2 diagnosis facilities 19
3.1.1 PACiS Equipment Simulator 19
3.1.2 ISAGRAF workbench runtime 19
3.2 Downloading a NEW software VERSION 19
3.2.1 Settings for downloading software 19
3.2.2 Software version verification 20
3.2.3 Copy new software into MiCOM C264/C264C 20
3.2.4 Return to standard parameters 21
3.2.5 Helpful features in the MiCOM C264/C264C 22
C264/EN MF/A13 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.
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 their 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 (Local Control Display) protected by password level 1

2.1.1 Front panel fixed MiCOM C264/C264C LED
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:
1 Red Trip OFF Not Used

2 Yellow Alarm ON If at least one Not acknowledged alarm
3 Yellow Out of Service ON HALT, MAINTENANCE or FAULT mode
BLINK hardware FAULT (see Faults Panel)
OFF Fully operational
4 Green Healthy ON MiCOM C264/C264C POWER ON
5 Red Edit mode ON setting parameter allowed in menu tree
Normally LED 4 is ON, and LED 3 OFF. MiCOM C264/C264C is fully operational.
If all LEDs and LCDs are OFF, the Front Panel is out of order.
• If other MiCOM C264/C264C functions are operating (communication, automation,

printing…), or if the watch dog on BIU (see chapter C264/EN CO) is at 1, the wire
between CPU and FP, or FP itself is not operational. Checked these after
authorisation and power off the MiCOM C264/C264C.
• If the watchdog is off and the supply is on, the MiCOM C264/C264C is not operating.
Switch off the power and replace the BIU or CPU board.
If the POWER LED is OFF and LCD or other LED light on, the Front Panel needs
replacement.
With POWER LED ON and BLINKING LED 3, use the LCD to help determine the faulty
board.
If the Healthy and Out of Service LED’s are OFF, the MiCOM C264/C264C is in one of its
predefined modes, i.e.
• not operational.
• probably not powered.

If the automation and communications are still operational, check the power supply and
ensure that the BIU, CPU and Front Panel/CPU cable are powered.
The LED indicators in front panel is the first method to check the information needed to fill in
the commissioning test and setting record sheets.
2.1.2 Front panel indications
When the MiCOM C264/C264C is powered on, the front panel displays a message
“AREVA”.
Follow the scheme below to check the MiCOM C264/C264C’s configuration:
Bay panels Menu

1 to 8 Tree
Panel
Configuration
panels
Scrolling
BOARDS
Up/Down
IED
SERVICE
Disturbance
Record Panel
C0073ENa
FIGURE 1: CONFIGURATION PANEL

To check the wiring of the I/O boards, there is one panel per board indicating the values of
each DI and DO.
For an input board, this panel looks like:
B I N I N P U T
B O A R D X X Board type
D I X X X value D I X X X value
↑ ↓
TABLEAU 1: BINARY INPUT PANEL

For an output board, this panels looks like:
B I N O U T P U T
B O A R D X X Board type
D O X X X value D O X X X value
↑ ↓
TABLEAU 2: BINARY OUPUT PANEL

For further details about navigating between the different panels see the C264/EN HI
chapter.
These indications you are necessary to fill in the commissioning record sheet after
conducting maintenance operations.
2.2 Maintenance period

It is recommended that AREVA T&D products receive periodic monitoring after their
installation. Deterioration may occur over time. Because of the critical nature of the MiCOM
C264/C264C and its non-frequent operation, it is recommended to confirm that they are
operating correctly at regular intervals.
The AREVA MiCOM C264/C264C life is at least 20 years.
MiCOM C264/C264C is self-supervising and therefore requires less maintenance than
previous products. Most problems will result of an alarm so that immediate action can be
taken. 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 Maintenance checks
Although some functionality checks can be done from a remote location by using the MiCOM
C264/C264C communications facilities, these are restricted to checking that the MiCOM
C264/C264C is measuring the applied currents and voltages accurately, and checking the
circuit breaker maintenance counters. Therefore it is recommended that the maintenance
checks (i.e. at the substation itself) are done locally
of the safety and technical data sections, and the ratings on the equipment's rating label.
2.3.1 Alarms
The alarm status LED should first be checked to identify if any alarm conditions exist. If so,
press the read key ! repeatedly to step through the alarms. Clear the alarms to extinguish
the LED.
2.3.2 Opto-isolators
The opto-isolated inputs can be checked to ensure that the MiCOM C264/C264C responds
to their energisation by repeating the commissioning test detailed in Chapter C264/EN CM
(Commissioning).
2.3.3 Output relays
The output relays can be checked to ensure that they operate by repeating the
commissioning test detailed in Chapter C264/EN CM (Commissioning).
2.3.4 Measurement accuracy
If the power system is energised, the values measured by the MiCOM C264/C264C can be
compared with known system values to check that they are in the approximate range that is
expected. If they are then the analogue/digital conversion and calculations are being
performed correctly by the MiCOM C264/C264C. Suitable test methods can be found in the
Chapter C264/EN CM (Commissioning).
Alternatively, the values measured by the MiCOM C264/C264C can be checked against
known values injected into the MiCOM C264/C264C via the test block, if fitted, or injected
directly into the MiCOM C264/C264C terminals. Suitable test methods can be found Chapter
C264/EN CM (Commissioning). These tests will prove the calibration accuracy is being
maintained.
2.4 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 faulty boards should be replaced, as
it is not possible to perform repairs on damaged circuits. Thus either the complete MiCOM
C264/C264C or just the faulty board, identified by the in-built diagnostic software, can be
replaced. Advice about identifying the faulty board can be found in Chapter C264/EN PR
(Problem Analysis).
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 possibility of incompatibility between replacement boards. However, 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.
Replacing boards can reduce transport costs but requires clean, dry conditions on site and
higher skills from the person performing the repair. However, if an approved service centre
does not perform the repair, the warranty will be invalidated.
of the safety and technical data sections and the ratings on the equipment's rating label. This
should ensure that incorrect handling of the electronic components causes no damage.
2.4.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 should replacement or repair become necessary without having to
disconnect the scheme wiring.
Before working at the rear of the MiCOM C264/C264C, isolate all voltage and current
supplies to the MiCOM C264/C264C.
NOTE: The MiCOM C264/C264C have integral current transformer shorting
switches which close when the heavy duty terminal block is removed.
Disconnect the MiCOM C264/C264C earth, IRIG-B and fibre optic connections as
appropriate, from the rear of the MiCOM C264/C264C.
There are two types of terminal block used on the MiCOM C264/C264C, medium and heavy
duty, which are fastened to the rear panel using cross-head screws, as in Figure 2.
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 2: 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.
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 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.
Withdraw the MiCOM C264/C264C from the panel, rack, etc. carefully because it will be
heavy due to the internal transformers.
To reinstall the repaired or replacement MiCOM C264/C264C follow the above instructions in
reverse, ensuring that each terminal block is relocated in the correct position and the case
earth, IRIG-B and fibber optic connections are replaced. To facilitate easy identification of
each terminal block, they are labelled alphabetically with 'A' on the left hand side when
viewed from the rear.
Once reinstallation is complete the MiCOM C264/C264C should be recommissioned using
the instructions in sections 1 to 7 inclusive of this chapter.
2.4.2 Replacing a board
If the MiCOM C264/C264C fails to operate correctly refer to Chapter C264/EN PR (Problem
Analysis), to help determine which board has become faulty.
To replace any of the MiCOM C264/C264C’s boards it is necessary to first remove the front
panel.
Before removing the front panel to replace a board the auxiliary supply must be removed. 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 90•, 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 THE

FRONT PANEL IS CONNECTED TO THE REST OF THE MiCOM
C264/C264C CIRCUITRY BY A 64-WAY RIBBON CABLE.
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.
The ribbon cable is fastened to the front panel using an IDC connector; a socket on the cable
itself and a plug with locking latches on the front panel. Gently push the two locking latches
outwards which will eject the connector socket slightly. Remove the socket from the plug to
disconnect the front panel.
C0111ENa
FIGURE 3: MiCOM C264C
C0110ENa
FIGURE 4: MiCOM C264

The boards within the MiCOM C264/C264C are now accessible. Figures 3 and 4 show the
board locations for the MiCOM C264/C264Cs in size 40TE (C264C) and size 80TE (C264)
cases respectively.
NOTE: The numbers above the case outline identify the guide slot reference
for each printed circuit board. Each printed circuit board has a label
stating the corresponding guide slot number to ensure correct re-
location after removal. To serve as a reminder of the slot numbering
there is a label on the rear of the front panel metallic screen.
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, which is the inner bus. To remove a
card you need to take off this printed circuit by holding it by the two extremities plus remove
the screw plus the bar of maintains that maintain the card fixed into the case.
The slots inside the case to hold the boards securely in place each correspond to a rear
terminal block. Looking from the front of the MiCOM C264/C264C these terminal blocks are
labelled from right to left.
NOTE: To ensure compatibility, always replace a faulty board with one of an
identical part number.
2.4.2.1 Replacement of the Binary Input Unit (BIU)

The BIU is the power supply board located on the extreme left-hand side of all 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.
The power supply board is the one with two large electrolytic capacitors on it that protrude
through the other board that forms the power supply module. To help identify that the correct
board has been removed, Figure 10 illustrates the layout of the power supply board for all
voltage ratings.
To update the MiCOM C264/C264C configuration see the chapter “Update the MiCOM
C264/C264C configuration information” at the end of this document.
To aid the recognition of these boards see the following figure:
C0031ENa
FIGURE 5: BIU BOARD

2.4.2.2 Replacement of the main processor board (CPU)

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. Therefore, it is useful if an electronic copy of the application-
specific settings is available on disk. Although this is not essential, it can reduce the time
taken to re-enter the settings and hence the time the MiCOM C264/C264C is out of service.
The CPU board is located next to the BIU board. To aid the recognition of these boards see
the following figure:
C0034ENa
FIGURE 6: MAIN CPU BOARD

2.4.2.3 Replacement of the Digital Input Unit (DIU)

The DIU board can be located in any slot between 03 to 16. To aid the recognition of these
boards see the following figure:
C0035ENa
FIGURE 7: DIGITAL INPUT UNIT

2.4.2.4 Replacement of the Digital Output Unit (DOU)

The DOU board can be located in any slot between 03 to 16. To aid the recognition of these
C0036ENa
FIGURE 8: DIGITAL OUTPUT UNIT

2.4.2.5 Replacement of the Analog Input Unit (AIU)

The AIU board can be located in any slot between 03 to 16. To aid the recognition of these
C0038ENa
FIGURE 9 ANALOG INPUT UNIT

2.4.2.6 Replacement of the Circuit breaker Control Unit (CCU)

The AIU board can be located in any slot between 03 to 16 To aid the recognition of these
C0037ENa
FIGURE 10: CIRCUIT BREAKER CONTROL UNIT

2.4.2.7 Replacement of the Transducerless Measurements Unit (TMU)
The measurement unit comprises of two boards fastened together, the Current transformer
board and the Voltage transformer board. Both boards must be removed together as a
complete unit.
2.4.2.8 Update the MiCOM C264/C264C configuration information

Before re-assembling the module with a replacement board, check that the number on the
round label adjacent to the front edge of the board matches the slot number into which it will
be fitted. If the slot number is missing or incorrect write the correct slot number on the label.
Make sure that the address for the replacement board is the same address that the board
replaced by checking the switch on the boards.
Re-assemble the module with a replacement board ensuring the inter-board connectors are
firmly pushed together and the four push-fit nylon pillars are securely located in their
respective holes in each board.
Slot the power supply module back into the relay case, ensuring that it is pushed fully back
on to the rear terminal blocks.
Refit the front panel. After refitting and closing the access covers on size 60TE cases, 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 should be recommissioned in
accordance with the instructions in sections 1 to 7 inclusive of this chapter.
2.5 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.
3. ENGINEERING MAINTENANCE OPERATION

3.1 Level 2 diagnosis facilities
By connecting a PC with an hyperterminal application to the RS232 in the front panel of the
MiCOM C264/C264C, commands can be sent that make the MiCOM C264/C264C return the
commissioning record and the setting record sheet.
3.1.1 PACiS Equipment Simulator
This engineering tool will provide assistance with checking for more obscure faults in the
MiCOM C264/C264C.
3.1.2 ISAGRAF workbench runtime
This engineering tool will provide assistance when debugging PCL functions.
3.2 Downloading a NEW software VERSION
With reference to VC Version Compatibility document, the installed MiCOM C264/C264C
may not have the last up-to-date software version. This is a maintenance operation
described in MF also given as a summary here.
MiCOM C264/C264C Start-up
After a reboot, the main operations done by MiCOM C264/C264C are:
• Load/start the BootPROM software
• Take in account start setting
• Load/start the Application software (called vxWorks)
• Load/start the DataBase of the MiCOM C264/C264C application

It is clear that this sequence should be interrupted if a new software vxWorks has to be
installed.
NOTE: Although the application software is called vxWorks, similar to the
operating system. The application software contains both vxWorks
libraries and application software.
3.2.1 Settings for downloading software
At start-up, it is necessary to start with new software extracted from host PC. Use the install
program or decompress the zipped delivery of MiCOM C264/C264C software into a FTP
server directory. This procedure can then be used even if no software has been loaded into
the MiCOM C264/C264C. The starting parameters will need to be modified as follows:
>reboot CR
Stop the sequence by pressing space bar when it is displayed
…
Look at and note current parameters with
>p CR
Enter the new start parameters with software on the host PC (in FTP directory).
>c CR
“boot device : xxx motfec0 CR
“host name : <nom PC hoste> CR
“file name : /flash/bin/vxWorks CR
“inet on Ethernet : xxx.xxx.xxx.xxx (CR) C264 IP@ CR
“host inet : xxx.xxx.xxx.xxx (CR) <PC host IP @ CR
“user : <nom user> vxWorks CR
“ftp password : <password> vxWorks CR
“flags : 0x0 CR
“target name : <nom target> <MiCOM C264/C264C name> CR
Check the entered parameters:
>p CR
>@ CR
The MiCOM C264/C264C start and may reject the database if it is not in accordance with the
software version. If database is rejected, Erase the flash memory of the MiCOM
C264/C264C for loading a new version:
>eraseFlash CR
NOTE: You will have access to this command only from the VxWorks
operating system not from the special boot software (when the prompt
is [VxWorks Boot]:).
3.2.2 Software version verification
After downloading new software, or when encountering a new MiCOM C264/C264C, the
software version can be determined as follows:
The software version is displayed at start-up or later on typing:
> version CR
vxWork version
> PRINT_CALC_VERSION
MiCOM C264/C264C version
3.2.3 Copy new software into MiCOM C264/C264C
Using the FTP server, download the following software into the MiCOM C264/C264C:
• vxWorks Application software

• mms_log UCA Agency parameters
• agency.cfg UCA Agency parameters
• lean.cfg UCA Agency parameters
• maint.dm Dat-a Model for maintenance (no DB)
• dbstatus File of the 2 DB staus
• tztab Array of translation time zone
• printer printer configuration file
Transfer the software into flash with
>bootInstall CR
Then reboot
>reboot CR
3.2.4 Return to standard parameters

When the software has been correctly downloaded, it is needed to restore the default start-
up parameters described in first chapter (or a previous section?).
The main modification applies the field BootDevice.
>c CR for configuration
“boot device : tffs=0,0 CR (from MiCOM C264/C264C flash)
“host name : <nom PC hoste> CR
“file name : /flash/bin/vxWorks CR (path into C264 flash)
“inet on Ethernet : xxx.xxx.xxx.xxx CR (MiCOM C264/C264C IP @)
“host inet : xxx.xxx.xxx.xxx CR
“user : < user name> CR
“ftp password : <password> CR
“flags : 0x0 CR
“target name : vxWorks CR
To verify the parameters, disconnect the Ethernet link from the serial link and reboot the
MiCOM C264/C264C.
>p CR
>@ CR
>Verify C264/C264C software version
3.2.5 Helpful features in the MiCOM C264/C264C

->HELP
tasks debug traces : SET_TRACES(task ID,msk,1/0)
Printer On : PRINT_ALL_ON
Printer Off : PRINT_ALL_OFF
Print Default Archive : PRINT_ARCH_FLT
: PRINT_CALC_VERSION
: PRINT_DB_VERSION
: SHOW_DB_INFO
: PRINT_CALC_MODE
Operator setting time : SET_TIME(DD,MM,YYYY,HH,MM,SS)
Print time info : GIVE_TIME
Display soft signals file : DISPLAY_FLT_FILE
Display Exceptions file : DISPLAY_EXCEPT_FILE
Ethernet interface RJ45 : SET_RJ45
Ethernet interface Opto Fdx : SET_OPTO_FDX
Ethernet interface Opto Hdx : SET_OPTO_HDX
value = 45 = 0x2d = '-'
->
->PRINT_CALC_VERSION
MiCOM C264/C264C
PROGRAM INFORMATION :
MiCOM C264/C264C
PROGRAM VERSION : A0.21
DATA BASE COMPATIBILITY : D8
MiCOM C264/C264C
LEXICAL
CONTENT
2. LEXICAL 3
C264/EN LX/A13 Lexical
BLANK PAGE

This document is a chapter of MiCOM C264 documentation binders. It is the lexical.
2. LEXICAL
AC Alternating Current
ACU Analog transduCerless Unit
Computer C264 Additional Mezzanine on CPU for CT/VT
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 Analog Input
Alarm An alarm is any event tagged as an alarm during configuration phase
AO Analogue Output
Value corresponding to a desired output current applied to a DAC.
AOU Analogue Ouput Unit
C264 board name for DC AO
API Application Programming Interfaces
ASCII American Standard Code for Information Interchange
ASDU Application Specific Data Unit
Name given in OSI protocol for applicative data (T103, T103..)
ATCC Automatic Tap Change Control
Same as AVR, automation to regulate secondary voltage
AVR Automatic Voltage Regulator
Automation used to regulate secondary voltage by automatic tap changer
control (see ATCC). Set of features can be added, see chapter C264 FD
Bay Set of LV, MV or HV plant (switches and transformer) 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 specif invalid code when coding
is not valid). Each decimal digit is coded by 4 binary digit.
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, 2 DO, 2
RS232/485 insulated ports
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 switch with capability to make line current and break fault current.
Some have isolation capability (nominal-earth at each side)
CBC Compact Bay Controller
Small capacity bay computer for Medium Voltage applications typically C264C
CCU Circuit breaker Control Unit
Computer C264 Board dedicated to switch control with 8DI, 4 DO
CCU Circuit Breaker Control Unit
Name of the C264 board with DI and power DO with inner SBO function
controlling the DO health, and in charge to control directly switch gears.
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 guarantee of
interoperability.
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 polynomal.
CSV Character SeparateValues
Asci 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 this AC value
and convert it to numerical measurement value.
CT/VT Current and Voltage transformers
(Conventional) By extension the C264 board and module (ACU, TVU, TCU) that capture via
wiring and digitalise the DC measurement.
CT/VT Current and Voltage transformers
(Non-Conventional or New generation of captor based for exemple on 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.
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, 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 transmition
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 electricly wired control.
DCT Double CounTer
Counter based on 2 DI with complementary states (counting switchgear
manoeuvre for example)
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.
DIU Digital Input Unit
Computer C264 Board name for Digital Input Unit
DM Digital Measurement
Is a measurement value which acquisition is done by DI and a specific coding
BCD, Gray, 1 among N…
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
C264 board with output relays
DP Double Point
Information/control derived from 2 digital inputs/output; usually used for
position indication of switching devices (OPEN, CLOSE).
DPS Double Point Status
Position indication of switching devices (OPEN, CLOSE).
EH90 Transmission protocol dedicated to time synchronisation and standardised by
EDF. Specification document: D.652/90-26c, March 1991.
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).
Gateway Level 6 session of OSI, the gateway is any device transfering data between
different networks and/or protocol. The RTU function of C264 gives a gateway
behaviour to SCADA or RCP level. PACIS Gateway is separate PC base
device dedicated to this function. C364 or PCI is referenced also as a gateway
between IED and upper lever of communication.
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 satelite signal, that transmit also absolute GMT
time used to synchronise a master clock
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).
HMI Human Machine Interface

Can be PACIS OI(Operator Interface) or C264 LCD (Local Control Display) or
Leds, mosaic...
HSR High Speed autoRecloser
First cycles of AR
HTML Hyper Text Mark-up Language
Used as standard for formating web display
HV High Voltage (for example 30kV to 150kV)
I/O Input/Output
IEC International Electrotechnical Commission
IED Intelligent Electronic Device
General expression for a whole range of microprocessor based products for
data collection and information processing
IRIG-B Inter-Range Instrumentation Group standard format B. This is an international
standard for time synchronisation based on analog 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 RS422).
(Kbus Courier)
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 Alstom or MODICON
LCD Liquid Crystal Display
Local Control Display
On C264
LD Ladder Diagram
LED Light Emitting Diode
LF Low Frequency
LOC Local Operator Console
Dedicated to maintenance operation
Local / Remote When set to local for a given control point it means that the commands can be
Control Mode issued from this point, else in remote control are issue for upper devices.
LV Low Voltage
MAFS Marketing And Functional Specification
MC Modular Computer
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 inputs during
(non-tariff) variable periods of time (time integration).
Metering Values computed depending on the values of digital or analogue inputs during
(tariff) variable periods and dedicated to the energy tariff management. These values
are provided by dedicated “ tariff computer ” which are external to the MiCOM
Systems.
MIDOS ALSTOM 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 Alstom 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
NBB Numerical Busbar Protection
NC Normally Closed (for a relay)
NO Normally Open (for a relay)
OBS One Box Solution
Computer which 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 which is being controlled by the same substation control
system.
OLE Object Linking and Embedding
OLE is a Microsoft specification and defines standards for interfacing objects.
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 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
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.
PSTN Public Switched Telephone Network
PT100 Temperature probes 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 bays 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 When set for a given control point it means that the commands are issued from
Mode a higher 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)
RRC Rapid ReClosure
RSVC Relocatable Static Var Compensator
RTU Remote Terminal Unit
Stand alone computer that acquires data and transmit it 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).
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, UCA2 and IEC 61850
SCADA Supervisory Control And Data Acquisition
Equivalent to RCC
SCP Substation Control Point
Name given to the device or part used to control localy 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)
SOE Sequence Of Events
Other term for the event list.
SP Single Point
SPS Single Point Status
SPC Single Point Control
ST Structured Text
Substation computer Bay computer used at substation level.
Suppression A binary information belonging to a bay in SBMC mode will be automatically
(Automatic) suppressed for the remote control. However changes of state will be signalled
locally, at SCP.
Suppression A binary information can be suppressed by an order issued from an operator.
(Manual) No subsequent change of state on a “ suppressed information ” can trigger any
action such as display, alarm and transmission.
SWR Switch Redundant
Computer C264 board Ethernet switch with redundant ethernet
SWU Switch Unit
Computer C264 board Ethernet switch
T101 Term used for IEC60870-5-101 protocol
T103 Term used for IEC60870-5-103 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
TCU Transformer Current Unit
Computer C264 CT/VT Board : Current acquisition
TIU Transformer Input Unit
Topological Interlocking algorithm, based on evaluation of topological information of the
interlocking switchgear arrangement in the HV network, the switchgear kind and position,
and defined rules for controling 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 (interger and scaled float) are in common class UCA2 Accumulator.
UTC Universal Time Coordinates (or Universal Time Code)
Naming that replace GMT (but it is the same)
VDEW Term used for IEC60870-5-103 protocol
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.
BLANK PAGE
Publication: C264/EN T/A14
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/

Schneider Micom C264C - Tech Guide PDF

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

Schneider Micom C264C - Tech Guide PDF

Uploaded by

Copyright:

Available Formats

MiCOM

MiCOM C264/C264C Page 1/2

Safety & Handling C264/EN SA/A14

Introduction C264/EN IT/A13

Technical data C264/EN TD/A13

Functionnal Description C264/EN FT/A13

Hardware Description C264/EN HW/A13

Connection C264/EN CO/A14

Installation C264/EN IN/A13

Application C264/EN AP/A13

Settings C264/EN ST/A13

Logic Diagrams C264/EN LG/A13

Communications C264/EN CT/A13

Commissioning C264/EN CM/A13

Commissioning Record Sheet C264/EN RS/A13

Maintenance C264/EN MF/A13

Lexical C264/EN LX/A13

Page 2/2 MiCOM C264

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

• 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

Insulation class IEC 601010-1: 1990/A2: 1995 This equipment

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

Page 4/8 MiCOM C264/C264C

2. INTRODUCTION TO MiCOM GUIDES

CHAPTERS ON PRODUCT DEFINITION AND CHARACTERISTICS

USER MINIMAL ACTIONS