MiCOM

C264/C264C
Bay Computer

Version B30

Technical Guide

C264/EN T/B30
Technical Guide C264/EN TG/B30

MiCOM C264/C264C Page 1/2

MiCOM C264/C264C
BAY COMPUTER
CONTENT

Safety & Handling C264/EN SA/B30

Introduction C264/EN IT/B30

Technical data C264/EN TD/B30

Functional Description C264/EN FT/B30

Hardware Description C264/EN HW/B30

Connection C264/EN CO/B30

Installation C264/EN IN/B30

Application C264/EN AP/B30

Settings C264/EN ST/B30

Communications C264/EN CT/B30

Commissioning C264/EN CM/B30

Commissioning Record Sheet C264/EN RS/B30

Maintenance C264/EN MF/B30

Lexical C264/EN LX/B30

C264/EN TG/B30 Technical Guide

Page 2/2 MiCOM C264/C264C

BLANK PAGE
Safety & Handling C264/EN SA/B30

MiCOM C264/C264C

SAFETY & HANDLING

Safety & Handling C264/EN SA/B30

MiCOM C264/C264C Page 1/12

CONTENT

1. INTRODUCTION 3

2. SAFETY 4
2.1 Health and Safety 4
2.2 Earth 4
2.3 Installing, Commissioning and Servicing 4

3. DECOMMISSIONING AND DISPOSAL 6

4. SPECIFICATIONS ON DEVICE/PEOPLE PROTECTION 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 AREVA T&D PRODUCTS 12

C264/EN SA/B30 Safety & Handling

Page 2/12 MiCOM C264/C264C

BLANK PAGE
Safety & Handling C264/EN SA/B30

MiCOM C264/C264C Page 3/12

1. INTRODUCTION
This document is a chapter of the MiCOM C264/C264C documentation binder. It describes
the safety, handling, packing and unpacking procedures applicable to MiCOM C264/C264C
modular computer series and associated equipment's and software tools.
C264/EN SA/B30 Safety & Handling

Page 4/12 MiCOM C264/C264C

2. SAFETY
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 Earth
The term earth used throughout the product documentation is the direct equivalent of the
North American term ground.
2.3 Installing, Commissioning and Servicing
Equipment connections
Personnel undertaking installation, commissioning or servicing work on this equipment
should be aware of the correct working procedures to ensure safety. The product
documentation should be consulted before installing, commissioning or servicing the
equipment.
Terminals exposed during installation, commissioning and maintenance may present a
hazardous voltage unless the equipment is electrically isolated.
If there is unlocked access to the rear of the equipment, care should be taken by all
personnel to avoid electrical shock or energy hazards.
Voltage and current connections should be made using insulated crimp terminations to
ensure that terminal block insulation requirements are maintained for safety. To ensure that
wires are correctly terminated the correct crimp terminal and tool for the wire size should be
used.
Before energising the equipment it must be earthed using the protective earth terminal, or
the appropriate termination of the supply plug in the case of plug connected equipment.
Omitting or disconnecting the equipment earth may cause a safety hazard.
The recommended minimum earth wire size is 2.5mm², unless otherwise stated in the
technical data section of the product documentation.
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)

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.
External resistors
Where external resistors are fitted to MiCOM computers, these may present a risk of electric
shock or burns, if touched.
Safety & Handling C264/EN SA/B30

MiCOM C264/C264C Page 5/12

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.
C264/EN SA/B30 Safety & Handling

Page 6/12 MiCOM C264/C264C

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.
Safety & Handling C264/EN SA/B30

MiCOM C264/C264C Page 7/12

4. SPECIFICATIONS ON DEVICE/PEOPLE PROTECTION

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.
C264/EN SA/B30 Safety & Handling

Page 8/12 MiCOM C264/C264C

5. HANDLING OF ELECTRONIC EQUIPMENTS

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

MiCOM C264/C264C Page 9/12

6. PACKING AND UNPACKING

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

Page 10/12 MiCOM C264/C264C

7. GUARANTIES
The media on which you received AREVA T&D software are guaranteed not to fail executing
programming instructions, due to defects in materials and workmanship, for a period of 90
days from date of shipment, as evidenced by receipts or other documentation. AREVA T&D
will, at its option, repair or replace software media that do not execute programming
instructions if AREVA T&D receive notice of such defects during the guaranty period.
AREVA 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 guaranty 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, AREVA 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 guaranties, express or implied and
specifically disclaims and guaranties of merchantability or fitness for a particular purpose.
Customer's rights to recover damages caused by fault or negligence on the part AREVA
T&D 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. AREVA T&D shall not be liable for any delay in performance
due to causes beyond its reasonable control. The warranty provided herein does not cover
damages, defects, malfunctions, or service failures caused by owner's failure to follow the
AREVA T&D 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.
Safety & Handling C264/EN SA/B30

MiCOM C264/C264C Page 11/12

8. COPYRIGHTS & TRADEMARKS

8.1 Copyrights
Under the copyright laws, this publication may not be reproduced or transmitted in any form,
electronic or mechanical, including photocopying, recording, storing in an information
retrieval system, or translating, in whole or in part, without the prior written consent of
AREVA T&D.
8.2 Trademarks
PACiS, PACiS SCE, PACiS ES, PACiS CMT, 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.
C264/EN SA/B30 Safety & Handling

Page 12/12 MiCOM C264/C264C

9. WARNINGS REGARDING USE OF AREVA T&D PRODUCTS

AREVA T&D products are not designed with components and testing for a level of reliability
suitable for use in connection with surgical implants or as critical components in any life
support systems whose failure to perform can reasonably be expected to cause significant
injuries to a human.
In any application, including the above reliability of operation of the software products can be
impaired by adverse factors, including - but not limited - to fluctuations in electrical power
supply, computer hardware malfunctions, computer operating system, software fitness,
fitness of compilers and development software used to develop an application, installation
errors, software and hardware compatibility problems, malfunctions or failures of electronic
monitoring or control devices, transient failures of electronic systems (hardware and/or
software), unanticipated uses or misuses, or errors from the user or applications designer
(adverse factors such as these are collectively termed "System failures").
Any application where a system failure would create a risk of harm to property or persons
(including the risk of bodily injuries and death) should not be reliant solely upon one form of
electronic system due to the risk of system failure to avoid damage, injury or death, the user
or application designer must take reasonably steps to protect against system failure,
including - but not limited - to back-up or shut-down mechanisms, not because end-user
system is customised and differs from AREVA T&D testing platforms but also a user or
application designer may use AREVA 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.
Introduction C264/EN IT/B30

MiCOM C264/C264C

INTRODUCTION
Introduction C264/EN IT/B30

MiCOM C264/C264C Page 1/8

CONTENT

1. INTRODUCTION TO MiCOM 3

2. INTRODUCTION TO MiCOM GUIDES 4

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

3. INTRODUCTION TO MiCOM APPLICATIONS 6

3.1 MiCOM Computers 6
3.2 Applications and Scope 6
C264/EN IT/B30 Introduction

Page 2/8 MiCOM C264/C264C

BLANK PAGE
Introduction C264/EN IT/B30

MiCOM C264/C264C Page 3/8

1. INTRODUCTION TO MiCOM
MiCOM is a comprehensive solution capable of meeting all electricity supply requirements. It
comprises a range of components, systems and services from AREVA T&D Energy
Automation & Information.
Central to the MiCOM concept is flexibility.
MiCOM provides the ability to define an application solution and, through extensive
communication capabilities, to integrate it with your power supply control system.
The components within MiCOM are:

• P range protection relays;

• C range control products;

• M range measurement products for accurate metering and monitoring;

• S range versatile PC support and substation control packages.

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
C264/EN IT/B30 Introduction

Page 4/8 MiCOM C264/C264C

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
C264/C264C computer.
2.1 Chapters description
2.1.1 Chapter Safety (SA)
This chapter contains the safety instructions, handling and reception of electronic equipment,
packing and unpacking parts, Copyrights and Trademarks.
Chapters on product definition and characteristics
2.1.2 Chapter Introduction (IT)
This is this document containing the description of each chapter of the MiCOM computer
guides. It is a brief introduction to MiCOM computer capabilities.
2.1.3 Chapter Technical Data (TD)
This chapter contains the technical data including, accuracy limits, recommended operating
conditions, ratings and performance data.
It also describes environment specification, compliance with technical standards.
2.1.4 Chapter Functional Description (FT)
This chapter contains a description of the product. It describes functions of the MiCOM
computer.
2.1.5 Chapter Hardware Description (HW)
This chapter contains the hardware product description (product identification, case,
electronic boards, operator interface, etc.).
2.1.6 Chapter Connection diagrams (CO)
This chapter contains the external wiring connections to the C264/C264C computers.
2.1.7 Chapter HMI, Local control and user interface (HI)
This chapter contains the operator interface description, Menu tree organisation and
navigation, LEDs description, Setting/configuration software.
Set of chapter upon Computer installation
2.1.8 Chapter Installation (IN)
This chapter contains the installation procedures.
2.1.9 Chapter Settings (ST)
This chapter contains the list of the setting with default values and range.
Introduction C264/EN IT/B30

MiCOM C264/C264C Page 5/8

2.1.10 Chapter Communications (CT)

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

Page 6/8 MiCOM C264/C264C

3. INTRODUCTION TO MiCOM APPLICATIONS

AREVA philosophy is to provide a range of computers, gateways and IEDs products. Each of
these products can be used independently, or can be integrated to form a PACiS system, a
Digital Control System (DCS) or a SCADA system.
3.1 MiCOM Computers
Driven by the requirements around the world for advanced applications in SCADA, Digital
Control Systems, Automation, control and monitoring, AREVA has designed and developed
a complete range of computer products, MiCOM C264 specifically for the power process
environment and electric utility industry. It allows building a personalised solution for Control,
Monitoring, Measurement and Automation of electrical processes.
MiCOM C264/C264C computers range are designed to address the needs of a wide range
of installations, from small to large and customer applications. Emphasis has been placed on
strong compliance to standards, scalability, modularity and openness architecture. These
facilitate use in a range of applications from the most basic to the most demanding. They
also ensure interoperability with existing components and, by providing building computers,
PLC or IEDs approach, provide a comprehensive upgrade path, which allows PACiS
capabilities to track customer requirements.
Key features are that this computer family is based on a Ethernet client/server architecture,
its a modular computer that offers a large variety of applications such as Bay Computer,
Remote Terminal Unit and Programmable Logic Controller.
Phase in time, dedicated computer available for each application will be purposed.
3.2 Applications and Scope
The MiCOM C264/C264C modular bay controller, RTU or PLC is used to control and monitor
switchbays. The information capacity of the MiCOM C264/C264C is designed for controlling
operated switchgear units equipped with electrical check-back signalling located in medium-
voltage or high-voltage substations.
External auxiliary devices are largely obviated by the integration of binary inputs and power
outputs that are independent of auxiliary voltages, by the direct connection option for current
and voltage transformers, and by the comprehensive interlocking capability.
This simplifies handling of bay protection and control technology from planning to station
commissioning. During operation, the user-friendly interface makes it easy to set the unit and
allows safe operation of the substation by preventing non-permissible switching operations.
Continuous self-monitoring reduces maintenance costs for protection and control systems.
A built-in liquid crystal display (optional front face with LCD) shows not only switchgear
settings but also measured data and monitoring signals or indications.
The bay is controlled interactively by using the control keys and the display.
Adjustment to the quantity of information required is made via the PACiS System
Configurator Editor (PACiS SCE).
The MiCOM C264/C264C can be connected to a higher control level, local control level or
lower levels by way of a built-in communications interface.
Introduction C264/EN IT/B30

MiCOM C264/C264C Page 7/8

C264C WEB access

SCADA Interface
DNP3 & IEC 60870-5-101
& IEC 60870-5-104

Master clock
(GPS)
Operator
Interface

HV EEDER BAY
Fast Ethernet
UCA2
C264

C264C
Main p on
EHV FEE BAY

I/Os
C264

MV FEE ER AYS
CO AY

Cubicle/Switchboard MV FE DE BAYS
TRANS OR ER AY integration
C0001ENb

FIGURE 1 : TYPICAL USE OF A MiCOM C264 – BAY CONTROLLER

PSTN or Remote
SCADA Interface
dedicated HMI
DNP3 & IEC 60870-5-101
line
& IEC 60870-5-104

Px30
Px40

NP3,
DBUS,
M720 IE 0-5-103,
I 870-5-101

Px20
Px30

PLC
BC

I/Os
I/Os
C0002ENb

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

The figures show some typical cases that can be mixed to face specific constraint. Two
examples can illustrate this case:

• The system application on “figure 1” uses several C264 with several communication
links to SCADA (one per voltage level for example).

• RTU application can use several C264 linked together on SBUS Ethernet. One of the
C264 RTUs is in charge of the concentration of data and of the communication with
the remote SCADA.
C264/EN IT/B30 Introduction

Page 8/8 MiCOM C264/C264C

BLANK PAGE
Technical Data C264/EN TD/B30

MiCOM C264/C264C

TECHNICAL DATA
Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 1/20

CONTENT

1. SCOPE OF THE DOCUMENT 3

2. CONFORMITY 4

3. GENERAL DATA 5
3.1 Design 5
3.2 Installation Position 5
3.3 Degree of Protection 5
3.4 Weight 5
3.5 Dimensions and Connections 5
3.6 Terminals 5
3.7 Creepage Distances and Clearances 6

4. RATINGS 7
4.1 Auxiliary Voltage 7
4.2 Digital inputs 7
4.2.1 DIU200 7
4.2.2 DIU210 8
4.2.3 CCU200 9
4.3 Digital outputs 10
4.3.1 DOU200 10
4.3.2 CCU200 10
4.3.3 BIU241 11
4.4 Analogue inputs 11
4.5 CT/VT inputs 12
4.5.1 Currents 12
4.5.2 Voltages 13
4.5.3 A/D converter 13

5. BURDENS 14
5.1 Auxiliary Voltage 14
5.2 Power supply 14
5.3 CPU board 14
5.4 Digital inputs 14
5.4.1 DIU200 14
5.4.2 DIU210 14
5.5 Digital outputs 15
5.5.1 DOU200 15
5.5.2 CCU200 15
C264/EN TD/B30 Technical Data

Page 2/20 MiCOM C264/C264C

5.6 Analogue inputs 15

5.7 Ethernet Switches 15
5.8 CT / VT inputs 15
5.9 Front panels 15

6. ACCURACY 16
6.1 Reference Conditions 16
6.2 Measurement Accuracy 16

7. TYPE TESTS 17
7.1 Dielectric Withstand 17
7.2 Mechanical Test 17
7.3 Atmospheric Test 18
7.4 “DC” Auxiliary Supply Test 18
7.5 “AC” Auxiliary Supply Test 19
7.6 EMC 19
Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 3/20

1. SCOPE OF THE DOCUMENT

This document is a chapter of MiCOM C264 documentation binders, describing the
Technical data of this computer.
C264/EN TD/B30 Technical Data

Page 4/20 MiCOM C264/C264C

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.
Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 5/20

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

Page 6/20 MiCOM C264/C264C

Current-measuring and Voltage-measuring inputs:

M5 threaded terminal ends, self-centring with wire protection for conductor cross sections
between 2.5 and 4 mm² for TMU200 Transducerless (4CT+4VT) board.
The TMU200 (4CT+4VT) board is equipped with a “MiCOM: ASSEMBLY CONNECTEUR
BLOCKL GJ104” connector.
3.7 Creepage Distances and Clearances
Per EN 61010-1 and IEC 664-1.
Pollution degree 3, working voltage 250 V.
Overvoltage category III, impulse test voltage 5 kV.
Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 7/20

4. RATINGS
4.1 Auxiliary Voltage
MiCOM C264/C264C computers are available in four auxiliary voltage versions, specified in
the table below:

Version Nominal ranges Operative DC range Operative AC range

A01 24 VDC 19.2 – 28.8 V -
A02 48 to 60 VDC 38.4 – 72 V -
A03 110 to 125 VDC 88 – 150 V -
A04 220 VDC and VAC 176 – 264 V 176 – 264 V

The nominal frequency (Fn) for the AC auxiliary voltage is dual rated at 50/60Hz, the operate
range is 45Hz to 65Hz.

The main characteristics of the BIU241 board are:

• Power supply: 40 W

• Nominal output voltage: + 5V

• Supply monitoring

• Power loss withstands capacity: 50 ms

• Protection against polarity reversal

• Insulation resistance: >100 MΩ ( CM) at 500 VDC

• Dielectric withstand: 2 kV (CM) – 50 Hz during 1min

4.2 Digital inputs
4.2.1 DIU200
The DIU200 board is available in four nominal voltage versions that characteristics are
specified in the table below.
The DIU200 board has 16 digital inputs..

Version Nominal voltage (+/-20%) Triggering threshold (VDC)

A01 24 VDC if V >10 .1VDC Input is set
A02 48 to 60 VDC if V >17.4 VDC Input is set
A03 110 to 125 VDC if V > 50 VDC Input is set
A04 220 VDC if V > 108 VDC Input is set
C264/EN TD/B30 Technical Data

Page 8/20 MiCOM C264/C264C

The DIU200 board is designed to allow 2 inputs serially connected. This answers to the
following need:

Un

IN1 IN2

C264

0 VDC C0124ENa

If R is open then IN1 and IN2 are set.

If R is closed then IN1 is set, IN2 is reset.
With this scheme, when IN1 is reset, this means that there is a problem into the external
wiring.
The input current at nominal voltage is detailed in chapter 5.4.
There are at maximum 15 DIU boards (including DIU200 and DIU210) inside a C264 rack.
4.2.2 DIU210
The DIU210 board works for all voltages between 24V and 220 DC (+/- 20%)
The DIU210 board has 16 digital inputs.
Whichever voltage, the triggering threshold is 19VDC
The maximum number of DIU210 board in one C264 rack depend on the rack type and on
the voltage level of inputs.
Please refer to the following table :

Maximum Maximum
DIU210 boards in 40TE racks DIU210 boards in 80TE racks
24V 2 8
48V 6 15
110-125V 3 10
>=220V 1 5
Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 9/20

The DIU210 board is designed to allow 2 inputs serially connected. This answers to the
following need:

Un

IN1 IN2

C264

0 VDC C0124ENa

If R is open then IN1 and IN2 are set.

If R is closed then IN1 is set, IN2 is reset.
With this scheme, when IN1 is reset, this means that there is a problem into the external
wiring.
The input current at nominal voltage is detailed in chapter 5.4.
There are at maximum 15 DIU boards (including DIU200 and DIU210) inside a C264 rack.

4.2.3 CCU200

The characteristics of the 8 inputs of CCU200 board are the same as the DIU200 board.
There are at maximum 15 CCU200 boards inside a C264 rack.
C264/EN TD/B30 Technical Data

Page 10/20 MiCOM C264/C264C

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
Operating voltage 24 to 250 VDC / 230 VAC
Make 2,5A
Carry 2,5A continuous
30 A for 500 ms or 100 A for 30 ms
Break DC: 50 W resistive, 15 W inductive (L/R = 20 ms)
AC : 1250 VA resistive, 1250 VA inductive (cosϕ = 0,7)
In these conditions, the contact resistance is still lower
than 250 mΩ for 10000 operations
Operating time Break < 7 ms
8 simple pole contacts Normally open
2 double pole contacts 1 Normally open +1 Normally close

• Isolation: 2 kV – 50 Hz (CM)

• The board is designed and monitored to avoid inadvertent controls.

• There are at maximum 15 DOU200 boards inside a C264 rack..

4.3.2 CCU200
The characteristics of the 4 Output Relay Contacts of the CCU200 board are specified in the
table below:
Each relay of the CCU board has double pole contacts. To get the characteristics described
below, the two output contacts of each relay are to be wired in serial.

Features Values
Operating voltage 24 to 250 VDC / 230 VAC
Make 5A
Carry 5A continuous
30 A for 500 ms or 250 A for 30 ms
Break DC : 100 W resistive, 30 W inductive (L/R = 40 ms)
AC : 1250 VA resistive, 1250 VA inductive (cosϕ = 0,7)
In these conditions, the contact resistance is still lower
than 250 mΩ for 10000 operations
Operating time Break < 7 ms
Double pole contacts Normally open

• Isolation: 2 kV – 50 Hz (CM)

• The board is designed and monitored to avoid inadvertent controls..

• There are at maximum 15 CCU200 boards inside a C264 rack..

Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 11/20

4.3.3 BIU241

The characteristics of the Watchdog Relay Contacts of the BIU241 board are the same as
the contacts “NO+NC” contacts of the DOU200 board.

The characteristics of the two output relays used for C264 redundancy are the same as the
single pole one on the DOU200 board.
4.4 Analogue inputs
The AIU201 board provides 4 independent analogue inputs. Each AI can be configured in
voltage or current range individually as specified in the table below:

Type Ranges
Current input range ±1mA
±2,5 mA
±5 mA
±10 mA
±20 mA
4-20 mA
Voltage input range ± 1,25V
±2,5V
±5V
± 10V
Sampling period 100 ms
Accuracy 0,1% full scale at 25°C
AD conversion 16 bit
Common mode rejection ratio (CMMR) > 100dB
Serial mode rejection ratio (SMMR) > 40dB
gains range (user-selectable) 1, 2, 4, 10
Input impedance for voltage inputs 11 KΩ
Input impedance for current inputs 75 Ω

The ranges are configures by software (PACiS configurator).

The current/voltage selection is done by choosing the input number of the connector.
There are at maximum 6 AIU boards (including AIU201 and AIU210) inside a C264 rack.
C264/EN TD/B30 Technical Data

Page 12/20 MiCOM C264/C264C

The AIU210 board provides 8 independent analogue inputs. Each AI can be configured in
current range only as specified in the table below:

Type Ranges
Current input range ±1mA
±2,5 mA
±5 mA
±10 mA
±20 mA
4-20 mA
Sampling period 100 ms
Accuracy 0,1% full scale at 25°C
AD conversion 16 bit
Common mode rejection ratio (CMMR) > 100dB
Serial mode rejection ratio (SMMR) > 40dB
gains range (user-selectable) 1, 2, 4, 10
Input impedance for current inputs 75 Ω

The ranges are configures by software (PACiS configurator).

The current selection is done by choosing the input number of the connector.
There are at maximum 6 AIU boards (including AIU201 and AIU210) inside a C264 rack.

4.5 CT/VT inputs

4.5.1 Currents
There are two available nominal currents with two different allocations on the terminal block.
The four measurement Current Transformers (4 CT) inputs have the following
characteristics:

Operating range
Features
1A 5A
Nominal AC current (IN) 1 Aeff 5 Aeff
Minimum measurable current with same 0.2 Aeff 0.2 Aeff
accuracy
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, without 6 Aeff 30 Aeff
destruction)
1 second (not measurable, without 20 Aeff 100 Aeff
destruction)
Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 13/20

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 7 Veff
Maximum measurable voltage 577 Veff
Frequency operating range 50 or 60 Hz ± 10%

VT load rating:

Duration Withstand
10 second 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 up to 1khz 0db
Low passed filter at 1khz -40db/decade
C264/EN TD/B30 Technical Data

Page 14/20 MiCOM C264/C264C

5. BURDENS
5.1 Auxiliary Voltage
The MiCOM C264/C264C computer burdens are specified in the table below:

Version Nominal Maximum

C264C 15W 22W
C264 20W 40W

5.2 Power supply

The BIU241 board burden on the internal 5V bus is 1,25W. This takes into account
watchdog, redundancy relays and communication ports.
The efficiency of the power supply is 78%.
5.3 CPU board
The CPU200 board burden on the internal 5V and 12V bus is 3,3W.

5.4 Digital inputs

5.4.1 DIU200
The DIU200 board burdens are specified in the table below:

Version Nominal wetting voltage Current at Un (mA)

A01 24 VDC 3.5
A02 48 to 60 VDC 5 for 48 VDC
6.8 for 60 VDC
A03 110 to 125 VDC 2.5 for110 VDC
3 for 125 VDC
A04 220 VDC 2

The DIU200 board burden on the internal 5V bus is 75mW.

5.4.2 DIU210
The DIU210 board burdens are specified in the table below:

Nominal wetting voltage Current at Un (mA)

24 VDC >25
48 to 60 VDC 3.8
110 to 125 VDC 4
220 VDC 4.1

The DIU210 board burden on the internal 5V bus is 75Mw.

Power consumption per input :
Un = 24V to 110V DC : 0,5W ± 30% per input
Un > 110V : 5mA ± 30%
From 48V to 220Vdc wetting voltage, a high current consumption is created on binary inputs
during a short period and circulates through external binary contacts to clean them. See the
peak current response curve.
WARNING : FOR THE 24V WETTING VOLTAGE, THERE IS NO SHORT PEAK
CURRENT BECAUSE OF THE PERMANENT HIGH CONSUMPTION ON
INPUTS >25mA.
Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 15/20

The current peak response curve.

35

30

25
Current (mA) 20

15

10

0
0 50 100 150 200 250 300
Tension (V)
C0159ENa

5.5 Digital outputs

5.5.1 DOU200
The DOU200 board burden on the internal 5V bus is 250mW plus 200mW per activated
relay.
5.5.2 CCU200
The CCU200 board burden on the internal 5V bus is 400mW plus 200mW per activated
relay.

5.6 Analogue inputs

The AIU201 and the AIU210 boards burden on the internal 5V bus is 1 W.

5.7 Ethernet Switches

The SWU200 board burden on the internal 5V bus is 3,85W with 2 optical ports.
The SWR200 board burden on the internal 5V bus is 4 W.
5.8 CT / VT inputs
The TMU200 burdens on inside transformers are specified in the table below:

CT burden (at nominal current – IN) Nominal consumption (VA)

1A <0.1
5A <0.5

VT burden (at nominal voltage – VN ) Nominal consumption (VA)

Vn = 130 Veff <0.1

The TMU200 board burden on the internal 5V bus is 600mW

5.9 Front panels
The GHU200 and GHU210 board burden on the internal 5V bus is 600mW when the LCD
screen is not back-lighted and 3W when the LCD screen is back-lighted.
The GHU201 and GHU211 board burden on the internal 5V bus is 600mW.
The GHU202 and GHU212 board burden on the internal 5V bus is <1mW.
C264/EN TD/B30 Technical Data

Page 16/20 MiCOM C264/C264C

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, 110V or 220V ±5%
AC 220V

6.2 Measurement Accuracy

The TMU200 board has the following characteristics:

Quantity Accuracy
Current 0.2% full scale
Voltage 0.2% full scale
Frequency ± 0.01 Hz
Amplitude < 1%
Phase ± 1°
Overall temperature coefficient ± 10 ppm/°C
Harmonics 15H
Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 17/20

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 IEC 60255-5 5 kV CM & 3 kV DM
Test

7.2 Mechanical Test

Type Test Name Type Test Standard Conditions

Free Fall Test IEC 60068-2-31 2 falls of 5 cm (Computer not powered)
Free Fall Packaging IEC 60068-2-32
Test
25 falls of 50 cm (Packaging computer)
Vibration Response – IEC 60255-21-1 Class 2:
Powered On
Acceleration: 1g from 10 to 150Hz
Vibration Response – IEC 60255-21-1 Class 2:
Not Powered On
Acceleration: 2g from 10 to 500Hz
Vibration Endurance – IEC 60068-2-6 Class 2:
Not Powered On
Acceleration: 1g from 10 to 500Hz
Shocks – Not Powered IEC 60255-21-2 Class 1:
On
15g, 11 ms
Shocks – Powered On IEC 60255-21-2 Class 2:
10g, 11 ms
Bump Test – Not IEC 60255-21-2 Class 1:
Powered On
10g, 16ms, 2000/axis
Seismic Test – Powered IEC 60255-21-3 Class 2:
On
Acceleration: 2g
Displacement: 7.5mm upon axe H
Acceleration: 1g
Displacement: 3.5mm upon axe V
C264/EN TD/B30 Technical Data

Page 18/20 MiCOM C264/C264C

7.3 Atmospheric Test

Type Test Name Type Test Standard Conditions

Damp Heat Test – IEC 60068-2-3 Test Ca:
Operating
+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)
Dry Heat Test – IEC 60068-2-2 70°c / 24 H
Operating

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

Type Test Name Type Test Standard Conditions

Inrush current (start-up) DICOT HN 46-R01-4 T < 1.5 ms / I < 20 A
1.5ms < 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
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
Technical Data C264/EN TD/B30

MiCOM C264/C264C Page 19/20

7.5 “AC” Auxiliary Supply Test

Type Test Name Type Test Standard Conditions

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

Type Test Name Type Test Standard Conditions

High Frequency IEC 60255-22-1 Class 3: 2.5kV (CM) / 1kV (DM)
Disturbance
IEC 61000-4-12
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 MHz
IEEE C37.90.2 & spot tests
35 V/m – 25 to 1000 MHz
Fast Transient Burst IEC 60255-22-4 Class 4: 4kV – 2.5kHz (CM)
IEC 61000-4-4 Class 4: 2.5kV – 2.5kHz (DM) on DI/DO
IEEE C37.90.1
Surge immunity IEC 61000-4-5 Class 4:
4kV (CM) – 2kV (DM)
High frequency IEC 61000-4-6 Class 3:
conducted immunity
10 V, 0.15 – 80 MHz
Harmonics Immunity IEC 61000-4-7 5% & 10% de H2 à H17
Power Frequency IEC 61000-4-8 Class 5:
Magnetic 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 IEC 61000-4-10 Class 5:
magnetic 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
C264/EN TD/B30 Technical Data

Page 20/20 MiCOM C264/C264C

BLANK PAGE
Functional Description C264/EN FT/B30

MiCOM C264/C264C

FUNCTIONAL DESCRIPTION
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 1/46

CONTENT

1. SCOPE OF THE DOCUMENT 5

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 9
3.3 Self tests 9
3.4 Time management 9
3.4.1 External clock 10
3.4.2 Clock message from a SCADA gateway 10
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 Legacy bus 12
4.3 Station bus 12
4.3.1 Exchanges 13
4.3.2 Supported Common Class 13
4.3.3 Controls 13

5. DIRECT PROCESS ACCESS 14

5.1 Digital input acquisition (DI) 14
5.1.1 Acquisition 14
5.1.2 Debouncing and filtering 14
5.1.3 Toggling 15
5.2 Counters acquisition (CT) 15
5.2.1 Single counter (SCT) 15
5.2.2 Double counter (DCT) 16
5.3 Digital measurement (DM) 16
5.3.1 Acquisition without RI 17
5.3.2 Acquisition with RI 18
5.3.3 Encoding 18
C264/EN FT/B30 Functional Description

Page 2/46 MiCOM C264/C264C

5.4 Analogue input acquisition (AI) 18

5.5 Digital outputs (DO) 18
5.6 Digital Setpoints 19
5.6.1 Encoding 19
5.6.2 Read Inhibit 19

6. DATA PROCESSING 20
6.1 Binary Input Processing 20
6.1.1 Binary Input Definition 20
6.1.2 Processing of Single Point Status 21
6.1.3 Processing of Double Point Status 22
6.1.4 Group processing 23
6.2 Processing of Multi Point Status 23
6.3 Measurement Input Processing 24
6.3.1 Analogue processing 24
6.3.2 CT/VT additional processing 25
6.3.3 Digital Measurement Processing 25
6.4 Accumulator Input Processing 25

7. CONTROL SEQUENCES 26
7.1 Kind of control sequences 26
7.2 Control sequences checks 26
7.2.1 Mode Management 26
7.2.2 IED connected 26
7.2.3 Control mode 27
7.2.4 Uniqueness of control 27
7.2.5 Inter-control delay 27
7.2.6 Status of the device 27
7.2.7 Lock device 27
7.2.8 Running Automation 27
7.2.9 Interlocking 27
7.3 HV Control Sequences 28
7.3.1 Circuit breaker 28
7.3.2 Disconnector 28
7.3.3 Transformer 28
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 3/46

8. AUTOMATIONS 29
8.1 Build-in Automation functions 29
8.1.1 Synchrocheck 29
8.1.2 Auto-Recloser (AR) 31
8.1.3 Trip Circuit supervision 32
8.1.4 Automatic Voltage Regulation (AVR) 33
8.2 Fast automation (PSL) 35
8.3 PLC automation 36

9. USER INTERFACE 37
9.1 Front Panel 37
9.1.1 Local Control Display 38
9.1.2 Local/Remote push-button 38
9.2 Computer Maintenance Tool 38
9.3 Printer 39
9.3.1 Inputs 39
9.3.2 Outputs 39
9.3.3 Printer management 40

10. RECORDS 42
10.1 Permanent records storage 42
10.1.1 Data storage 42
10.1.2 Waveform Recording 42
10.1.3 Events 44
10.2 Non-permanent data storage 45
10.2.1 Alarm function 45
C264/EN FT/B30 Functional Description

Page 4/46 MiCOM C264/C264C

BLANK PAGE
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 5/46

1. SCOPE OF THE DOCUMENT

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

• High communication abilities to IED, Ethernet, and RTU

• User configurable automation modules

• Events, alarms, measurement display, printing and archiving

• Enhanced inner management with databases handling, self-test controls and

synchronisation means

RTU, SCADA PACiS System, 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

C264/EN FT/B30 Functional Description

Page 6/46 MiCOM C264/C264C

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)

Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 7/46

2. DIRECT PROCESS INTERFACE

Several kind of boards can be used in MiCOM C264/C264C. Digital Input & Outputs,
Measurement acquisitions are checked to validate information/action and time tagged on any
change of state or value.
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 these data is internally
fixed for:

• Self-test (DI, AI, board self test failure),

• Unknown (DI, AI, communication failure to remote acquisition like IED)

• Toggling (DI, X change of state in given time)

• Over-range (AI, saturation of its transducer, or Counter value reaching limits)

• Open Circuit (AI kind 4-20 mA with current value under 4mA)

• Undefined (Digital Measurement or Counter with invalid DI coding)

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
refused.
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.
Information coming from IED are time tagged by IED itself if it has this facility otherwise it is
performed at C264 level when receiving the data.
C264/EN FT/B30 Functional Description

Page 8/46 MiCOM C264/C264C

3. MiCOM C264/C264C MANAGEMENT

The computer manages its own mode, configuration (Databases), 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 refused (this
mode is linked to computer redundancy management). In this mode there is no
communication with IED or SCADA
Maintenance: operator has requested this mode to switch databases. Only functions
needed for database or operating mode management are available.
Faulty: the computer has detected a major self test failure, it has the same behaviour as in
maintenance mode.
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 database.
The 2 redundant computers are the Main and the Backup one. The computer that performs
the bay(s) management is the Active one; the other one is the Standby one. So, a
redundant computer can be Main Active, Main Standby, Backup Active and Backup Standby.
The two computers perform simultaneously the same functions (inputs acquisition and
processing, archiving, automation), but at a given time, only the Active one send controls
to the electrical process or on the Station Bus. A PACiS UCA2 client receives information
from the 2 computers: so, a dedicated mechanism allows to process only information
received from the Active one. Only the Active computer manages communication with IED or
SCADA.
This switchover from the Active to the Standby (and vice-versa) is performed automatically
according to following features.

Station Bus

MAIN BACKUP
COMPUTER COMPUTER
DI2 DO2 DI1 DO1 DI1 DO1 DI2 DO2

Active State Control/Indication

UCA2 client State Control/Indication

C0125ENa
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 9/46

The computers exchange information using:

The Station Bus, to give their internal status (IS)
2 couples of DI/DO:

• DI1/DO1 to indicate the Active Status : DO1 is closed if the computer is Active,

• DI2/DO2 to indicate a Station Bus failure : DO2 is open in case of failure

These DI/DO are wired on BIU board.
A value is given to each type of computer failure: the computer IS is calculated by summing
all defaults. The healthiest computer is the one with the minimal internal status. The
healthiest computer is active.

Computer failure Value

DOU board failure 0x20
CCU board failure 0x10
CT/VT board failure 0x08
DIU board failure 0x04
BIU board failure 0x02
AIU board failure 0x01

3.2 Database management

The MiCOM C264 uses structured databases for data management. 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 database versions. A standby database can be downloaded even if computer is
operational using PACiS SMT (System Management Tool) or PACiS CMT (Computer
Maintenance Tool).
A switch database control from SMT or CMT allows changing of the current database. The
computer will restart to take into account the new structured data. A fundamental principle is
that the computer can only work with an other PACIS equipment if their current database
versions are identical.
3.3 Self tests
Computer makes self-checks:

• Hardware (hardware fault) at start-up and cyclically.

• Software (software fault) cyclically to check that software tasks are alive and not take
all the CPU time.

• Database coherency at start-up.

• Acquisition and output at start-up and cyclically.

3.4 Time management
The computer Real Time Clock has small drift per day, therefore the operator should set its
time periodically or it should be synchronised to a master clock.
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)

C264/EN FT/B30 Functional Description

Page 10/46 MiCOM C264/C264C

When computer is synchronised all events and measurement have a time tag with
synchronised attribute. If synchronisation is lost, or has never been received attributes
indicates that time tag is not synchronised.
The time management organisation is based on the following scheme:

Synchronisation signal

External clock SCADA

Which Which synchronises

synchronises through SCADA bus
System Master
Clock

Which synchronises Operator

through station bus time setting

UCA2
equipment

Which synchronises
through legacy bus

IEDs

C0004ENb

FIGURE 2 : TIME MANAGEMENT

3.4.1 External clock
The external clock device receives the synchronisation signal through several possible
protocols (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 depends on protocol. The synchronisation message is directly
acquires by the MiCOM C264/C264C through the SCADA link.
3.4.3 System master clock
In a PACiS system, it is enough to externally synchronise one MiCOM C264/C264C. This
computer is identified as Master Clock and synchronises all other equipments on station bus.
3.4.4 Time set by an operator
The user may set time and date directly using the MiCOM C264/C264C local Operator
Interface or the CMT tool.
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 11/46

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

Computer Kernel

Legacy Gateway I/O boards

L-Bus

IED
C0005ENb

FIGURE 3 : COMMUNICATIONS
4.1 Telecontrol bus
The available slave protocols are:

• IEC 60870-5-101 (T101),

• IEC 60870-5-104 (T104),

• DNP3.0

• DNP3 over IP

• MODBUS
MiCOM C264/C264C behaves as a slave into master/slave protocol (DNP3.0, T101, DNP3
over IP, MODBUS) or balanced protocol (T101, T104).
The connection with SCADA is direct or via modem.
Physical layer:

• T101, DNP3.0, MODBUS: RS232, RS422, RS485

• T104, DNP3 over IP: Ethernet 10 or 100 Mb/s: RJ45 connector or optical fibre
(multimode or monomode)
Up to two protocols can be configured, same protocol or not, with or without redundant
channels. The C264 computers have up to four serial ports. Be careful, for the CPU, the
baudrate must be the same on both serial ports.
The redundancy is not available for T104, DNP3 over IP and MODBUS.
C264/EN FT/B30 Functional Description

Page 12/46 MiCOM C264/C264C

4.2 Legacy bus

MiCOM C264/C264C behaves as a master.
Protocols:

• IEC 60870-5-103 (T103),

• IEC 60870-5-101 (T101),

• ModBus

• DNP3
Devices connected to: IEDs
Physical layer:

• RS232, RS422, RS485

• Optical fibber
Four serial ports are available to make four networks with different protocols or not.
For T103 and Modbus, a tunnelling mode is available. This allows a setting software running
on a personal computer to access the IEDs through the C264.
4.3 Station bus
The SBUS Protocol is used for PACiS subsystems communication but it is also available for
other equipment.
MiCOM C264/C264C behaves mainly as a server but it can be also a client of other C264
(distributed automations) or UCA2 IED.
Protocol:

• UCA2
Devices connected to:

• PACiS devices (OI, SMT, PACiS Gateway, CMT)

• Other MiCOM C264/C264C

• UCA2 IEDs
Link layer: Ethernet 10 or 100 Mb/s
Physical support:

• Copper twisted pair (RJ45 connector)

• Optical fibber (multimode or monomode)

The optical port is optional. To increase the number of Ethernet port, two Ethernet switch
boards are available:

• SWU with 4 RJ45 ports and up 2 optical ports (multimode or monomode)

• SWR with 4 RJ45 ports and 2 optical ports for a redundant ring (multimode or
monomode)
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 13/46

4.3.1 Exchanges
The MiCOM C264 acquires and sends data on Ethernet network using two mechanisms:

• REPORT

• GOOSE
The REPORT is specific between a server and one client, it provides:

• data value

• data state or quality attribute (validity and several kind of invalid state)

• time tag of last data value change

• time tag quality attribute (server synchronised or not when event occur)
Data quality defines if data is valid or several kind of invalidity: unknown when disconnected,
Saturated, Undefined… REPORTS are send/received with their RFI (Reason For Inclusion):
periodic, spontaneous state/value change or following control.
The GOOSE is a short message sent in multicast to all SBUS equipment, this is quicker than
Report, but only the data value is sent.
4.3.2 Supported Common Class
MiCOM C264 computer exchange data using Common Class. The following list gives
implemented ones:

Kind of information 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 (SBOCF)
Regulating step control Analogue Output (AO)
Setpoint control (CF) Configuration (CF)

TABLEAU 1 : DATA MANAGEMENT

4.3.3 Controls
MiCOM C264 supports Common Class control expressed with BO, DCO, and SBOCF.
Receiving control from Ethernet it manages protocol control termination (possibly with NACK
codes). The Bypass control is supported (through management of quality attributes).
C264/EN FT/B30 Functional Description

Page 14/46 MiCOM C264/C264C

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 and depend on their type.
5.1 Digital input acquisition (DI)
5.1.1 Acquisition
Acquisition of binary information is done via DIU200 (16 DIs) or CCU200 (8 DIs+4 DOs)
boards:

Debouncing & Toggle

Filtering for BI Filtering for To BI
BI treatment

Hardware Software Time Debouncing & Special

acquisition acquisition stamping Filtering for treatment To measurements
DM for DM treatment

Debouncing & Special

Filtering for treatment To counters
counters for treatment
counters

C0126ENa

5.1.2 Debouncing and filtering

A filtering is applied on digital inputs as follow:

Filtering time

Debouncing
time

t0 t1 t2
C0127ENa

t0 is the instant of detection of the first transition. t1 is the instant of validation of the change of
state. t2 is the end of the filtering. (the signal has remained stable from t1 to t2). The change of
state is time stamped at t0 .
A value of 0 means that no filter is applied : a change of state is validated as soon as it is
detected.
Three couple of delays (deboucing / filtering) are defined :

• one for all DI which will be used as BI

• one for all DI which will be used as DM

• one for all DI which will be used as counters

Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 15/46

5.1.3 Toggling
A digital input is said to be toggling if its state has changed more than N times in a given
period of time T1.
A toggling DI returns in the normal state if its state has not changed within another period of
time T2.
N, T1 and T2 are parameters determined at configuration time on a per system basis (same
parameters for all MiCOM computers of a system).
The toggle filtering applies only on DI that will be used as BI (there is no toggle filtering on DI
that will be used for counters or DM).
5.2 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 debouncing and filtering
values must be chosen in consequence.
5.2.1 Single counter (SCT)
A SCT is acquired on a single contact.
The value of the accumulator is incremented after a low to high transition, confirmed after a
filtering time (Tcount). Tcount is defined for the whole system, with a step of 5 ms : the chosen
value must be coherent with the pulse frequency (i.e. all counters of a system use the same
Tcount).
A subsequent pulse can be taken into account only after a high to low transition.

Tcount Tcount

Transition validated,
Low to high transition
counter is incremented

Transition discarded
Low to high transition
C0128ENa
C264/EN FT/B30 Functional Description

Page 16/46 MiCOM C264/C264C

5.2.2 Double counter (DCT)

A double counter is acquired on two contacts. One is called the true contact (TC), the other
is the complemented contact (CC). Normally these contacts should have complementary
states.
Pulses are detected in the same manner as for SCT, on the TC variations, using the Tcount
delay (the same Tcount value is used for SCT and DCT).
A subsequent pulse can be taken into account only after a high to low transition on TC (and
so a low to high transition on CC).
The difference is that both contacts should be in opposite states for transitions to be
detected and validated. The counter is invalid if it exists a non-complementarity between the
2 contacts during a delay Tdef. This delay is defined for the whole system (i.e. all DCT use the
same delay).

Tcount Tcount Tdef

TC

CC

Low to high transition Low to high transition, but no

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

Low to high transition Non-complementarity

confirmed, counter is invalid
Transition validated,
counter is incremented Detection of non-complementarity
C0129ENa

5.3 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.
DMs are used to process measurements and tap position indications.
A Digital Measurement can be associated to a Read Inhibit (RI) signal. The acquisition
process is different depending of the presence of this signal.
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 17/46

5.3.1 Acquisition without RI

The DM is calculated at each change of state of one of its bits.
A stability processing is applied at each calculation to confirm the value :
if the difference between the current value and the previous confirmed value is less or equal
than Vstab (value defined in configuration), then the current value is confirmed
if the difference is greater than Vstab, then the Tstab delay is launched (value defined in
configuration, from 0 to 60s, with a 10 ms step). If a Tstab delay is already launched, this one
is cancelled. At the end of the delay, the DM value is confirmed.

Confirmed Confirmed Confirmed

DM value DM value DM value

Tstab
Tstab

Bit change => new Bit change => Bit change =>
calculation new calculation new calculation
∆≤V stab=> confirmed ∆>V stab => Tstab ∆>V stab => Tstab
DM value launched re-launched

Note : ∆= |confirmed DM value – new calculation|

C0130ENa

Furthermore, an invalidity processing is applied : at the first change of state of one bit
following a confirmed DM value, the TInv delay is launched (value defined in configuration,
from 0 to 300s, with a 10 ms step). If the value is not confirmed at the end of this delay, the
DM is declared UNDEFINED.

TInv

Confirmed
DM value DM UNDEFINED
Tstab
Tstab
Tstab

Bit change => Bit change => Bit change =>

new calculation new calculation new calculation
∆>V stab => Tstab ∆>V stab => Tstab ∆>V stab => Tstab
launched re-launched re-launched
C0131ENa

If Vstab is equal to 0, there is no stability processing : all DM values are sent at each
calculation.
C264/EN FT/B30 Functional Description

Page 18/46 MiCOM C264/C264C

5.3.2 Acquisition with RI

When the RI signal changes to set state, the Tinh delay is launched. If the signal is always set
at the end of the delay, the DM is declared UNDEFINED. Otherwise, if the RI signal changes
to reset state before the end of the delay, the current DM value is transmitted.

Tinh Tinh

RI

DM value transmitted DM UNDEFINED

C0132ENa

If the RI signal is invalid, the DM will be invalid.

5.3.3 Encoding
The following code are allowed for DM :

CODE Number of bits Range of value

BCD 4 (1 BCD decade) 0 to 9
8 (2 BCD decades) 0 to 99
12 (3 BCD decades) 0 to 999
16 (4 BCD decades) 0 to 9999
Binary 4 0 to 15
7 0 to 127
8 0 to 255
12 0 to 4095
16 0 to 65535
Gray 8 0 to 255
16 0 to 65535
Decimal 16 (1 bit among 6 for the tens, 1 0 to 69
among 10 for the unit)
1 among N 2 0 to 2
to 32 to 0 to 32

One supplementary bit can be used for the sign (0 indicates a positive value, 1 indicates a
negative value)
5.4 Analogue input acquisition (AI)
Acquisition of voltage or current DC signals is done via AIU201 (4 AIs) board.
Acquisition of AC voltage and current coming from the electrical network is done via TMU200
(4CT + 4 VT) board.
5.5 Digital outputs (DO)
Two types of Digital Outputs are available into MiCOM C264:

• CCU200 boards for controls (8 DIs+4 normal open DOs), this board allows double
pole switching controls.

• DOU200 boards for alarms (8 normal open DOs + 2 normal open/normal close DOs).
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 19/46

5.6 Digital Setpoints

Digital setpoints are digital values sent on multiple parallel wired outputs. Each wired output
represents a bit of the value. Digital setpoints are used to send instruction values to the
process or to auxiliary devices.
The Digital Setpoints are processed on the same boards as the Digital Outputs. The Digital
Outputs characteristics described above apply on Digital Setpoints. Nevertheless, only
standard DO boards with single pole N/O relays can be used.
5.6.1 Encoding
The following code are allowed:

CODE Number of bits Range of value

BCD 4 (1 BCD decade) 0 to 9
8 (2 BCD decades) 0 to 99
12 (3 BCD decades) 0 to 999
16 (4 BCD decades) 0 to 9999
Binary 4 0 to 15
7 0 to 127
8 0 to 255
12 0 to 4095
16 0 to 65535
Gray 8 0 to 255
16 0 to 65535
Decimal 16 (1 bit among 6 for the tens, 1 0 to 69
among 10 for the unit)
1 among N 2 0 to 2
to 48 to 0 to 48

Moreover a supplementary bit can be used for the sign (0 indicates a positive value, 1
indicates a negative value).
5.6.2 Read Inhibit
A dedicated binary output can be used to allow or forbid the reading of the value by the
external device.
There is one (or none) read inhibit (RI) output per value.
If the RI output is a logical one (external polarity applied), the reading is permitted.
The procedure used to output a value with a RI output is :

• Reset the RI output to a logical 0 : read forbidden.

• Wait for N ms

• Output the value

• Wait for N ms

• Set the RI output to a logical 1 : read permitted.

The 0 to 1 transition on the RI output can be used by the external device as a trigger,
indicating that a new value is available.
C264/EN FT/B30 Functional Description

Page 20/46 MiCOM C264/C264C

6. DATA PROCESSING
MiCOM C264/C264C treatment entries can be Binary Inputs or Analogue Inputs. They are
issues 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 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.
After the acquisition on digital inputs boards, the computer performs toggle filtering, this
avoids to load the computer itself or other equipment when an input has an hazardous
behaviour (More than N state changes during a given duration).
A binary input can be suppressed by an order issued from an operator. No subsequent
change of state on a suppressed BI can trigger any action e.g. display, alarm, transmission.
The BI takes the “SUPPRESSED” state. When the operator unsuppresses the BI, this one
takes its actual state.
A BI can be substituted to a manual set state by an operator (state “SUBSTITUTED xxx”).
The BI stays in the state determined by the operator until he unsubstitutes it. When a BI is
substituted, no changes of state are transmitted, and computations, for instance groupings,
are made with the substituted state. When the BI is unsubstituted, the actual state is
transmitted to higher control levels and subsequent changes of state are transmitted again.
When an information is invalid (i.e. SELFCHECK FAULTY, TOGGLING, UNDEFINED or
UNKNOWN), it can be manually forced by a user (state “FORCED xxx”). This feature is
similar to the substitution but the information is automatically updated when valid information
is available again. A SUPPRESSED or SUBSTITUTED datapoint cannot be forced. The
forcing could also be automatic : in this case, the invalid information is automatically
replaced by the state defined in configuration.
By configuration, a BI could be transmitted using the two modes:

• Report based mode: for displaying, printing or archiving

• GOOSE based mode: for Ethernet UCA2 devices purposes

Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 21/46

6.1.2 Processing of Single Point Status

DI/DO
association

Group
processing

From Toggle
acquisition filtering Manual
suppression Persistance
filtering Transmission – To RCP
Substitution Report based To HMI
From IED IED To Printer
inputs To Archive
Forcing

System
Inputs
Transmission –
GOOSE based To
automation
C0133ENa

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 time tag is user-selectable :

• Mode 1 : the status is stamped with the time of the transition.

• Mode 2 : the status is stamped at the end of the persistent filtering.

The SP resulting states are:

States (Report) Goose

RESET 01
SET 10
TOGGLING 11
SELFCHECK FAULTY 11
UNKNOWN 11
SUPPRESSED 11
FORCED RESET 01
FORCED SET 10
SUBSTITUTED RESET 01
SUBSTITUTED SET 10

For automation (interlock, PSL, PLC, and build in functions), goose are used. Each valid
state (01, 10 and 00) is configurable to be seen by automation in False, True or invalid sate.
C264/EN FT/B30 Functional Description

Page 22/46 MiCOM C264/C264C

6.1.3 Processing of Double Point Status

Close DI/DO
contact association
From Toggle
acquisition filtering Group
processing
Open Persistance
Manual
contact Toggle filtering
suppression
From filtering Motion
acquisition filtering
Substitution
Transmission – To RCP
Report based To HMI
From IED IED Forcing
To Printer
inputs To Archive

System
Inputs
Transmission –
GOOSE based To
automation
C0134ENa

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

Close Contact Open Contact DPS State

0 0 Below motion delay, the state is valid motion. For
REPORT no transmission of the transitory state.
After Motion filtering, state is invalid JAMMED
0 1 OPEN
1 0 CLOSE
1 1 UNDEFINED after a permanent filtering

Preliminary treatments (filtering) for some DPs is applied to filter the MOTION state on a
certain period of time. This avoids the transmission of this (normally) transient state.
This treatment is said to be a motion filtering.
The time tag is user-selectable :

• Mode 1 : the valid state (OPEN or CLOSE) is stamped with the time of the beginning
of the MOTION state

• Mode 2 : the valid state (OPEN or CLOSE) is stamped with the time of this valid
transition
This time stamping can be superseded if a persistence filtering apply.
If the MOTION state is confirmed, it is always stamped with the time of the beginning of the
MOTION state. Furthermore, the BI takes the state JAMMED (in case of confirmed
MOTION00 state) or UNDEFINED (in case of confirmed MOTION11 state). In this case, the
following valid state (OPEN or CLOSE) is always time-stamped with the time of this valid
transition (depending of the persistence filtering feature).
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 23/46

The DP resulting states are:

States (report) Goose

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

6.1.4 Group processing

A group is a logical OR ,AND,NOR or NAND combination of Binary Inputs (BIs) or groups.
A group component can be a SP, DP (direct or via IED), SI, Group. A component can belong
to several groups.
A group is processed as a SP. It is time stamped with the date / time of the last data-point
which has modified the group status.
A group is calculated with filtered BIs (persistent filtering or motion filtering if configured).
Other computer BIs coming from reports.
6.2 Processing of Multi Point Status

contact 1
Toggle
From
filtering
acquisition

contact N Manual
Toggle suppression
From
filtering
acquisition Transmission –
Substitution MP filtering Report based

Forcing

System
Inputs
C0135ENa

Multiple Points is derived from N Digital Inputs. It is a kind of “1 among N” BIs. Transient
filtering is also added on acquisition for the cases where no Digital Inputs are SET or more
than one Digital Inputs are SET. After this delay, the MP becomes UNDEFINED.

N is fixed by MiCOM C264/C264C configuration from 2 to 32. There is no GOOSE

transmission mechanism.
C264/EN FT/B30 Functional Description

Page 24/46 MiCOM C264/C264C

6.3 Measurement Input Processing

Measurement Values can be Analogue Measurement, or Digital Measurement. Analogue
Measurements are acquired from communication or from computer boards (AIU201 for DC
or TMU200 for AC). Digital Measurement comes from Digital input boards.
6.3.1 Analogue processing

From IED
acquisition
Manual
suppression
Open Circuit Scaling Thresholds
From analogue
Management detection Substitution
acquisition

Forcing
From digital
acquisition

Transmission
CT/VT
From CT/VT
Calculations
acquisition

To RCP
To HMI
To Printer
To archive
To automation
C0136ENa

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 been cross
UNDERSHOOT[1..3] One of the 3 undershoot values has been 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 or on variation (% of nominal), and
anyway on state change. Periodic transmission is based on multiple of 100 (fast) or 500 ms
(slow).
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 25/46

6.3.2 CT/VT additional processing

From the direct primary measures (currents and voltages), MiCOM C264/C264C calculates
and transmits:

• RMS Values, current and voltage

• Active, Reactive and Apparent Power

• Power factor

• Frequency network

• 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
6.3.3 Digital Measurement Processing
DM is measurement is derived from Digital input. They are used for process measures or
Tap indications.
The DM is UNDEFINED in the followings conditions:

• The value is not stable.

• BCD: a quartet is more than 9

• Decimal: no bit is set or more than one for tens or unit

Two other bits can be used:

• For read inhibit: in this case, the DM is acquired when the read inhibit bit is set.

• For the sign

6.4 Accumulator Input Processing
The accumulator stores its current value in non-volatile memory. At configured sample 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 (among of energy of valid pulse).
C264/EN FT/B30 Functional Description

Page 26/46 MiCOM C264/C264C

7. CONTROL SEQUENCES
Control sequence is a basic built-in function on a module (switch, relay, and function). It
receives control order, sending back acknowledgement. After checks, control sequence send
control (protocol or DO), and check correct execution with feed back from protocol or from
DI.
7.1 Kind of control sequences
The control sequences automation receives three kind of input triggers (as order from higher
level) with selection, execution and unselection. Control order may have a normal or
abnormal termination with positive or negative acknowledgement to operator and to
communication.
By configuration, at PACiS SCE level a control sequence may be executed in one of the
following mode:

• Direct execute: Execution

• SBO once: Selection then Execution

• SBO many: Selection, several Execution, until Unselection (for transformers only)
By configuration, each DPC order (close order or open order) and each SPC can activate
simultaneously two DO contacts.
7.2 Control sequences checks
Receiving control, the control sequence 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 inside the substation

Module conditions

− Inter-control delay

− Status of the device

− Lock condition

− Automation already running (AR, AVR, …)

− Interlock equations (substation, bay, local of the module)

Execution conditions

− Delays upon selection feed back, start moving, final position reached
7.2.1 Mode Management
Control sequences are only performed if the computer mode is in operational mode. In test
mode, control sequences are allowed but digital outputs are not set.
7.2.2 IED connected
If a control has to be send to an IED, it is only accepted if this IED is connected to the
computer.
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 27/46

7.2.3 Control mode

This control sequence receives requests from the various control points:

• Automation (Auto Recloser, voltage regulation, PLC)

• MiCOM C264 Local Control Display

• MiCOM C264 TBUS communication from SCADA

• Station BUS (other computer in distributed automation, PACiS Operator Interface,

PACIS Gateway)

• Legacy BUS (from One Box Solution IED)

To avoid conflict between the control points, substation and bay modes are checked. Each
control sequence can be subject or not to these checks. The switches Remote/Local can be
hardware or software (saved in non-volatile memory).
The SBMC Site Based Maintenance Control allows controlling one specific bay from Local
Display or Operator interface even if substation is in remote. This feature is dedicated to
commissioning or maintenance and has also the possibility to filter data transmitted from the
bay to SCADA.
7.2.4 Uniqueness of control
It is possible by configuration to prevent having more than one control at a time.
7.2.5 Inter-control delay
It is possible by configuration to define an inter-control delay that is a minimum delay
between two consecutive controls on the same device.
7.2.6 Status of the device
It is possible by configuration to prevent control is the status of the device is not valid.
7.2.7 Lock device
Controls are not allowed on a lock device.
7.2.8 Running Automation
Controls are not allowed on a device if there is an associated automation in running.
For example controls issued from PACiS OI or gateway are not allowed on a transformer
controlled by voltage regulation.
7.2.9 Interlocking
The operating of a switching device (Circuit breakers, Traditional disconnecting switches,
Disconnecting switches with abrupt rupture, Ground disconnecting switches) is directly
related on its nature and its environment.
To operate these devices some conditions have to be respected. These conditions, called
interlocking, are managed by logical equations within the MiCOM C264/C264C.
The goal of the function of interlocking is to prohibit control sequence that may violate device
operating condition (e.g. break capability, isolation…) or plant operating condition.
C264/EN FT/B30 Functional Description

Page 28/46 MiCOM C264/C264C

7.3 HV Control Sequences

7.3.1 Circuit breaker
Several kind of circuit breaker can be managed:

• Three phases or single phase circuit breaker

• Synchronised or non-synchronised, with internal or external synchrocheck.

• With and without Auto Recloser

For three phase breaker each phase DPS is provided separately, and it is managed globally
by single (grouped) control and global DPS position. Pole Discrepancy management is
available.
7.3.2 Disconnector
The control sequence of disconnectors is identical to single non-synchronised circuit
breakers.
7.3.3 Transformer
Transformer position is determined using TPI (Tap Position Indication). TPI can be a Digital
Measurement or Analogue Measurement (from DC Analogue Input).
Transformer is the only device supporting the SBO Many control sequences. It is linked to
voltage regulation, also its Raise and Lower controls are defined for secondary voltage (and
not tap position). Except for auto wounded transformer, raise/lower voltage is also a
raise/lower tap.
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 29/46

8. AUTOMATIONS
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 some build-in automation functions are available and can be
set directly by the user:

• Auto-recloser

• Synchrocheck

• Transformer Voltage regulation

• Trip-coil supervision
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 live line / live bar in locking or coupling
mode.

• Automatic and manual network connection on live line / dead bar,

• Automatic and manual network connection on dead line / live bar,

• Automatic and manual network connection on dead line / dead bar.

C264/EN FT/B30 Functional Description

Page 30/46 MiCOM C264/C264C

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 allow the circuit breaker closing.
The following voltage controls are available:

• Vline and Vbusbar for network coupling

• Vline and Vbusbar for network locking

• Vline and not(Vbusbar)

• not(Vline) and Vbusbar

• not(Vline) and not(Vbusbar)

With Vline and Vbusbar TRUE if the measured voltage is above the threshold V>, and not(Vline)
and not(Vbusbar) TRUE if the measured voltage is below the threshold V<.
The selection of the voltage control is made during the configuration phase.
By configuration, a single synchrocheck can manage two circuit breakers. Be careful, in this
case the voltage switching is not managed by the computer.
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 31/46

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.
The general diagram of the auto-recloser function is :

Auto-recloser out
of service

In Service request

Auto-recloser in
service

TRIP /TRIP_1P_X

3 phases
no 1 phase
CB_HEALTHY Analysis of the CB_HEALTHY no
Cycle n˚=1
= SET ? received trip = SET ?

yes yes
Waiting CB Waiting CB
opening opening

End of 150 ms timer End of 150 ms

CB open timer CB open
AR locked AR locked
Launch cycle timer Launch cycle timer
(for first single- (for 3-phases cycle)
phase cycle)

TRIP
TRIP_1P_X always set
End of
End of TRIP always set
timer
timer AR locked
AR locked
AR_BLOCKING no
AR_BLOCKING
no = RESET ?
= RESET ?
yes
yes
Closing the CB
Closing the CB

CB closed TRIP New CB

TRIP closed

Launch Cycle = cycle +1

recovering timer

Launch
recovering timer
End of TRIP
timer
Cycle n˚=2
TRIP End of
timer

no
Last cycle?

yes

AR locked
C0137ENa

FIGURE 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.
C264/EN FT/B30 Functional Description

Page 32/46 MiCOM C264/C264C

8.1.3 Trip Circuit supervision

The trip circuit supervision shall continuously monitor the trip circuit wiring continuity
whatever the position of the circuit breaker poles.
The MiCOM computers are able to support the 2 diagrams used in Trip Circuit Supervision:

• Trip Circuit Supervision with one Digital Input + external resistor.

+ Uaux

Computer

Protection relay
Vn+
DI-1
Vn-

Vn+
DI-2
Vn-

CB

- Uaux
C0138ENa

FIGURE 6 : TRIP CIRCUIT SUPERVISION WITH ONE DI

Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 33/46

• Trip Circuit Supervision with two Digital Inputs without external resistor.

+ Uaux

Computer

Protection relay
Vn+
DI-1
Vn-

Vn+
DI-2
Vn-

CB

- Uaux
C0139ENa

FIGURE 7 : TRIP CIRCUIT SUPERVISION WITH TWO DI

8.1.4 Automatic Voltage Regulation (AVR)
To maintain a system voltage supply within given deadband, 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 Voltage Regulation function that continuously monitors the
transformer.
The motors-driven OLTC received the "Raise" and "Lower" control commands from the
Voltage Regulation module. These order 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 : VOLTAGE REGULATION MANAGEMENT

C264/EN FT/B30 Functional Description

Page 34/46 MiCOM C264/C264C

Automatic Voltage Regulation module also manages:

• Active and reactive compounding in order the maintain the voltage at a remote
location

• Homing in order to adjust a transformer to the voltage of the busbar 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.

• Electrical topology in order to determine parallel transformers

• Tap Position Indication

The user may set the Automatic Voltage Regulation module:

• Automatic Voltage Regulation On/Off

• Five Target Voltages (5 floating pre-set values)

The Automatic Voltage Regulation module display the 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

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

Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 35/46

8.2 Fast automation (PSL)

These automations are event-driven : they are calculated each time an input changes (i.e.
there is no cycle time).
Only BI and measurements described are usable as inputs (controls are not).
PSL are logical equations that use the following functions :
AND, OR, XOR, NOT, NAND, NOR operators
“bistable” function
pickup and drop-off timers (from 10 ms to 60 seconds, by step of 10 ms)
BI setting – the system BI is :

• SET if the PSL is TRUE

• RESET if the PSL is FALSE

• INVALID if the PSL is INVALID

Digital Output setting – the DO is :

• closed if the PSL is TRUE

• opened if the PSL is FALSE or INVALID (only in case of permanent DO)

The equations management rules described for interlocking equations apply on PSL.
For the PSL, limits are 256 gates and 1700 logical equations.

I1
& DO1
setting

I2
& DO2
setting

≥1 t

&
BI1
≥1
setting
≥1

I3
≥1
I4
C0140ENa

FIGURE 9 : EXAMPLE OF PSL

PSL configuration is part of PACiS System Configuration Editor
C264/EN FT/B30 Functional Description

Page 36/46 MiCOM C264/C264C

8.3 PLC automation

The MiCOM C264/C264C allows the user to configure specific control sequences or
automations (e.g. switching sequences, busbar transfer, load shedding, GIS-pressure
supervision) during the substation configuration phase.
The Programmable Logic Controls (PLC) or Configurable Automations are entered and build
onto a logic development workbench. A real time kernel that is located in the computer runs
them.
The solution retained for developing control logic programs in the computer is a Soft Logic
package.
The Soft Logic package Workbench is a Host-based software development environment
associated to the System Configurator. It used to create control logic programs.
It is a full-featured set of tools providing:

• Editing

• Code generation

• Simulation

• Debugging
The Soft Logic package supports standard programming languages of the IEC 1131-3:

• Sequential Function Chart, SFC (GRAFCET)

This language can be used with Function Block Diagram (FBD), Ladder Diagram (LD) or
Instruction List (IL) for action and transition descriptions.

• Structured Text, ST
The code generated by the Soft Logic package workbench is uploaded to the computer
target system that runs it.

Control logic
application
code

Soft Logic Target

package hardware

C0019ENa

FIGURE 10 : WORKBENCH AND TARGET

Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 37/46

9. USER INTERFACE
MiCOM C264/C264C provides three user interfaces:

• The front Panel

• The Computer Maintenance Tool (CMT)

• The Printer
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 (GHU210 or GHU211)

• A graphical FP with LEDs, L/R push-button, the Local Control Display and the serial
link (GHU200 or GHU201)

LEDs

Key-pad

Local/Remote
Graphical push-button
LCD

RS 232 Serial port

C0020ENb

FIGURE 11 : MiCOM C264C FRONT PANEL (GHU200)

The FP is detachable up to 5 meters from the MiCOM C264/C264C base case using a
specific front panel (GHU220 or GHU221)
13 (for GHU20x) or 12 (for GHU21x) red LED 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.
C264/EN FT/B30 Functional Description

Page 38/46 MiCOM C264/C264C

9.1.1 Local Control Display

The Liquid Crystal Display has several kind of screen or panels split in two families protected
by 2 levels of password for action. The first set of panel 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 of panel is called menu tree. It allows access to settings or suppression of
data point state/value.
The push buttons associated with the graphical LCD allow:

• Navigate between screens or panels,

• Select information

• Enter value or string (including password)

• Send Control (Bay Mode, switch gear, transformer …)

9.1.2 Local/Remote push-button
The Local/Remote push button manage the MiCOM C264/C264C operation modes:

• Local

• Remote
When a control depends on bay mode, it is accepted from front panel when the bay is in
Local mode and from other control points when the bay is in Remote Mode.
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 tunnelling mode)

9.2 Computer Maintenance Tool
CMT is a graphical tool, it gives access to standard commands and secure the basic
maintenance interventions
CMT communicates with C264 on Ethernet in direct addressing mode.
CMT functions are:

• Access to C264 software version and facility to download new software

• Access to C264 databases versions and descriptions and facility to download and
switch new database

• Access to boot parameters and facility to change them

• Access to date and time and facility to change them

• Access to Sequence of events file

Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 39/46

9.3 Printer
Some specific events (the events to log are declared in the database) are printed and
chronologically sorted on logbook printers. They are printed with their time stamping and a
complete description (location and event description).
Logbook printers can be connected to SCP operator interface or to a bay level computer.
The printout format, which can be defined by user during the system configuration phase, is
the same across the whole log book printers connected.
A computer does not print information coming from other computers.
9.3.1 Inputs
A computer receives acquisition from various equipment (protection, captors, etc.) and, after
processing, may generate events that have to be printed. These kinds of events are defined
in the database during the configuration phase.
Types of events can be :

• Binary inputs (SP, DP, MP, SI and Groups)

• Tap position indication

• Measurement

• Operator action :

• Log-in and log-off,

• Devices control

• Alarm acknowledgement / clearing

9.3.2 Outputs
The 5 following properties can be printed. Each property is separated from the other by one
blank character The position of each property in the printed line (i.e. position 1, 2, 3, 4 or 5)
is defined in configuration :
Chronology – 1 character : refer to § “SOE events”
TimeStamp – 24 or 26 characters : refer to § “SOE events”
Origin - 67 characters : for BI, TPI, measures, controls and alarms, the origin gives the
access path to the object (refer to § “SOE events”)
ObjectName - 16 characters
ObjectMessage - 16 characters
The Origin, ObjectName and ObjectMessage properties contain different information
depending of the associated event type.
C264/EN FT/B30 Functional Description

Page 40/46 MiCOM C264/C264C

9.3.3 Printer management

9.3.3.1 Header & footer
A header and footer can be printed at each page. They are composed of one line, separated
from the events by a blank line.

Site Name – Computer Name Date / Time

<blank line>

<Log Book>

<blank line>

Page Number
C0141ENa

FIGURE 12 : PAGE FORMAT

The page number is in the range [1..999]. It is reset at 1 after reaching 999 and at each new
day.
The date could have the following format : DD/MM/YY or MM/DD/YY or YY/MM/DD or
DD/MM/YYYY or MM/DD/YYYY or YYYY/MM/DD. The time has the following format :
hh:mm:ss.
9.3.3.2 Chronology & time stamp
The printers are managed in a real-time printing mode.
All synchronised information is printed in a chronological order.
Events are printed with their time-stamping and a complete description (location and event
description). The equipment detecting the event does the time-stamping (time-stamping at
source).
9.3.3.3 Printer out of service
If a printer fails, all the messages are stored in a circular buffer
When the buffer is full, any new message replaces the oldest one.
An indication (Printer status) is generated to indicate the printer failure.
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 41/46

9.3.3.4 Circular FIFO management

Before being printed, all information goes into a circular buffer
A latency delay is configured to sort information.

latency

Printers Buffer Length Data flow

C0142ENa

FIGURE 13 : FIFO MANAGEMENT

The size of the buffer is 1000.
When the buffer is full, the oldest information are deleted (300 information suppressed) in
order to have place for new ones.
A specific message is inserted in the buffer to indicate the lost of information, this message
has the following information:
TimeStamp = date of the oldest suppress information
Origin = Name of the computer (configurable)
ObjectName = SUPPRESSED INFOS (configurable)
ObjectMessage = number of lost information
C264/EN FT/B30 Functional Description

Page 42/46 MiCOM C264/C264C

10. RECORDS
Several kinds of records are stored into MiCOM C264.
10.1 Permanent records storage
They are stored on flash disk.
10.1.1 Data storage
All parameters or settings that can be modified via front face LCD are stored in flash disk.
Lists of system information are also stored in the flash disk.
10.1.2 Waveform Recording
MiCOM C264/C264C provides

• Fast Waveform recording which gives access to samples

• Slow wave form which gives access to RMS values

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

Number of Files Number of cycles

8 60
4 120
2 240
1 480

The waveform recorder can be triggered by the following events, each of which is user
configurable :

• Changes in state of binary inputs (SP, DP, MP, SI or Groups)

• Changes in state of digital outputs

• Measurement threshold violations

• Operator request
Only one re-trig is allowed : it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are stored using COMTRADE 97 binary format.
Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 43/46

10.1.2.2 Slow Waveform Recording

The inputs for the slow waveform records are :

• analogue values coming from CT VT calculation (RMS values)

• analogue values coming from AIU boards.

• Digital inputs

• Digital outputs
The slow wave form manages up to 24 analogue and 48 digital values.
Data from CT VT can be chosen among:

• RMS Values of phase voltage

• RMS values of busbar voltage

• RMS values of phase current

• RMS values of residual voltage and current

• Fundamental sequence components

• Active Power

• Reactive Power

• Apparent Power

• Frequency

• Harmonics levels
MiCOM C264 stores at maximum 5000 integrated values as follow:

Number of Files Number of integrated values

1 5000
2 2500
5 1000
10 500
20 250
50 100

The integrated value has duration up to one hour. It is defined in configuration.

For analogue, the stored value is the average value during integrated period.
For digital, the stored value depends also on the average:
If average value > x then the stored value is 1 else it is 0, x is defined in configuration and it
is a value between 0.1 and 0.9.
The slow waveform recorder can be triggered by the following events, each of which is user
configurable :

• Changes in state of binary inputs (SP, DP, MP, SI or Groups)

• Changes in state of digital outputs

• Measurement threshold violations

• Operator request

• Periodically (i.e. every day at 00h00)

C264/EN FT/B30 Functional Description

Page 44/46 MiCOM C264/C264C

10.1.3 Events
All data change or events declared in MiCOM C264/C264C configuration database « To be
logged » are stored in a circular queue.
The event records are available for viewing either via the front panel LCD, via slave protocol
at SCADA level or on CMT equipment. They also can be printed.
Events , following MiCOM C264/C264C configuration, may typically contain the MiCOM
C264/C264C description, the date of the event and the time of the event with an accuracy of
1 ms, plus specific information regarding the causes of the events.
The MiCOM C264/C264C under the following circumstances may create events:

• Changes of state of Binary Inputs (SP, DP, MP, SI, Groups)

• Changes of state of Measurements

• Changes of state and value of Tap Position Indications

• Devices Control actions and acknowledgements.

• Alarm acknowledgement.
The size queue is:

• 200 data for front panel

• 2000 data for CMT

• configurable per slave protocol for SCADA

Functional Description C264/EN FT/B30

MiCOM C264/C264C Page 45/46

10.2 Non-permanent data storage

10.2.1 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
By configuration, one of the following behaviour is chosen:

Alarm inactive
/ cleared
0
AL+

AL+
Alarm active-
AL- (auto) unacknowledged AL+

AL+ ACK AL-

Alarm active- Alarm inactive-

acknowledged active-
unacknowledged
2 3
AL- ACK

ACK (auto)
Alarm inactive-
acknowledged
CLEAR AL+
4
C0143ENa

FIGURE 14 : EVENT ALARMED ON APPEARANCE ONLY

C264/EN FT/B30 Functional Description

Page 46/46 MiCOM C264/C264C

Alarm inactive
/ cleared
0

AL+ AL+

AL+
Alarm active-
unacknowledged
AL+
1
AL+
AL-

ACK Alarm inactive-

active-
unacknowledged
5

ACK

Alarm active- Alarm inactive-

acknowledged unacknowledged
2 AL- 3
ACK

ACK (auto)
Alarm inactive-
CLEAR acknowledged AL+
4
C0144ENa

FIGURE 15 : EVENT ALARMED ON APPEARANCE AND DISAPPEARANCE

Transition events:

• AL+ alarmed event appearance

• AL- alarmed event disappearance

• ACK operator acknowledgement of the alarm

• CLEAR operator clearing of the alarm

NOTE: In that case « alarmed event disappears (AL-) » means that the
associated data is now in another state which is not alarmed. The time
stamp of the alarm is modified.
Hardware C264/EN HW/B30

MiCOM C264/C264C

HARDWARE
Hardware C264/EN HW/B30

MiCOM C264/C264C Page 1/34

CONTENT

1. SCOPE OF THE DOCUMENT 3

2. HARDWARE DESCRIPTION 4
2.1 Concept 4
2.1.1 Components 4
2.1.2 Hardware Overview 5
2.2 MiCOM C264C 6
2.2.1 Hardware presentation 6
2.2.2 Modularity 7
2.2.3 I/O Capabilities 7
2.2.4 Front Back Plane – FBP242 8
2.2.5 Front Panels 8
2.3 MiCOM C264 10
2.3.1 Hardware presentation 10
2.3.2 Modularity 11
2.3.3 I/O Capabilities 11
2.3.4 Front Back Plane – FBP280 11
2.3.5 Front Panels 12
2.4 Coding of board address 13
2.5 Modules description 14
2.5.1 Power auxiliary supply and legacy ports board – BIU241 14
2.5.2 Central Processing Unit and base communications board – CPU260 16
2.5.3 Digital Inputs Unit – DIU200 18
2.5.4 Digital Inputs Unit – DIU210 19
2.5.5 Digital Outputs Unit – DOU200 20
2.5.6 Circuit breaker Control Unit - CCU200 21
2.5.7 Analogue Input Unit – AIU201 22
2.5.8 Analogue Input Unit – AIU210 23
2.5.9 Transducer less Measurements Unit – TMU200 24
2.5.10 Ethernet Switch Unit – SWU200 25
2.5.11 Extended communication Unit – ECU200 32
2.5.12 Extended communication Unit – ECU201 33
2.6 Hardware tropicalisation 33
C264/EN HW/B30 Hardware

Page 2/34 MiCOM C264/C264C

BLANK PAGE
Hardware C264/EN HW/B30

MiCOM C264/C264C Page 3/34

1. SCOPE OF THE DOCUMENT

This document is a chapter of MiCOM C264/C264C documentation binders. It describes the
product hardware which is not the commissioning chapter.
C264/EN HW/B30 Hardware

Page 4/34 MiCOM C264/C264C

2. HARDWARE DESCRIPTION
2.1 Concept
2.1.1 Components
The MiCOM C264/C264C is based on a modular and scalable architecture to support
dedicated hardware modules adapted to the plant data interfaces.
Each MiCOM C264/C264C rack can be equipped with the following modules:

• BIU241: Basic Interface Unit. This board includes the auxiliary power supply
converter, the watchdog relay, 2 digital outputs/2 digital inputs for computer
redundancy and 2 insulated RS485/RS232 interface.

• CPU260: Central Processing Unit and communications board based on PowerPC

processor

• DSP200: Digital Signal Processing board is the processor board for CT VT calculation.
It is the CPU200 daughter board.

• FBP280: Front BackPlane : bus for 80TE case

• FBP242: Front BackPlane: bus for 40TE case

• DIU200: Digital Inputs Unit each with 16 digital inputs

• DIU210: Digital Inputs Unit each with 16 digital inputs with current-peak and voltages
from 24V to 220V

• DOU200: Digital Outputs Unit each with 10 digital outputs for alarms

• CCU200: Circuit breaker Control Unit each with 8 digital inputs and 4 digital outputs

• AIU201: Analogue Input Unit each with 4 analogue inputs direct current or voltage

• AIU210: Analogue Input Unit each with 8 analogue inputs direct current

• TMU200: Transducerless Measurements Unit board for direct CT/VT measuring

acquisition with 4 CT and 4 VT

• SWU200: Ethernet SWitch Unit board with 4 electrical links and 0,1 or 2 optical links

• SWR200: Ethernet SWitch for Redundancy board with 4 electrical links and 2 optical
links for a redundancy ring.

• ECU200: Extended Communication Unit board to convert non insulated RS232 into
optical signal

• ECU201: Extended Communication Unit board to convert non insulated RS232 into
insulated RS485 signal

• GHU201 (for C264) or GHU200 (for C264C): Graphical Human machine interface
Unit: Front Panel including 17 LEDs (13 free configurable) + 7 pushbuttons (L/R,
Open, Close, etc) + LCD (resolution of 128 x 128 pixels /16 lines of 21 characters
each) and a keypad at the front plate for local MMI management.

• GHU211 (for C264) or GHU210 (for C264C): Front Panel including 17 LEDs (12 free
configurable) + 1 pushbutton (L/R).

• GHU221 (for C264) or GHU220 (for C264C): Front Face used to connect a detachable
HMI (GHU20x or GHU21x).
Hardware C264/EN HW/B30

MiCOM C264/C264C Page 5/34

2.1.2 Hardware Overview

Watchdog
FBP280 BIU241
or FBP242 (1) Redundancy RS232/RS485/RS422

COM 1 / COM 2
RS232/RS485
Power Supply
Electrical RJ45 link
Ethernet
CPU260 Optical link
(1)
COM 1 / COM 2
DSP200 RS232 ECU20x RS485
(up to 1) RS422
IRIG-B RS232 ECU20x Optical

GHU240
OR
GHU240 GHU240
OR OR
GHU240 GHU240

SWU200 Optical 1 / Optical 2

(up to 1)

Electrical 1 to 4

SWR200 Optical 1 / Optical 2

(up to 1) Mandatory

Optional
Electrical 1 to 4

AIU201/AIU210
(up to 6)

DOU200
(up to 15)

CCU200
(up to 15)

DIU200/DIU210
(up to 15)

TMU200
(up to 1)

C0117 ENb

FIGURE 1 : HARDWARE OVERVIEW

C264/EN HW/B30 Hardware

Page 6/34 MiCOM C264/C264C

2.2 MiCOM C264C

2.2.1 Hardware presentation
The MiCOM C264C mechanical rack has the following features:

• Height: 4 U

• Width: 40 TE
Dimensions of this rack are in the figure below:

FIGURE 2 : MiCOM C264C – RACK SIZE

Case properties:

• Case degree of protection: IP52 in standard

• Front Panel degree of protection: IP52

• Metallic case
Hardware C264/EN HW/B30

MiCOM C264/C264C Page 7/34

2.2.2 Modularity
The MiCOM C264C is available in two case versions allowing flexibility and scalability in the
use of the I/O modules:

FIGURE 3 : MiCOM C264C – REAR PANEL OVERVIEW WITH CTVT

FIGURE 4 : MiCOM C264C – REAR PANEL OVERVIEW WITHOUT CTVT

2.2.3 I/O Capabilities
Inside the Case with CT VT, there are 4 available slots for I/O boards (DIU200, DIU210,
AIU201, AIU210, DOU200 or CCU200) or switch boards (SWU200 or SWR200).
Inside the Case without CT VT, there are 6 available slots for I/O boards (DIU200, DIU210,
AIU201, AIU210, DOU200 or CCU200) or switch boards (SWU200 or SWR200).
C264/EN HW/B30 Hardware

Page 8/34 MiCOM C264/C264C

2.2.4 Front Back Plane – FBP242

The FBP242 board is the back plane used for the MiCOM C264C.

FIGURE 5 : MiCOM C264C – FBP242 BOARD

2.2.5 Front Panels
2.2.5.1 GHU200
The GHU200 is the front panel with LCD and LEDs used for the MiCOM C264C:

• 17 LEDs (13 free configurable)

• 7 pushbuttons (L/R, Open, Close, etc)

• a keypad at the front plate for local MMI management with 5 pushbuttons

• a LCD (resolution of 128 x 128 pixels /16 lines of 21 characters each)

FIGURE 6 : MiCOM C264C – GHU200 BOARD

Hardware C264/EN HW/B30

MiCOM C264/C264C Page 9/34

2.2.5.2 GHU210
The GHU210 is the front panel with LEDs used for the MiCOM C264C:

• 17 LEDs (12 free configurable)

• 1 pushbuttons (L/R)

FIGURE 7 : MiCOM C264C – GHU210 BOARD

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

FIGURE 8 : MiCOM C264C – GHU220 BOARD

C264/EN HW/B30 Hardware

Page 10/34 MiCOM C264/C264C

2.3 MiCOM C264

2.3.1 Hardware presentation
The MiCOM C264 mechanical rack has the following features:

• Height: 4 U

• Width: 80 TE
Dimensions of this rack are in the figure bellow:

FIGURE 9 : MiCOM C264 – FRONT PANEL OVERVIEW

Case properties:

• Case degree of protection: IP20 in standard

• Front Panel degree of protection: IP52

• Metallic case
Hardware C264/EN HW/B30

MiCOM C264/C264C Page 11/34

2.3.2 Modularity
The MiCOM C264C is available in two case versions allowing flexibility and scalability in the
use of the I/O modules:

FIGURE 10 : MiCOM C264 – REAR PANEL OVERVIEW WITH CTVT

FIGURE 11 : MiCOM C264 – REAR PANEL OVERVIEW WITHOUT CTVT

2.3.3 I/O Capabilities
Inside the Case with CT VT, there are 14 available slots for I/O boards (DIU200, DIU210,
AIU201, AIU210, DOU200 or CCU200) or switch boards (SWU200 or SWR200).
Inside the Case without CT VT, there are 15 available slots for I/O boards (DIU200, DIU210,
AIU201, AIU210, DOU200 or CCU200) or switch boards (SWU200 or SWR200).
2.3.4 Front Back Plane – FBP280
The FBP280 board is the back plane used for the MiCOM C264.

FIGURE 12 : MiCOM C264 – FBP280 BOARD

C264/EN HW/B30 Hardware

Page 12/34 MiCOM C264/C264C

2.3.5 Front Panels

2.3.5.1 GHU201
The GHU201 is the front panel with LCD and LEDs used for the MiCOM C264:

• 17 LEDs (13 free configurable)

• 7 pushbuttons (L/R, Open, Close, etc)

• a keypad at the front plate for local MMI management with 5 pushbuttons

• a LCD (resolution of 128 x 128 pixels /16 lines of 21 characters each)

FIGURE 13 : MiCOM C264 – GHU201 BOARD

2.3.5.2 GHU211
The GHU211 is the front panel with LEDs used for the MiCOM C264:

• 17 LEDs (12 free configurable)

• 1 pushbuttons (L/R)

FIGURE 14 : MiCOM C264 – GHU211 BOARD

Hardware C264/EN HW/B30

MiCOM C264/C264C Page 13/34

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

FIGURE 15 : MiCOM C264 – GHU221 BOARD

2.4 Coding of board address

Same rule is applicable to all I/O boards (DIU200, DIU210,
AIU201, AIU210, DOU200, and CCU200):
Binary coding on 4 jumpers top down (From 0 to 15)

− Jumper

− missing => 1

− present => 0
Example:

1 0
0 2
0 0
0 8

address =1 address = 10
C0030ENa

NOTE: Two boards of the same type must not have the same address
C264/EN HW/B30 Hardware

Page 14/34 MiCOM C264/C264C

2.5 Modules description

2.5.1 Power auxiliary supply and legacy ports board – BIU241
This board includes:

• the auxiliary power supply converter

• the watchdog relay (closed if the product is healthy)

• 2 outputs (Normally open contacts) and 2 inputs for redundancy

• 2 insulated interfaces (Port 1: RS232 or RS485, Port 2: RS232, RS422 or RS485).

The power auxiliary supply board is protected against reversal polarity

FIGURE 16 : MiCOM C264 - BIU241 BOARD

The BIU241 board provides two insulated serial links.
Hardware C264/EN HW/B30

MiCOM C264/C264C Page 15/34

This following figure shows how to configure the serial links.

C0033ENa

FIGURE 17 : ZOOM ON BIU JUMPERS

2.5.1.1 Configurable communication Port 1 - RS232/485
The communication link characteristics are:

• full duplex serial protocol

• Transmission rate: 50 to 38400 bps (configurable with PACiS configurator or settable

via GHU20x)
Configuration:
The hardware jumpers arrangement is as follow.

• In RS232 set the jumpers S14, S16 and between S12.1 and S12.3

• In RS485 set the jumpers S13, S15 and between S12.1 and S12.2. It is possible to
end the line with a 124Ω resistor by setting S17. (See CO chapter to know when the
resistor has to be used).
2.5.1.2 Configurable communication Port 2 - RS232/422/485
The communication link characteristics are:

• full duplex serial protocol

• Transmission rate: 50 to 38400 bps (configurable with PACiS configurator or settable

via GHU20x)
Configuration:
The hardware jumpers arrangement is as follow.

• In RS232 set the jumpers S5, S6, S9 and S3

• In RS485 set the jumpers S7, S8, S2. It is possible to end the line with a 124Ω resistor
by setting S11. (See CO chapter to know when the resistor has to be used).

• In RS422 set the jumpers S7, S8, S4 and S2. It is possible to end the line with a 124Ω
resistor by setting the jumpers S10 and S11. (See CO chapter to know when the
resistor has to be used).
C264/EN HW/B30 Hardware

Page 16/34 MiCOM C264/C264C

2.5.2 Central Processing Unit and base communications board – CPU260

The CPU260 board is based on a PowerPC processor including the 10/100BaseT Ethernet
communication.
Optionally, this board includes the following capabilities:

• One 100BaseF Ethernet port (ST connector)

• Two non insulated RS232 links. The transmission rate must be the same on both links
(values from 50 to 38400 bps (configurable with PACiS configurator or settable via
GHU20x)

• One IRIG-B input

• One daughter board (DSP200) for CTVT management

This board is interfaced with all I/O boards and the front panel.
CPU260 has the following key features:

• 32-bit Power PC-based microprocessor (MPC860DP or MPC860P) clocked at

80 MHz;

• 64 Mbytes Dynamic memory DRAM

• 16 Mbytes Flash memory

• 256 Kbytes static memory SRAM

• Calendar saved

FIGURE 18 : MiCOM C264 - CPU260 BOARD

Hardware C264/EN HW/B30

MiCOM C264/C264C Page 17/34

FIGURE 19 : MiCOM C264 – DSP200 DAUGHTER BOARD ON CPU200

C264/EN HW/B30 Hardware

Page 18/34 MiCOM C264/C264C

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 used for single or double status, pulse or digital
measurement input on the same module.

FIGURE 20 : MiCOM C264 - DIU200 BOARD

Hardware C264/EN HW/B30

MiCOM C264/C264C Page 19/34

2.5.4 Digital Inputs Unit – DIU210

The Digital Input module provides 16 optically insulated digital inputs.
The capabilities of the DIU210 boards are:

• 16 optically insulated digital inputs

• 1 common contact for 2 inputs

• Protection against reversal polarity

• The digital inputs can be used for single or double status, pulse or digital
measurement input on the same module.

• All voltages between 24V and 220V DC

• From 48V to 220VDC : High current circulationonsumption inside binary

contactsinputs during a short time (to clean external contacts) : see the current peak
response curve

• With 24Vdc voltage, the high current consumption (>25mA) is permanent

FIGURE 21 : MiCOM C264 - DIU210 BOARD

C264/EN HW/B30 Hardware

Page 20/34 MiCOM C264/C264C

Current peak response curve

35

30

25
Current (mA)
20

15

10

0
0 50 100 150 200 250 300
Tension (V)
C0159ENa

2.5.5 Digital Outputs Unit – DOU200

The Digital Outputs Unit (DOU200) board provides 10 outputs (10 DO) using integrated
relays.
The DOU200 board capabilities are:

• 8 single pole relays with one normally open (NO) contact

• 2 single pole relays with 1 common for 2 outputs (NO/NC)

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

FIGURE 22 : MiCOM C264 - DOU200 BOARD

Hardware C264/EN HW/B30

MiCOM C264/C264C Page 21/34

2.5.6 Circuit breaker Control Unit - CCU200

The Circuit breaker Control Unit (CCU200) board provides 8 digital inputs (8 DI) and 4
double pole outputs (4 DO) using integrated relays.
The CCU200 provides 8 optically insulated digital inputs.
The digital input (DI) capabilities of the CCU200 boards are:

• 8 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 inputs on the same
module.
The digital output (DO) capabilities of the CCU200 boards are:

• 4 double pole switching relays with normally open (NO) contacts

• 1 common + and 1 common - contacts per 2 relays

A self-monitoring device for the output control chain is provided (address check, state
monitoring)
The +5V voltage is monitored to avoid issuing inadvertent controls.
The digital outputs can be configured in double remote signalling only.

FIGURE 23 : MiCOM C264 - CCU200 BOARD

C264/EN HW/B30 Hardware

Page 22/34 MiCOM C264/C264C

2.5.7 Analogue Input Unit – AIU201

The Analogue input module (AIU201) has 4 independent analogue inputs. Each AI can be
configured in voltage or current range individually between.

FIGURE 24 : MiCOM C264 - AIU201 BOARD

Hardware C264/EN HW/B30

MiCOM C264/C264C Page 23/34

2.5.8 Analogue Input Unit – AIU210

The Analogue input module (AIU210) has 8 independent analogue inputs. Each AI can be
configured in current range only.

FIGURE 25 : MiCOM C264 - AIU210 BOARD

C264/EN HW/B30 Hardware

Page 24/34 MiCOM C264/C264C

2.5.9 Transducer less Measurements Unit – TMU200

The transducers less 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%

FIGURE 26 : MiCOM C264 – TMU200 BOARD

Hardware C264/EN HW/B30

MiCOM C264/C264C Page 25/34

2.5.10 Ethernet Switch Unit – SWU200

This board is an Ethernet switch with 4 electrical links and up to 2 optical links

FIGURE 27 : MiCOM C264 – SWU200 BOARD

Some jumpers are used to adapt the switch to your network :

Factory
N° Open Closed
setting
W1 No watching port 5 Fault watching Port 5 (Fx) Open
W3 Enable more aggressive back- Enable less aggressive back-off Open
off
W4 Max length is 1536 byte Enable enforce the max frame Open
length for VLAN is 1522
W5 Enable half duplex back Disable half duplex back pressure Open
pressure
W6 Continue sending frame Enable to drop frame after 16 Open
regardless of number of collisions
collisions
W7 Enable flow control Disable flow control Closed
W8 No priority reserve Enable 6KB priority buffer reserved Closed
W9 Half duplex for port 5 (Fx) Full duplex for port 5(Fx) Closed
W10 Unlimited broadcast frames Enable 5% broadcast frame allowed Open
W11 Half duplex for port 6 (Fx) Full duplex for port 6 (Fx) Closed
W12 Enable 802.1p selected by Enable 802.1p field for all port Closed
EEPROM
W13 Share buffers up to 512 Enable equal amount of buffers per Open
buffers on a single port port (113 buffers)

OPEN CLOSE
C264/EN HW/B30 Hardware

Page 26/34 MiCOM C264/C264C

Port 6

W12

Port 5 (optional)

LED1
LED2
LED3 Port 4
LED4
LED5
Port 3
LED6
W13
W4 Port 2
W3
W5
W6 W8
W7 W9
W10 W1 Port 1
W11

C0118ENa

The optical link are monitored. If one comes down

Components side Pin State

1 Open

2 Common

1 2 3 3 Close

Close if default
C0119ENa
Hardware C264/EN HW/B30

MiCOM C264/C264C Page 27/34

Ethernet Redundant Switch– SWR200

This board is an Ethernet switch with 4 electrical links and 2 optical links for a redundancy
ring.

FIGURE 28 : MiCOM C264 – SWR200 BOARD

L1 L2
Fx1

Rp
J1
J3 Es

Rs
L5 L6 L7 L8 J2
L3 L4 Ep

J6-1

L9 L10 L11 L12 J6-4 1_

J7-1
S4 2_
J4
J7-7
3_
J9
J8-1
L13 L14 L15 L16 4_
J8-6

J5

L17 L18 L19 L20 C0120ENa

C264/EN HW/B30 Hardware

Page 28/34 MiCOM C264/C264C

Some jumpers are used to adapt the switch to your network :

Factory
N° Open Closed
setting
S4 Open
J7-1 Board address bit 1 = 1 Board address bit 1 = 0 Close
J7-2 Board address bit 2 = 1 Board address bit 2 = 0 Close
J7-3 Board address bit 4 = 1 Board address bit 4 = 0 Close
J7-4 Board address bit 8 = 1 Board address bit 8 = 0 Close
J7-5 Board address bit 16 = 1 Board address bit 16 = 0 Close
J7-6 Board address bit 32 = 1 Board address bit 32 = 0 Close
J7-7 Board address bit 64 = 1 Board address bit 64 = 0 Close

Address of the board :

Each board on the ring has a specific address. Each address must be single and included
between 1 and 127.
The address is equal to the sum of the « open bits ».
At the beginning address = 0
If J7-1 = open address = address + 1 if not address = address + 0
If J7-2 = open address = address + 2 if not address = address + 0
If J7-3 = open address = address + 4 if not address = address + 0
If J7-4 = open address = address + 8 if not address = address + 0
If J7-5 = open address = address + 16 if not address = address + 0
If J7-6 = open address = address + 32 if not address = address + 0
If J7-7 = open address = address + 64 if not address = address + 0
Example :
Address = 0
J7-1 = open address = address + 1
J7-2 = open address = address + 2
J7-3 = close address = address + 0
J7-4 = open address = address + 8
J7-5 = close address = address + 0
J7-6 = close address = address + 0
J7-7 = close address = address + 0
Address = 11

OPEN CLOSE
Hardware C264/EN HW/B30

MiCOM C264/C264C Page 29/34

Internal LED:
Some LED are used to indicate the state of the links.
The table below indicates the function of each LED :

LED
FUNCTION DESCRIPTION
number
L1 Receive RpEs
L2 Link RpEs
L3 Receive RsEp
L4 Link RsEp
L5 Link and activity port 1 Off : no connection
Green : link
Green + blink : link + activity
L6 Link and activity port 2 «
L7 Link and activity port 3 «
L8 Link and activity port 4 «
L9 Speed port 1 Off : 10Mbps Green : 100Mbps
L10 Speed port 2 «
L11 Speed port 3 «
L12 Speed port 4 «
L13 Address board bit 0 Only the first 4 bits are visualized
L14 Address board bit 1 «
L15 Address board bit 2 «
L16 Address board bit 3 «
L17 Number of repeter detected on the ring bit 0 Only the first 4 bits are visualized
L18 Number of repeter detected on the ring bit 1 «
L19 Number of repeter detected on the ring bit 2 «
L20 Number of repeter detected on the ring bit 3 «

Fault signal output:

The optical ring is monitored. If one link come down the default is announced by the
contacts:

Components side Pin State

1 Default Rp-Es

2 Common

1 2 3 3 Default Rs-Ep

Close if default
C0121ENa
C264/EN HW/B30 Hardware

Page 30/34 MiCOM C264/C264C

Switch management:
It is possible to manage the switch with the MDIO bus (J6)

Sub D 25 male

J2
8
1 9
MDC 2
3 11

4 18
19
20
21
22

C0122ENa

Ethernet cable type

Use data quality twisted pair shielded cable rated category 5 with standard RJ45 connectors.
The maximum cable length for 10/100BaseT(x) is typically 100 meters.
Ethernet Optical Fibre
The FO cable are connected to the corresponding FO elements. The connector type for the
multi mode fibre or single mode is ST.
Fibre Optic budget calculations
Optical power is expressed in Watts. However, the common unit of power measure is the
dBm and defined by the following equation: Power (dBm) = 10 log Power (mW) / 1 mW.
The following example shows the calculation of the maximum range for various types of
fibres

SWR200 SWR200

1
SWR200 SWR200

Patch Patch
Panel Panel

SWR200 SWR200

C0123ENa
Hardware C264/EN HW/B30

MiCOM C264/C264C Page 31/34

Fibre type Multi mode Single mode

62,5/125 micron 9/125 micron
Power coupled into - 19 dBm - 15 dBm
fiber
sensitivity - 31 dBm - 34 dBm

Example 1 : between two repeaters

Link budget 12 dB 19 dB
Connector loss (2) 0,8 dB 0,8 dB
Safety Margin 4 dB 4 dB
Allowed link attenuation 6,4 dB 13,4 dB
Typical cable attenuation 1 dB/km 0,4 dB/km
Maximum range 6,4 km 33 km

Example 2 : between two repeaters via patch panel

Link budget 12 dB 19 dB
Connector loss (6) 0,8 dB 0,8 dB
Patch loss (2) 2 dB 1 dB
Safety Margin 4 dB 4 dB
Allowed link attenuation -0,8 dB 8,2 dB
Typical cable attenuation 1 dB/km 0,4 dB/km
Maximum range 0 20 km

The values given above are only approximate ones. Always use cable and connector losses
as specified by the manufacturer.
C264/EN HW/B30 Hardware

Page 32/34 MiCOM C264/C264C

2.5.11 Extended communication Unit – ECU200

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

FIGURE 29 : MiCOM C264 – ECU200 MODULE

Hardware C264/EN HW/B30

MiCOM C264/C264C Page 33/34

2.5.12 Extended communication Unit – ECU201

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

FIGURE 30 : MiCOM C264 – ECU201 MODULE

2.6 Hardware tropicalisation
In option, the MiCOM C264/C264C hardware is available in a tropicalised version.
In this case, each board is covered by a dedicated varnish.
C264/EN HW/B30 Hardware

Page 34/34 MiCOM C264/C264C

BLANK PAGE
Connections C264/EN CO/B30

MiCOM C264/C264C

CONNECTIONS
Connections C264/EN CO/B30

MiCOM C264/C264C Page 1/30

CONTENT

1. SCOPE OF THE DOCUMENT 3

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. FITTING CAUTION 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 14
4.3 Digital Inputs module – DIU200 15
4.4 Digital Inputs module – DIU210 16
4.5 Digital Outputs module – DOU200 19
4.6 Circuit breaker Control Unit - CCU200 21
4.7 Analogue Input module – AIU201 23
4.8 Analogue Input module – AIU210 25
4.9 Transducerless Measurements Unit module –TMU200 27
4.10 Front panel 29
C264/EN CO/B30 Connections

Page 2/30 MiCOM C264/C264C

BLANK PAGE
Connections C264/EN CO/B30

MiCOM C264/C264C Page 3/30

1. SCOPE OF THE DOCUMENT

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.
C264/EN CO/B30 Connections

Page 4/30 MiCOM C264/C264C

2. CONNECTOR BLOCKS
2.1 I/O Connector Block
All the I/O connection uses a standard type of connector block with a 24-way and 5.08 mm
pitch.
The I/O connector block characteristics are the following:

Parameter Value
Continuous rating 10 A
Connection method Screw M3
Cable size 2.5 mm2
Connection pitch 5,08 mm
Isolation to other terminal and to earth 300 V basic insulation
Standards UL, CSA

TABLE 1 : I/O CONNECTOR BLOCKS

PIN

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

C0041ENa

FIGURE 1 : SAMPLE OF FEMALE CONNECTOR

NOTE: The connector is fixed with 2 screws M3 located on both vertical sides
of the connector.
Connections C264/EN CO/B30

MiCOM C264/C264C Page 5/30

2.2 CT/VT Connector Block

MiCOM C264 uses a standard MiDOS 28 connector block for transformer connection.
CT connection has 2 dual terminal groups, this allows dual rated transformer (1A/5A). Each
group has shorting contact to allow disconnection of CTs without damage.
The CT/VT connector block characteristics are the following:

Parameter Value
VT connection
Continuous rating 10 A
3 second rating 30 A
30 ms rating 250 A
Connection method Screw M4
Cable size 2 * 2.5 mm2
Isolation to other terminal and to earth 500 V basic insulation
CT connection
Continuous rating 20 A
10 second rating 150 A
1 second rating 500 A
Connection method Screw M4
Cable size 2 * 2.5 mm2 / 1 * 4 mm2
Isolation to other terminal and to earth 300 V basic insulation

TABLE 2 : CT/VT CONNECTOR BLOCK

1 2

3 4

5 6

7 8

9 10

11 12

13 14

15 16

17 18

19 20

21 22

23 24

25 26

27 28

C0042ENa

FIGURE 2 : STANDARD MIDOS 28 CONNECTOR

NOTE: The connector is fixed to the rack with 4 Phillips screws M4; 2 are
located on the top part and 2 on the bottom part.
C264/EN CO/B30 Connections

Page 6/30 MiCOM C264/C264C

2.3 Serial communications connections

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

MiCOM C264 (Slave) (Slave) (Slave)

Rear panel Relay or IED Relay or IED Relay or IED
RS485 connector

Rx Tx Gnd Rx Tx Gnd Rx Tx Gnd Rx Tx Gnd

120 Ohms 120 Ohms

Earthing Earthing
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.
Connections C264/EN CO/B30

MiCOM C264/C264C Page 7/30

MiCOM C264 MiCOM C264 (Slave) (Slave) (Slave)

Relay or IED Relay or IED Relay or IED

(Slave) (Slave) (Slave) (Slave)

Relay or IED Relay or IED Relay or IED Relay or IED

C0045ENa

FIGURE 5 : STAR NETWORK OR NETWORK WITH TEES – WRONG CONNECTIONS

NOTE: A “Star” or a network with “Stubs (Tees)” is not recommended as
reflections within the cable may result in data corruption.

Wiring recommendation for RS422

Master (c264) Slave(IED)
TA(+) R+
TB(-) R-
RA(+) T+
RB(-) T-

2.4 Optical communications connections

WARNING OF LASER RAYS!

Non–observance of the following measure can result in death, personal injury or substantial
property damage.
Do not look directly into the fibre-optic elements!
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").
C264/EN CO/B30 Connections

Page 8/30 MiCOM C264/C264C

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.
Connections C264/EN CO/B30

MiCOM C264/C264C Page 9/30

3. FITTING CAUTION
3.1 Earthing
MiCOM C264/C264C must be connected to the earth according to the EN60950 - 2.5.11
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

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.
C264/EN CO/B30 Connections

Page 10/30 MiCOM C264/C264C

First example: MiCOM C264/C264C fitted without metallic cubicle.

Mechanical Earth

MiCOM C264 - Rear panel

Mechanical Earth

Power sypply cables to stick to earthing plan

Signal cables to stick to earthing plan

C0048ENb

FIGURE 8 : FIRST EXAMPLE OF EARTHING PLAN

Connections C264/EN CO/B30

MiCOM C264/C264C Page 11/30

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

Stick as near as
Stick as near as
possible to the MiCOM C264 possible to the
cubicle metallic
or other device cubicle metallic
surface
surface

Earth
Auxiliary power

Earth
Digital boundary
connector

Power Analogue
connector boundary
connector
C0049ENb

FIGURE 9 : SECOND EXAMPLE OF CABLE FITTING

C264/EN CO/B30 Connections

Page 12/30 MiCOM C264/C264C

4. CONNECTION DIAGRAMS FOR EACH I/O BOARDS

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

Case Port N°1 Port N°2

1 RS232 RS232
2 RS485 RS232
3 RS232 RS422
4 RS485 RS422
5 RS232 RS485
6 RS485 RS485

TABLE 3 : BASE LEGACY PORTS (PORTS N°1 / N°2) - CAPABILITIES

Connector description:

Pin n° Signal
1 Redundancy relay 2 - NO contact
2 Redundancy relay - common 1-2
3 Redundancy relay 1 - NO contact
4 Watchdog relay - NO contact
5 Watchdog relay - NC contact
6 Watchdog relay - common
7 Redundancy input - 1+
8 Redundancy input - common 1 / 2
9 Redundancy input - 2+
10
11
12 RS232: RxD RS485 : B - Port 1
13 GND - Port 1
14 RS232: TxD RS485 : A - Port 1
15 GND - Port 2
16 RS232: CTS - Port 2
17 RS232: RxD RS485 B RS422: TB - Port 2
18 RS232: TxD RS485 A RS422: TA - Port 2
19 RS232: RTS RS422: RB - Port 2
20 RS422: RA - Port 2
21 RS232: DCD - Port 2
22 Voltage input: Gnd Gnd
23 Voltage input: AC/DC (+)
24 Voltage input: AC/DC (•)

TABLE 4 : BIU241 BOARD - CONNECTOR DESCRIPTION

Connections C264/EN CO/B30

MiCOM C264/C264C Page 13/30

Block diagram:

Power auxiliary supply BIU241

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 1
14 TXD / TA
#
15
GND
16 RS232/
CTS
17 RS422
RXD / TB Serial
18 TXD / TA RS485
RTS / RB link 2
19
RA #
20 DCD
21
22
V aux Power
23 +

24 - supply
-

C0050ENc

FIGURE 10 : BIU241 BOARD – BLOCK DIAGRAM

C264/EN CO/B30 Connections

Page 14/30 MiCOM C264/C264C

4.2 Central Processing Unit – CPU260

In base, this board includes the 10/100BaseT Ethernet interface (RJ45 connector).
Optionally, this board includes:

• The 100BaseF Ethernet interface (ST connector),

• The IRIG-B interface,

• Two non-insulated RS232 interfaces (DB9 male connector)

The external modules ECU200/ECU201 convert non-insulated RS232 into optical
link/insulated RS485 or RS422.
The DB9 connectors description:

1 CD
2 RX
3 TX
4 5V ( for ECU20x supply)
5 ground
6 Not used
7 RTS
8 CTS
9 Not used

Connector DB 9

5
1

6 9

1
5

9 6
C0152ENa

FIGURE 11 : OPTIONAL LEGACY PORTS (PORTS N°3 / N°4) - DESCRIPTION

Connections C264/EN CO/B30

MiCOM C264/C264C Page 15/30

The ECU201 module has a 5 wires female connector.

1 TA (+)
2 TB (-)
3 Ground
4 RA (+)
5 RB (-)

TABLE 5 : ECU201 - DESCRIPTION

For RS422 connection : TA(+), TB(-), RA(+), RB(-) are used. Jumper S1 must be set
For RS485 connection: only TA(+) and TB(-), are used. Jumper S1 must not be set.

4.3 Digital Inputs module – DIU200

The Digital Input module (DIU200) provides 16 optically insulated digital inputs (with 1
common for 2DI).
The DIU200 board is equipped with a 24-way 5.08 mm pitch connector.
Connector description:

Pin N°. Signal

1 Digital Input 1+
2 Digital Input 2+
3 Common Digital Input 1 / 2
4 Digital Input 3+
5 Digital Input 4+
6 Common Digital Input 3 / 4
7 Digital Input 5+
8 Digital Input 6+
9 Common Digital Input 5 / 6
10 Digital Input 7+
11 Digital Input 8+
12 Common Digital Input 7 / 8
13 Digital Input 9+
14 Digital Input 10+
15 Common Digital Input 9 / 10
16 Digital Input 11+
17 Digital Input 12+
18 Common Digital Input 11 / 12
19 Digital Input 13+
20 Digital Input 14+
21 Common Digital Input 13 / 14
22 Digital Input 15+
23 Digital Input 16+
24 Common Digital Input 15 / 16

TABLE 6 : DIU200 BOARD - CONNECTOR DESCRIPTION

C264/EN CO/B30 Connections

Page 16/30 MiCOM C264/C264C

Block diagram:

Digital Input Unit DIU210

board

PIN Signal inputs

1 VIN VIN
+ DI1 + DI2
- -
2 - -
3

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

C0056ENb

FIGURE 12: DIU200 BOARD – BLOCK DIAGRAM

NOTE: Different types of DIU200 boards, depending on the wetting voltage
for the DI points, exist in the MiCOM C264/C264C catalogue. Special
caution is on the wetting voltage for the DI, there is no hardware
disabusing 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 Inputs module – DIU210

The Digital Input module (DIU210) provides 16 optically insulated digital inputs (with 1
common for 2DI).
The DIU210 board is equipped with a 24-way 5.08 mm pitch connector.
Connector description:
Connections C264/EN CO/B30

MiCOM C264/C264C Page 17/30

Pin N°. Signal

1 Digital Input 1+
2 Digital Input 2+
3 Common Digital Input 1 / 2
4 Digital Input 3+
5 Digital Input 4+
6 Common Digital Input 3 / 4
7 Digital Input 5+
8 Digital Input 6+
9 Common Digital Input 5 / 6
10 Digital Input 7+
11 Digital Input 8+
12 Common Digital Input 7 / 8
13 Digital Input 9+
14 Digital Input 10+
15 Common Digital Input 9 / 10
16 Digital Input 11+
17 Digital Input 12+
18 Common Digital Input 11 / 12
19 Digital Input 13+
20 Digital Input 14+
21 Common Digital Input 13 / 14
22 Digital Input 15+
23 Digital Input 16+
24 Common Digital Input 15 / 16

TABLE 7 : DIU210 BOARD - CONNECTOR DESCRIPTION

C264/EN CO/B30 Connections

Page 18/30 MiCOM C264/C264C

Block diagram:

Digital Input Unit DIU210

board

PIN Signal inputs

1 VIN VIN
+ DI1 + DI2
- -
2 - -
3

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

C0056ENb

FIGURE 13: DIU210 BOARD – BLOCK DIAGRAM

NOTE: There is only one type of DIU210 board, including all wetting voltages
between 24 and 220V AC/DC
Connections C264/EN CO/B30

MiCOM C264/C264C Page 19/30

4.5 Digital Outputs module – DOU200

The Digital Outputs Unit (DOU200) board provides 10 outputs (10 DO) using relays.
The DOU200 board is equipped with a 24-way 5.08 mm pitch connector.
Connector description:

Pin N°. Signal

1 Digital output 1 +
2 Digital output 1 -
3 Digital output 2 +
4 Digital output 2 -
5 Digital output 3 +
6 Digital output 3 -
7 Digital output 4 +
8 Digital output 4 -
9 Digital output 5 +
10 Digital output 5 -
11 Digital output 6 +
12 Digital output 6 -
13 Digital output 7 +
14 Digital output 7 -
15 Digital output 8 +
16 Digital output 8 -
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 8 : DOU200 BOARD - CONNECTOR DESCRIPTION

C264/EN CO/B30 Connections

Page 20/30 MiCOM C264/C264C

Block diagram:

D igital Output U nit DOU200

board

PIN Signal outputs

1
2 DO 1
3

4 DO 2
5

6 DO 3
7

8 DO 4
9

10 DO 5
11

12 DO 6
13

14 DO 7
15

16 DO 8
17

18

19

20
DO 9
21

22

23
DO 10
24

C0057ENb

FIGURE 14 : DOU200 BOARD – BLOCK DIAGRAM

Connections C264/EN CO/B30

MiCOM C264/C264C Page 21/30

4.6 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.
The DOU200 board is equipped with a 24-way 5.08 mm pitch connector.
Connector description:

Pin N°. Signal

1 Digital Input 1+
2 Digital Input 2+
3 Common Digital Input 1 / 2
4 Digital Input 3+
5 Digital Input 4+
6 Common Digital Input 3 / 4
7 Digital Input 5+
8 Digital Input 6+
9 Common Digital Input 5 / 6
10 Digital Input 7+
11 Digital Input 8+
12 Common Digital Input 7 / 8
13 Digital Output 1 B
14 Digital Output 1 A
15 Common Digital Output 1 - 2 A
16 Digital Output 2 A
17 Digital Output 2 B
18 Common Digital Output 1 - 2 B
19 Digital Output 3 B
20 Digital Output 3 A
21 Common Digital Output 3 – 4 A
22 Digital Output 4 A
23 Digital Output 4 B
24 Common Digital Output 3 - 4 B

TABLE 9 : CCU200 BOARD - CONNECTOR DESCRIPTION

C264/EN CO/B30 Connections

Page 22/30 MiCOM C264/C264C

Block diagram:

Circuit breaker CCU 200

Control Unit
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 15 : CCU200 BOARD – BLOCK DIAGRAM

NOTE: Different types of CCU200 boards, depending on the wetting voltage
for the DI points, exist in the MiCOM C264/C264C catalogue. Special
caution is on the wetting voltage for the DI, there is no hardware
disabusing on the connector.
Range: Version A01 for 24VDC, A02 for 48/60 VDC, A03 for 110/125VDC
and A03 for 220 VDC
Connections C264/EN CO/B30

MiCOM C264/C264C Page 23/30

4.7 Analogue Input module – AIU201

The Analogue input module (AIU201) provides 4 independent Analogue inputs (4AI).
The AIU201 board is equipped with a 24-way 5.08 mm pitch connector.
Connector description:

Pin N°. Signal

1 Analogue Input 1+ (voltage)
2 Analogue Input 1-(voltage)
3 Analogue Input 1+(current)
4 Analogue Input 1-(current)
5 Insulated Ground 1
6 Ground
7 Analogue Input 2+ (voltage)
8 Analogue Input 2-(voltage)
9 Analogue Input 2+(current)
10 Analogue Input 2-(current)
11 Insulated Ground 2
12 Ground
13 Analogue Input 3+ (voltage)
14 Analogue Input 3-(voltage)
15 Analogue Input 3+(current)
16 Analogue Input 3-(current)
17 Insulated Ground 3
18 Ground
19 Analogue Input 4+ (voltage)
20 Analogue Input 4-(voltage)
21 Analogue Input 4+(current)
22 Analogue Input 4-(current)
23 Insulated Ground 4
24 Ground

TABLE 10 : AIU201 BOARD - CONNECTOR DESCRIPTION

C264/EN CO/B30 Connections

Page 24/30 MiCOM C264/C264C

Block diagram:

Analogue Input U nit AIU210

board

PIN Signal inputs

1 + U
2 - mA AI 5
#
3 + U
4 - mA AI 1
#
5 Insulated
GND
6
GND
7 + U
8 - mA AI 6
#
9 + U
10 - mA AI 2
#
11 Insulated
GND
12
GND
13 + U
14 - mA AI 7
#
15 + U
16 - mA AI 3
#
17 Insulated
GND
18
GND
19 + U
20 - mA AI 8
#
21 + U
22 - mA AI 4
#
23 Insulated
GND
24
GND

C0059ENc

FIGURE 16 : AIU201 BOARD – BLOCK DIAGRAM

Connections C264/EN CO/B30

MiCOM C264/C264C Page 25/30

4.8 Analogue Input module – AIU210

The Analogue input module (AIU210) provides 8 independent Analogue inputs (8AI).
The AIU210 board is equipped with a 24-way 5.08 mm pitch connector.
Connector description:

Pin N°. Signal

1 Analogue Input 5+ (current)
2 Analogue Input 5-( current)
3 Analogue Input 1+(current)
4 Analogue Input 1-(current)
5 Insulated Ground 1
6 Ground
7 Analogue Input 6+ (current)
8 Analogue Input 6-( current)
9 Analogue Input 2+(current)
10 Analogue Input 2-(current)
11 Insulated Ground 2
12 Ground
13 Analogue Input 7+ (current)
14 Analogue Input 7-( current)
15 Analogue Input 3+(current)
16 Analogue Input 3-(current)
17 Insulated Ground 3
18 Ground
19 Analogue Input 8+ (current)
20 Analogue Input 8-( current)
21 Analogue Input 4+(current)
22 Analogue Input 4-(current)
23 Insulated Ground 4
24 Ground

TABLE 11 : AIU210 BOARD - CONNECTOR DESCRIPTION

C264/EN CO/B30 Connections

Page 26/30 MiCOM C264/C264C

Block diagram:

Analogue Input U nit AIU210

board

PIN Signal inputs

1 + U
2 - mA AI 5
#
3 + U
4 - mA AI 1
#
5 Insulated
GND
6
GND
7 + U
8 - mA AI 6
#
9 + U
10 - mA AI 2
#
11 Insulated
GND
12
GND
13 + U
14 - mA AI 7
#
15 + U
16 - mA AI 3
#
17 Insulated
GND
18
GND
19 + U
20 - mA AI 8
#
21 + U
22 - mA AI 4
#
23 Insulated
GND
24
GND

C0059ENc

FIGURE 17 : AIU210 BOARD – BLOCK DIAGRAM

Connections C264/EN CO/B30

MiCOM C264/C264C Page 27/30

4.9 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).
Connector description:

Pin N°. Signal

1 Current Input 5A - N1
2 Current Input 5A – N2
3 Current Input 1A – N1
4 Current Input 1A – N2
5 Current Input 5A – C1
6 Current Input 5A – C2
7 Current Input 1A – C1
8 Current Input 1A – C2
9 Current Input 5A – B1
10 Current Input 5A – B2
11 Current Input 1A – B1
12 Current Input 1A – B2
13 Current Input 5A – A1
14 Current Input 5A – A2
15 Current Input 1A – A1
16 Current Input 1A – A2
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 12 : TMU200 BOARD - CONNECTOR DESCRIPTION

C264/EN CO/B30 Connections

Page 28/30 MiCOM C264/C264C

Block diagram:

Transducerless 1A Transducerless 5A
Current and Voltage TMU 200 Current and Voltage TMU 200
U nit board U nit board

Transducerless Transducerless
current inputs current inputs
PIN PIN
N1

1 2 1 2 N2
N1

3 4 N2 3 4
C1
5 6 5 6 C2
C1

7 8 C2 7 8
B1

9 10 9 10 B2
B1
11 12 B2 11 12
A1
13 14 13 14 A2
A1

15 16 A2 15 16

17 18 17 18
Transducerless Transducerless
voltage inputs voltage inputs
19 20 19 20
U1 U1

21 22 U2 21 22 U2
V1 V1
23 24 V2 23 24 V2
W1 W1

25 26 W2 25 26 W2
N1 N1
27 28 N2 27 28 N2

C0060ENb

FIGURE 18 : CT/VT BOARD – BLOCK DIAGRAM

Connections C264/EN CO/B30

MiCOM C264/C264C Page 29/30

4.10 Front panel

The front panel includes a non-insulated RS232 interface dedicated for maintenance and
settings.
The properties of the serial link (DB9 female connector) for the maintenance dialogue are:

• Baud rate: 19200

• Databits: 8

• Parity: No

• Stop bit: 1

• Control Xon/Xoff
Connector description:

5 4 3 2 1

9 8 7 6
C0061ENa

FIGURE 19 : 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 13 : FRONT PANEL - CONNECTOR DESCRIPTION

C264/EN CO/B30 Connections

Page 30/30 MiCOM C264/C264C

MiCOM C264C Front panel:

RS232 port: This serial port is

dedicated to a PC for
Tunnelling.

C0062ENb

FIGURE 20 : MiCOM C264C FRONT PANEL

Installation C264/EN IN/B30

MiCOM C264/C264C

INSTALLATION
Installation C264/EN IN/B30

MiCOM C264/C264C Page 1/44

CONTENT

1. SCOPE OF THE DOCUMENT 3

2. REQUIREMENT 4
2.1 MiCOM C264 4
2.2 Personal Computer 5
2.3 Communication wiring 5

3. DELIVERY RECEPTION 6
3.1 Packing inspection and opening 6
3.2 Delivery form checking 6

4. MECHANICAL MOUNTING 7
4.1 Rack mounting 7
4.2 Panel mounting 7

5. WIRING INSTALLATION 8
5.1 General wiring 8
5.2 Power supply wiring 8
5.3 I/O board wiring 8
5.4 Networks wiring 8

6. MICOM C264 POWER UP 10

7. MICOM C264 SOFTWARE INSTALLATION 11

7.1 Tools installation on the PC 11
7.1.1 Recommendation for the PC performances 11
7.1.2 Installation on the PC 11
7.2 Connection between the PC and C264 16
7.2.1 Without Ethernet Switch 16
7.2.2 With Ethernet Switch 16
7.3 Settings to enter 17
7.4 Input new settings 17
7.5 C264 Software installation 18
7.6 C264 Software upgrade 18

8. DOWNLOADING DATABASE 19
8.1 Database download with CMT 19
8.1.1 Loading DB under CMT 19
8.1.2 Download DB onto C264 19
C264/EN IN/B30 Installation

Page 2/44 MiCOM C264/C264C

8.2 Database download with SMT 19

8.2.1 Loading DB under SMT 19
8.2.2 Download DB onto C264 19
8.2.3 Switch to downloaded data base 19

9. AFTER COMPUTER INSTALLATION 20

10. PROTECTION KEY 21

11. OPTIONAL INSTALLATION 22

11.1 External master clock connection 22
11.2 Printer installation 22

12. CMT ONLINE HELP 23

12.1 INTRODUCTION 23
12.1.1 Scope 23
12.2 Pacis Computer Maintenance Tool (Cmt) overview 23
12.2.1 Generalities 23
12.2.2 Launching the software 23
12.2.3 Cmt main window 24
12.2.4 Operations performed by Cmt buttons 27
Installation C264/EN IN/B30

MiCOM C264/C264C Page 3/44

1. SCOPE OF THE DOCUMENT

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.
C264/EN IN/B30 Installation

Page 4/44 MiCOM C264/C264C

2. REQUIREMENT
MiCOM C264 boot setting and software installation is carried out using a Windows PC with
common utilities and serial/Ethernet link to the computer.
The PACiS CD-ROM System installation is needed to run the C264’s install software on the
Host PC.
2.1 MiCOM C264
The MiCOM C264 needs at least

• CPU board CPU260

• Power board BIU241

• Backplane FBP242 (for MiCOM C264C) or FBP280 (for MiCOM C264)

The BIU241 needs to be correctly wired to its voltage level as described in chapter C264/EN
CO (Connections). Before any operational voltage is applied the shield wiring should be
checked following rules of chapter C264/EN SA (Safety Handling).
The CPU260 has default factory parameters.
NOTE: The computer needs to be installed with the software that allows
booting in flash. Installation or reinstallation of BOOTPROM software
in PROM is described in C264/EN MF Maintenance chapter, and out
of scope of this chapter.
Before starting installation the following information is required:

• Computer IP address

• Computer alias name

Both parameters are also defined in computer database. If parameters inside database differ
from actual setting then the UCA2 communication with other PACiS equipment will not be
possible.
Installation C264/EN IN/B30

MiCOM C264/C264C Page 5/44

2.2 Personal Computer

A Personal Computer is used for setting and download. The required Windows operating
system is WinNT or Win2000 .
The PC hardware requirement is:

• Ethernet port 10 Mb/s or 100 Mb/s

• 100 Mb of free space on hard disk

The PC software's needed is:

• Computer package named Computer_X.YZ.exe ( X.YZ is the computer version)

2.3 Communication wiring
The link between PC and MiCOM C264 is Ethernet.
For a direct connection (without Ethernet Switch) between the PC and the MiCOM C264, a
crossed wire is required.
C264/EN IN/B30 Installation

Page 6/44 MiCOM C264/C264C

3. DELIVERY RECEPTION
Delivery reception is composed of:

• Packing inspection and opening

• Delivery form checking

• Feeling up commissioning
3.1 Packing inspection and opening
On receipt of the unit, inform the delivery agent if there is any signs of damage.
Check the box for documentation, or computer hardware option added in the delivery form
like ribbon, screws, port extension etc.
3.2 Delivery form checking
The delivery form is based on the order form issued from CORTEC. It lists computer type,
boards (with supply, serial numbers and position in the rack) and options.
Verify that the composition of the device is as ordered.
Computer is delivered with the required connectors.
Installation C264/EN IN/B30

MiCOM C264/C264C Page 7/44

4. MECHANICAL MOUNTING
The chapter C264/EN HW gives the size of MiCOM C264 rack, the fixation diameters and
their position.
If electric screwdriver is used the torque limitation should be set to the small diameters of the
screws.
The MiCOM C264 can be mounted in racks or panel.
4.1 Rack mounting
MiCOM C264 may be rack mounted using single tier rack frames (our part number is
FX0021 001):

These frames have been designed to have dimensions in accordance with IEC60297 and
are supplied pre-assembled ready to use.
The two horizontal rails of the rack frame have holes drilled at approximately 26mm intervals
and C264 cases are attached via their mounting flanges using M4 Taptite self-tapping
screws with captive 3 mm thick washers to ensure a good earth contact (our part number is
ZB5865250).
It is possible to install two C264C side by side on the assembly panel or one C264.
Ensure that the computers are earthed, using the screw terminal on the rear of the unit.
4.2 Panel mounting
MiCOM C264 can be flush mounted into panels using M4 Taptite self-tapping screws with
captive 3 mm thick washers to ensure a good earth contact (our part number is
ZB5865250).
Alternatively tapped holes can be used if the panel has a minimum thickness of 2.5 mm.
Where several MiCOM C264 are to be mounted in a single cut-out in the panel, it is advised
that they are mechanically grouped together horizontally and/or vertically to form rigid
assemblies prior to mounting in the panel.
NOTE: It is not advised that MiCOM C264 are fastened using pop rivets as
this will not allow the device to be easily removed from the panel in the
future if repair is necessary.
C264/EN IN/B30 Installation

Page 8/44 MiCOM C264/C264C

5. WIRING INSTALLATION
Wiring has to be prepared before installation. The MiCOM C264 is delivered with required
connectors for I/O boards and Ethernet switches. The wire diameters stated in chapter
C264/EN CO are mandatory. Tighten the screws in a cross pattern (e.g. top left, then bottom
right etc), take care not to over torque the screws.
5.1 General wiring
Only two wires can be screwed together on any one MiCOM connector. The AC and DC
analogues, digital signal, and communication wires should use separate shielded cable.
From a practical point of view the power supply of each computer should have a switch
(MCB, link, or fuse) to turn off the power during installation and commissioning tests.
The MiCOM C264 description sheet describes the type of board Installed on each slot (C, D
etc.) It is very important to use it to correctly plug the connectors.
Connection diagrams of the C264 are given in chapter C264/EN CO. Wires should be
connected with the connector unplugged. Each wired signal has to be tested before plugging
and fixing the connectors. The connectors have to be fixed on the C264 case with the
screws available at each extremity of the connector.
5.2 Power supply wiring
The BIU connector wiring is vital as it provides the power supply. Power voltage should be
tested and checked to BIU reference defined in chapter C264/EN HW to ensure that supply
is compliant to BIU voltage.
The power has to be switched off before plugging in the connector.
5.3 I/O board wiring
Several DIU, CCU, BIU board voltage are available for Digital Input. Check that the DIU
voltage as stated on the delivery form matches with the nominal signal input before plugging
connector to the computer.
DOU, and CCU 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 only, should be fitted
(120 ohms for RS422 and RS485).
Copper Ethernet network have to stay inside a cubicle. Fibre optic has to be used between
cubicles.
For the use of SWR200, the optical ring as to be connected as follows:
Installation C264/EN IN/B30

MiCOM C264/C264C Page 9/44

Rp Rp
Rp
Es Es
Es SWR200
SWR200 SWR200
Rs Rs
Rs
Ep Ep
Ep

C0145ENa
C264/EN IN/B30 Installation

Page 10/44 MiCOM C264/C264C

6. MiCOM C264 POWER UP

The MiCOM C264 as delivered has the following installed:

• bootrom start-up software

• Factory Start-up Setting

Before powering up the computer all the DI/DO board connectors should be disconnected.
Tests are described in the C264/EN CM chapter to check that the computer with its factory
settings have not suffered damage during transport.
Installation C264/EN IN/B30

MiCOM C264/C264C Page 11/44

7. MiCOM C264 SOFTWARE INSTALLATION

While you have insert the PACiS CD-ROM System installation into your CD-drive you will
find the install software of the computer into the following directory:
\System\Delivery\PACiS Va.b.c\C264 VX.YZ (Va.b.c is the PACiS system version, X.YZ is
the computer version).
Install the Computer_X.YZ.exe on your PC.
It is recommended to use default installation parameters. This will install CMT (Computer
Maintenance Tool), FTP server and set the C264 application in a directory accessible by the
MiCOM C264.
Connect the MiCOM C264 and the PC on the same Ethernet switch or directly with a
crossed Ethernet wire.
7.1 Tools installation on the PC
The tools and C264 software is delivered on a CD-ROM, these software have to be installed
on a PC.
7.1.1 Recommendation for the PC performances

• At least Pentium 3 or similar

• At least 700MHz

• Windows 2000 or Windows NT

• At least 100 Mb fee space on hard disk

• A CD-ROM drive

• An Ethernet port
7.1.2 Installation on the PC
The software is in the C264/VX.YZ folder (X.YZ is the computer version).

• Insert the CD-ROM in the CD-drive

• Launch the Computer_X.YZ.exe file.

• During installation select parameters as detailed below:

C264/EN IN/B30 Installation

Page 12/44 MiCOM C264/C264C

Click on Next

Select I accept the agreement and click on Next

Installation C264/EN IN/B30

MiCOM C264/C264C Page 13/44

Choose the path to install the software but it is better to keep the default parameters.
Click on Next.

Click on Next
C264/EN IN/B30 Installation

Page 14/44 MiCOM C264/C264C

Click on Next

Click on Next
Installation C264/EN IN/B30

MiCOM C264/C264C Page 15/44

Click on Install

Click on Finish
C264/EN IN/B30 Installation

Page 16/44 MiCOM C264/C264C

7.2 Connection between the PC and C264

Connect the PC and the C264 via Ethernet following one of the following architecture.
7.2.1 Without Ethernet Switch

Crossed Ethernet
wire
PC C264

C0146ENa

The crossed Ethernet wire is as below:

Connector RJ-45 EIA/TIA-232

1 (connected to pin 8)
2 DTR
3 TxD
4 GND
5 GND
6 RxD
7 DSR
8 (connected to pin 1)

1 Wire colors T-568B:

8
1 ORANGE/
2 ORANGE
3 GREEN/
4 BLUE
5 BLUE/
6 GREEN
7 BROWN/
8 BROWN

Wire colors T-568A:

8 1
1 GREEN/
1 1
2 GREEN
2 2
3 ORANGE/
3 3
4 BLUE
4 4
5 BLUE/
5 5
6 ORANGE
6 6
7 BROWN/
7 7
8 BROWN
8 8
C0148ENa

7.2.2 With Ethernet Switch

Direct Ethernet
cables
PC C264

Ethernet Switch

C0147ENa

The crossed Ethernet wire is as below:

1 connected to 1, 2 connected to 2, etc
Installation C264/EN IN/B30

MiCOM C264/C264C Page 17/44

7.3 Settings to enter

The computer has a default factory IP address and alias, these need to be changed to the
application specific values.
The settings to enter are:

• host IP address: your maintenance laptop IP@

• target name: should be the Computer name defined by SCE for its database

• C264 IP address: should be the Computer IP address defined by SCE for its database
Other parameters should not be modified.
The following item describes how to modify the parameters.
7.4 Input new settings

− Launch PACiS FTPD server previously installed.

There is the following display on your PC desk:

− Launch CMT software previously installed.

There is the following display on your PC desk:

NOTE: CMT provides an online HELP. This Help is also included in the end of
this IN chapter.

− Access your C264 by select “Search computers” button

NOTE: If there is no computer in the list, it is perhaps due to the Ethernet
interface of your PC. Go into “file” in the top of the window and
“Network interface” to choose the right interface

− Select your MiCOM C264 in the list.

− Go into “Boot Parameters” Menu

− Select “Network boot” option

− Modify:

− “IP on Ethernet (e)“ and set the Ethernet address you have chosen for the MiCOM
C264

− “host IP (h)” and set the Ethernet address of the PC that supports CMT

− “target name (tn)” and set a name for the MiCOM C264

− Click on “Set Boot Parameters” button in order to send the new parameters to the
MiCOM C264.

− Select “Reboot Computer” in order to restart the C264. It will restart with the software
installed on the PC.
C264/EN IN/B30 Installation

Page 18/44 MiCOM C264/C264C

7.5 C264 Software installation

On the CMT application:

− Access your C264 by select “Search computers” button

− Select your MiCOM C264 in the list.

− Go into “Boot Parameters” Menu

− Select “flash boot” option

− Click on “Set Boot Parameters” button in order to take into account the new
parameters.

− Click on “ BootInstall ” Menu.

− Choose C264_cpu2 directory

− Click on “ Updatebootrom ”.

− Wait for the end of installation

− Click on “ Start bootInstall ”.

− Wait for the end of installation, MiCOM C264 installation takes around 1 minute.

− When it is finished restart your computer by clicking on “reboot computer” to take into
account the new parameters and software.
After the reboot the computer C264 will switch into maintenance mode. Computer is ready
for receiving the application database.
7.6 C264 Software upgrade
To upgrade a software, the sequence is quite identical with the CMT:

− Access your C264 by select “Search computers” button

− Select your MiCOM C264 in the list.

− Click on “ BootInstall ” Menu.

− Choose C264_cpu2 directory

− Click on “ Updatebootrom ”.

− Wait for the end of installation

− Click on “ Start bootInstall ”.

− Wait for the end of installation, MiCOM C264 installation takes around 1 minute.

− When it is finished restart your computer by clicking on “reboot computer” to take into
account the new parameters and software.
Installation C264/EN IN/B30

MiCOM C264/C264C Page 19/44

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 database.
SMT (System Management Tool) or CMT (Computer Maintenance Tool) are used to
download and switch the databases.
The use of SMT or CMT depends on the number of computers. For several computers on
the same Ethernet network, it is recommended to use SMT in order to insure database
coherency between computers.
8.1 Database download with CMT
8.1.1 Loading DB under CMT
First action is to copy the .zip database issued from SCE on your PC.
8.1.2 Download DB onto C264
On the CMT application:

− Access your C264 by select “Search computers” button

− Select your MiCOM C264 in the list.

− Go into “ Key and DB ” Menu

− click on “ Select a Data Base version” button, choose the bd.x.xx.zip file
corresponding to the database you want to use and click on “OK”

− Click on “ Download Data Base ” button, choose the “.adb” file of your computer and
click on “OK”

− When it is done, click on “ Switch Data Bases ” button, the MiCOM C264 computer
will restart on the database you have downloaded.
8.2 Database download with SMT
8.2.1 Loading DB under SMT
First action under SMT is to load the DB version. The DB is then stored on the hard disk and
prepared for communication (with communication setting).
The DB will appear in the database list, a right click allows to “set current” the DB, then to
send a “connect all”. SMT should then be communicating with the computer, if not
communication wiring and settings should be checked.
8.2.2 Download DB onto C264
Still using right buttons chose the “download all” option and wait for the acknowledgement of
a successful transfer.
8.2.3 Switch to downloaded data base
If no database has previously been installed then the database is automatically set to be the
running database. If there is a database already installed then the downloaded database will
become the standby database, in which case the new database will have to be switched to
make it the running database. In both cases it is necessary to reboot the computer to put the
database into running mode.
C264/EN IN/B30 Installation

Page 20/44 MiCOM C264/C264C

9. AFTER COMPUTER INSTALLATION

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

MiCOM C264/C264C Page 21/44

10. PROTECTION KEY

There is a software protection Key inside the MiCOM C264.
To verify the available functions, use the CMT application:

− Access the C264 by select “Search computers” button

− Select the MiCOM C264 in the list.

− Go into “Key and DB” Menu

− click on “Get computer key” button, a valid key number should be displayed with the
available functions.
If there is not a valid Key, then contact After Sales department of AREVA T&D EAI to have a
valid one. Before calling you need the serial number given into “Boot Parameters” Menu
and the needed functions among the following list :

− T104

− Serial SCADA links

− IED links

− ISaGRAF runtime

− Synchrocheck and voltage regulation

Once you have the Key, insert it into key box of “Key and DB” Menu and click on “Set
computer key” button. Then you should have a valid key.
C264/EN IN/B30 Installation

Page 22/44 MiCOM C264/C264C

11. OPTIONAL INSTALLATION

Optional hardware modules are:

• IRIG B connection

• Printer
11.1 External master clock connection
With the option of the CPU board, an external standard BNC connection is used to receive
external master clock synchronisation. The recommended external master clock is the hopf
6870 radio clock.
Installation should follow the standard rules of BNC cable installation including length limit
and optional 50 ohms termination.
For installation of the external master clock, refer to its documentation and to the summary in
PACiS system/EN IN chapter.
External IRIG B synchronisation should be configured in the computer database.
11.2 Printer installation
A printer can be installed permanently for the SOE, or temporally for
commissioning/maintenance use. Data labelling is defined with PACiS SCE.
The printer should be connected to either port 1,2,3 or port 4 of the computer.
If the port is on the BIU board, the board has to be configured for RS232 by using the correct
jumper configuration.
Furthermore, a configuration file (included in database) has to be installed onto the computer
with the printer communication parameters.
Installation C264/EN IN/B30

MiCOM C264/C264C Page 23/44

12. CMT ONLINE HELP

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

Page 24/44 MiCOM C264/C264C

12.2.3 Cmt main window

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

12.2.3.1 The menu: File, Tools, and Help

12.2.3.1.1 File menu
File menu contains two submenus: Network Interface and Quit.
Network interface submenu ( F2 )

It selects the Networks Interface board used by the PC to access computer Network.
A chooses window opens and proposes Network interface board existing on your PC.
Select the board you want to use and click OK, or close the window using Windows close
mechanism
For a PC with only one Ethernet board the right board is automatically selected
example:

• MS TCP Loop back interface : (not useable by CMT)

• 3Com 3C90x Ethernet Adapter:

• 3Com Ether Link PCI:

• AT-2500 NDIS Series 4.0 driver:

• NdisWan Adapter : (not useable by CMT)

The selection is saved in Registry
Quit submenu (CTRL + q)
It's used to exit the software
Installation C264/EN IN/B30

MiCOM C264/C264C Page 25/44

12.2.3.1.2 Tools menu

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

The selected color is saved in Registry.

C264/EN IN/B30 Installation

Page 26/44 MiCOM C264/C264C

12.2.3.1.3 Help menu

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

12.2.3.2 The "Search computers" button

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

Just click left on a computer to select it.

Installation C264/EN IN/B30

MiCOM C264/C264C Page 27/44

Each button is colored representing computer internal state :

application software running or normal : green
application software stopped : blue
Bootprom : red
The selected computer name, IP address, Type and serial number is shown in the top right
white box "Selected Computer:".

Each window can show 20 buttons, clicking the tab ( Next...) makes the next 20 computers
visible. A maximum of one hundred computers is possible.
12.2.3.3 The "Computer's list" button
The list of all the "responding" computers is displayed, with their name, IP address, Type and
serial number, without searching on network.
12.2.3.4 The left bar
It contains all the operations that can be performed on the selected computer:
Simply click on a button to launch the desired task.
Each operation is described in the next section of this manual.
12.2.4 Operations performed by Cmt buttons
12.2.4.1 Computer version
The output window software and database information from Cx6x computer:

• Version
• Database compatibility
• UCA2 agency version
• Isagraf software version
• Triangle software version
• creation date of the application software.
Information on the running database is also given ( if a database is running ...):

• device name
• device type
• model
• company
• description
• substation
• database name
• version
• path of the database.
• data base creation date and last setting date.
Information on the computer state :
ACTIVE or MAINTENANCE or INITIALIZATION or SIMULATION or STANDBY or
FAULTY or HALTED or STOPPED
C264/EN IN/B30 Installation

Page 28/44 MiCOM C264/C264C

12.2.4.2 Boot Parameter

"Boot Parameters" button shows current computer boot parameters.
Modifications of the values can be done for all the fields displayed in white box ("inet on
Ethernet", "host inet" and "target name").
The radio buttons "Network boot" and "Flash boot" and "Bootprom boot". These three
buttons automatically change the required fields in the boot line to make the computer boot
using FTP (Network ) or using its flash memory (Flash ) or stopped after boot (Bootprom ).

The normal mode is "Flash boot"

Ethernet Interface Type can be selected and saved in computer flash using the white choose
box "Ethernet interface".
possible selection :
[Composant FrontPage Enregistreur de résultats]

RJ45 auto detect is the default mode : auto negotiation between the computer and switch
"Get Boot parameters" button gets information reading computer flash memory.
Once the modifications are finished, the "Set boot Parameters" button has to be pressed in
order to apply the changes on the computer.
Modifications are saved in the flash memory of The CX6X
Modifications will be used only after the next reboot.
12.2.4.3 Key and Data base Management
"Key and DB" button shows the key and data base window management.
12.2.4.3.1 Key Management
Computer software utilization is limited by a software key mechanism.
Each computer is associated with a permission key. This window allows user to read "Get
computer key" or to update "Set computer key" the computer with a new key.
Keys are unique and associated to the computer Ethernet address.

Authorized functions are marked with a black radio button.

12.2.4.3.2 Data base Management
Installation C264/EN IN/B30

MiCOM C264/C264C Page 29/44

The data base part of the window is used to manage computer data base.
"Data base 1" shows the first data base version revision and its state "CURRENT" or
"STANDBY"
"Data base 2" shows the second data base version revision and its state "CURRENT" or
"STANDBY"
"Clean DB1" removes the first data base.
"Clean DB2" removes the second data base.
"Clean all DB" removes the first and the second data base.
"Switch data bases" switches the two data bases from "CURRENT" becomes
"STANDBY" and "STANDBY" becomes "CURRENT".
"Select a Data base version" with this button user can select a versioned system data base ,
generated by "System configurator" (S.C.E ).selecting this button opens a new window, type
file chooser, and user can select a "*.x.yy.zip" file.

Once the file "*.x.yy.zip" selected, the file is unzipped and his version revision x.yy is
memorized for the future download operation: "New DB version".
C264/EN IN/B30 Installation

Page 30/44 MiCOM C264/C264C

"Favorites" button gives access to the file system of your PC .

Once a data base version is selected user can download the "*.adb" file to computer using
"Download data base".
A file chooser window opens and propose the "*.adb" files compressed in the "*.x.yy.zip" file
and unzipped by using "Select a Data base version".

Clicking on "OK" will start download database process to computer.

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

12.2.4.4.2 Get computer date

This section reads time on computer ( local time).
Installation C264/EN IN/B30

MiCOM C264/C264C Page 31/44

12.2.4.4.3 Set date

This section select a time and date value from PC and sends it to computer.
"Set date" is used to modify the computer date and time. The current date and time are
taken from Windows on the operator PC and displayed. They can be changed if needed. The
"OK" button is used to confirm the changes and to update the settings on the computer.

Clicking "OK" sends time to computer, if the new time is accepted or not, this confirmation
window will open.
C264/EN IN/B30 Installation

Page 32/44 MiCOM C264/C264C

12.2.4.4.4 Set year

This section select a year value from PC and sends it to computer.
"Set year" acts like "Set date" but only the year is changed. It’s useful to set year on a new
computer because IRIG B does not contain the year information. The default value is taken
from Windows and can be changed. "OK" set the value on the computer.

Clicking "OK" sends time to computer, if the new year is accepted or not, this confirmation
window will open.

12.2.4.4.5 IRIG-B
This section reads IRIG B information from computer.
If IRIG-B interface is present on the CPU board :

If IRIG-B interface is not present on CPU :

Installation C264/EN IN/B30

MiCOM C264/C264C Page 33/44

12.2.4.4.6 Synchronism
This section reads synchronism information from computer.

12.2.4.5 Errors
The content of "/flash/systrap/index.txt" is displayed. It shows the number of errors since the
initialization of the index, the date and time of the last error and the name of the file
containing information on this error.

This file (containing the last systrap) is pre-selected in the "File to display" choose box.
On a CX6X the last tenth error files are archived, you can select one of this file using "File to
display" choose box
C264/EN IN/B30 Installation

Page 34/44 MiCOM C264/C264C

Once a file is selected you visualize it, clicking :

⇒ "Open" show the file on the output window.

⇒ "Print" sends the file to the Windows printer.

Installation C264/EN IN/B30

MiCOM C264/C264C Page 35/44

⇒ "Save as ..." save the file on the PC disk. Its open a new file chooser window.

Note that the file filename refers to the file "/flash/SYSTRAP/STxx.TXT" on the computer.
12.2.4.6 File Explorer
This section is designed like many FTP clients or files explorer.
The left part is an image of the local PC file system, the right one an image of the computer
file system.
C264/EN IN/B30 Installation

Page 36/44 MiCOM C264/C264C

12.2.4.6.1 Local PC Side ( Left )

On the PC-side , the default current directory is the latest selected directory ( value saved in
Registry )
Directories are displayed with a bold font. They can be browsed by simple clicks. The
content of the browser is automatically updated to reflect the new directory files or
subdirectories.
Files are shown with a normal font. To select a file, just simple clicks on it ( dark blue
background indicates the selection).
The top box "Change disk" list all the drives of the PC used as root for the browser.
A gray box show the current path or selected file ( bold).
12.2.4.6.2 Remote Computer Side ( Right )
On the right size, you first have to choose the root of the computer file system. /RAMDEV (
ramdisk ) and /flash ( flash memory ) are available. click on the "Change root" box.
a simple click on a directory shows its content and simple click on a file selects it ( dark
blue background indicates the selection).
For each file, its size and modification date is also displayed.
12.2.4.6.3 Download ( Left to Right Arrow )
To begin a transfer, use the two arrows between the two browsers:
The "Left to Right Arrow" download the file selected on the PC browser in the directory
selected on the computer.
Name is not changed, only files with DOS name format ( 8 . 3 character format ) can be
copied .Files is automatically overwritten on the computer if it's already exist.
The progress-meter shows the advancement of the transfer in yellow, write time on flash
memory is represented by a full red progress-meter
12.2.4.6.4 Upload ( Right to Left Arrow )
The "Right to Left Arrow" uploads a file. The file selected on the computer is uploaded on the
PC, in the current directory.
Name is not changed. Files is automatically overwritten on the computer if it's already exist.
The progress-meter shows the advancement of the transfer in yellow.
12.2.4.6.5 Delete
The "Delete" button delete the selected file on the computer file system.
A confirmation window open showing the full path of the file to be deleted and user can
confirm or cancel.
Installation C264/EN IN/B30

MiCOM C264/C264C Page 37/44

12.2.4.6.6 Format
The "Format" button erases and reformats the computer file system , all files are deleted.
This button is only useable wile computer is stopped or on boot mode.

A confirmation window opens and user have to confirm or cancel his click...

12.2.4.7 BootInstall
This function is equivalent to the BootInstall command, launched from a shell. It's
downloaded automatically a set of files mandatory for a Cx6x computer application.

The set of file is selected automatically by the user (u ) name of the boot info windows
( c264_cpu0, c264_cpu1, c264_cpu2, c364)
The left part is an image of the local PC file system.
C264/EN IN/B30 Installation

Page 38/44 MiCOM C264/C264C

12.2.4.7.1 Local PC Side ( Left )

On the PC-side , the default current directory is the latest selected directory ( value saved in
Registry )
Directories are displayed with a bold font. They can be browsed by simple clicks. The
content of the browser is automatically updated to reflect the new directory files or
subdirectories.
Files are shown with a normal font. To select a file, just simple clicks on it ( dark blue
background indicates the selection).
The top box "Change disk" list all the drives of the PC used as root for the browser.
A gray box show the current path ( bold). If a file is selected, only the path is used, the
filename is ignored.
12.2.4.7.2 Start BootInstall
If the computer is not in the mode : STOPPED or BOOT

After a confirmation window , the BootInstall begins.

The upper progress-meter, show the advancement file by file ( yellow for the transfer and red
for write ).
The lower progress-meter, shows the advancement of the global process (yellow).
the "Start BootInstall" button is deleted after each used , you have to re-click on "BootInstall"
button and reselect a directory
12.2.4.7.3 Abort BootInstall
The "Abort BootInstall" button can stop the file transfer process. Click is memorized and stop
the download after a full file transfer, it can't stop inside a file transfer. No confirmation is
needed.
Installation C264/EN IN/B30

MiCOM C264/C264C Page 39/44

12.2.4.7.4 Update bootrom

The "Update bootrom" button is used to update the bootrom part of the computer flash (
software executed after a restart) . Computer must be in stop mode to allow this function.

First user must select a directory witch contains "bootrom.flh" file. A confirmation is
requested.

The file is downloaded first to computer /RAMDEV/bootrom.flh and after copied in flash.
Be sure of your choice, if a bad file is selected the computer will not reboot at next
restart.
12.2.4.8 Telnet
This button launches the default Windows Telnet client on the operator PC. Telnet is
connected to the selected computer.

It can be used to easily get a shell on the computer, in order to perform tasks that Cmt can't
handle.
the "logout" command or the Windows close can be use to terminate the session.
As Telnet is launched independently of Cmt, multi sessions on two or more computers are
possible.
Telnet used TCP/IP stack and the computer have to be accessible from the PC in this
mode ...
C264/EN IN/B30 Installation

Page 40/44 MiCOM C264/C264C

12.2.4.9 Event log storage

This section reads or changes event log storage and printer configuration from or to
computer.
12.2.4.9.1 Event log storage management

Function Information
"Function information" gives information about event log storage mechanism.
Installation C264/EN IN/B30

MiCOM C264/C264C Page 41/44

Enable/Disable event log storage

"Disable event log storage" (default state) disables event log storage mechanism. The state
is updated in function information window.

"Enable event log storage" (default state) enables event log storage mechanism. The state is
updated in function information window.

tGet stored event log

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

and open a "notepad" window

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

C264/EN IN/B30 Installation

Page 42/44 MiCOM C264/C264C

12.2.4.9.2 Printer management

Get Printer Parameter

"Get Printer Parameter" reads printer configuration.

Device can be one of :

"no printer"
"Frontal RS232" : subd 9 points on front panel ( setting or shell connector )
"/Scc1/tty" : port 1 on BIU
"/Scc2/tty" : port 2 on BIU
"/Scc3/tty" : port 3 on Cpu260 board ( rear side)
"/Scc4/tty" : port 4 on Cpu260 board ( rear side)
Control can be one of:
"0 (none)" no control
"1 (Xon/Xoff)" software control
"2 (Hard)" hardware control
"3 (Both)" software and hardware control
Printer mode
"printer mode" changes printer mode from NORMAL ( prints events marked as printable in
configuration) to OFF ( don't print any events even if printable in configuration ) or DEBUG
(print all events even if they are not marked printable in configuration).

Event log mode

"Event log mode" changes event log mode from NORMAL ( saves events marked as "log"
in configuration) to DEBUG (saves all the events even if they are not marked "log" in
configuration).
Installation C264/EN IN/B30

MiCOM C264/C264C Page 43/44

12.2.4.10 Stop Computer

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

12.2.4.11 Reboot Computer

This operation reboots the selected computer. A confirmation is needed.
C264/EN IN/B30 Installation

Page 44/44 MiCOM C264/C264C

BLANK PAGE
Application C264/EN AP/B30

MiCOM C264/C264C

APPLICATION
Application C264/EN AP/B30

MiCOM C264/C264C Page 1/396

CONTENT

1. SCOPE OF THE DOCUMENT 5

2. REQUIREMENTS 6

3. MiCOM C264 COMPUTER CONFIGURATION SCOPE 7

3.1 General PACiS system configuration 7
3.2 MiCOM C264 Computer configuration in PACiS system configuration 7
3.3 Sparing object 8

4. DEFINING MiCOM C264 COMPUTER CONFIGURATION IN SYSTEM

ARCHITECTURE 9
4.1 Setting general system configuration relevant to MiCOM C264 Computers 9
4.2 Adding a MiCOM C264 Computer in the system architecture 12
4.2.1 Kind of MiCOM C264 Computers 12
4.3 Setting specific parameterisation of MiCOM C264 Computer 14
4.3.1 Configuring binary input (BI) filtering 15
4.3.2 Configuring measurement acquisition and transmission 17
4.3.3 Configuring counter acquisition 17
4.3.4 Configuring MiCOM C264 Computer internal fault characteristics 18
4.3.5 Locating MiCOM C264 Computer in a substation (mandatory) 18
4.3.6 Defining a MiCOM C264 Computer as system master clock 19
4.3.7 Defining a redundant MiCOM C264 Computer (optional) 19
4.4 Adding MiCOM C264 Computer hardware components 22
4.4.1 Adding boards 22
4.4.2 Setting specific attributes to MiCOM C264 Computer’s boards 23
4.4.3 Adding extra communication channels to CPU board 25
4.4.4 Configuring a communication channel 26
4.4.5 Configuring an AI channel 27
4.4.6 Adding a printer 27
4.5 Networking MiCOM C264 Computer on the station-bus network 31
4.5.1 Connecting MiCOM C264 Computer to others station-bus sub-systems 31
4.5.2 Defining addressing mapping of station-bus network 34
4.5.3 Addressing datapoint on station-bus network 46
4.6 Networking IED on MiCOM C264 Computer legacy network 46
4.6.1 Creating a legacy network of IED 46
4.6.2 Defining addressing mapping of legacy IED 56
4.6.3 Addressing datapoint on IED legacy network 73
C264/EN AP/B30 Application

Page 2/396 MiCOM C264/C264C

4.7 Networking SCADA on MiCOM C264 Computer SCADA network 74

4.7.1 Creating a SCADA network 74
4.7.2 Defining addressing mapping of SCADA legacy network 82
4.7.3 Addressing datapoint on SCADA legacy network 97
4.8 Defining wave record file management 98
4.8.1 Defining management of disturbance file for IED 98
4.8.2 Defining T103 IED extra information for disturbance file 100
4.8.3 Defining management of wave record file for MiCOM C264 Computer CT/VT board 103
4.9 Defining MiCOM C264 Computer klaxon 111
4.10 Setting system information for MiCOM C264 Computer components 112
4.10.1 Setting general system information of MiCOM C264 Computer 113
4.10.2 Setting system information of board 118
4.10.3 Setting system information of legacy IED 119
4.10.4 Setting system information of serial printer 120
4.10.5 Setting system information of SCADA network 121

5. DEFINING DATAPOINT 122

5.1 Creating datapoint 122
5.1.1 Overview of binary input processing 123
5.1.2 Defining SPS datapoint 124
5.1.3 Defining DPS datapoint 128
5.1.4 Defining MPS datapoint 134
5.1.5 Overview of measurement processing 137
5.1.6 Defining MV datapoint 146
5.1.7 Defining TPI datapoint 150
5.1.8 Defining Counter datapoint 155
5.1.9 Overview of control sequence processing 160
5.1.10 Defining SPC datapoint 178
5.1.11 Defining DPC datapoint 182
5.1.12 Defining SetPoint datapoint 186
5.2 Linking datapoint to profile 193
5.2.1 Defining a SPS profile 195
5.2.2 Defining a DPS profile 199
5.2.3 Defining a MPS profile 205
5.2.4 Defining a MV profile 211
5.2.5 Defining a Counter profile 217
5.2.6 Defining a SPC profile 221
5.2.7 Defining a DPC profile 225
5.2.8 Defining a SetPoint profile 229
5.3 Defining MiCOM C264 Computer local archiving of datapoint events 232
5.4 Defining MiCOM C264 Computer local archiving of datapoint alarms 232
5.5 Defining MiCOM C264 Computer local logging of datapoint events and alarms 232
Application C264/EN AP/B30

MiCOM C264/C264C Page 3/396

5.6 Defining acquisition source for input datapoints 232

5.6.1 Acquiring input datapoint via input channels 232
5.6.2 Acquiring input datapoint via IED legacy network 238
5.6.3 Acquiring input datapoint via non-PACiS UCA2 communicant IED 239
5.6.4 Producing input datapoint 239
5.7 Defining control source for output datapoints 241
5.7.1 Controlling output datapoint via output channels 241
5.7.2 Controlling output datapoint via IED legacy network 244
5.7.3 Controlling output datapoint via non-PACiS UCA2 communicant IED 245
5.7.4 Producing output datapoint 246

6. DEFINING MiCOM C264 COMPUTER CONFIGURATION IN

ELECTRICAL ARCHITECTURE 247
6.1 Defining electrical topology 247
6.1.1 Defining Site 249
6.1.2 Defining Substation 249
6.1.3 Defining Voltage level 254
6.1.4 Defining Bay 256
6.1.5 Defining Module 262
6.2 Defining Synchrocheck function 273
6.2.1 Completing circuit-breaker definition for synchrocheck 273
6.2.2 External synchrocheck behaviour 277
6.2.3 Internal synchrocheck behaviour 282
6.2.4 Creating a synchrocheck function 288
6.3 Defining Auto-recloser built-in function 295
6.3.1 Auto-recloser behaviour 295
6.3.2 Creating an auto-recloser function 299
6.4 Defining Tap changer built-in function 306
6.4.1 Tap changer behaviour 306
6.4.2 Creating a tap changer function 310
6.5 Defining AVR built-in function 312
6.5.1 AVR behaviour 312
6.5.2 Creating an AVR function 327
6.6 Defining electrical regulation by user function 341
6.6.1 Defining a FBD fast automation 341
6.6.2 A "DPC" or "SPC" 347
6.6.3 Defining a group 353
6.6.4 Controlling xPC by xPS change of state 355
6.6.5 Producing DPS from 2 SPS 356
6.6.6 Defining interlocking 356
6.6.7 Defining an automatic/manual dependency 358
C264/EN AP/B30 Application

Page 4/396 MiCOM C264/C264C

7. DEFINING MiCOM C264 COMPUTER LOCAL HMI 359

7.1 Defining bitmap table 359
7.2 Defining MiCOM C264 Computer workspace 361
7.2.1 Settings LHMI labels 362
7.2.2 Creating a workspace 362
7.3 Defining MiCOM C264 Computer bay mimic 363
7.3.1 Creating a MiCOM C264 Computer bay mimic 363
7.3.2 Defining static part: line, bitmap, fixed text 366
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation,
transformer representation 369
7.3.4 Assigning MV to bay mimic 376
7.4 Displaying datapoint status with Led 377

8. ANNEX A: COUPLING SCE DATA MODEL AND ISaGRAF 378

8.1 ISaGRAF presentation 378
8.1.1 ISaGRAF workbench description 378
8.1.2 Directories structure of ISAGRAF 379
8.1.3 Uploaded files towards the target 380
8.2 Usage of SCE datapoints in ISaGRAF 381
8.2.1 Hierarchical relationship: Function management DPs. 381
8.2.2 Server relationship 381
8.2.3 Client relationship 382
8.2.4 Access rights summary table 382
8.2.5 Equivalence of SCE datapoint in ISaGRAF 383
8.2.6 ISaGRAF dictionary data structure 384
8.2.7 Prototype and usage of PACiS function for ISaGRAF 387
Application C264/EN AP/B30

MiCOM C264/C264C Page 5/396

1. SCOPE OF THE DOCUMENT

The present document is a MiCOM C264/C264C computer chapter of the documentation
binder. This document is intended to present you how to configure the MiCOM C264
Computer. It is the chapter Application (AP) of this Product.
C264/EN AP/B30 Application

Page 6/396 MiCOM C264/C264C

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 MiCOM C264 Computer into an existing system you need to have the
mapping of the system (IP address, Network names of equipment…).
To generate a template, for an existent UCA2 C264 Computer, see the chapter of the SCE
product.
Application C264/EN AP/B30

MiCOM C264/C264C Page 7/396

3. MiCOM C264 COMPUTER CONFIGURATION SCOPE

3.1 General PACiS system configuration
To define a complete PACiS system, three aspects should be taken into account.
The first one is the system topology. It consists of device composition that manages the
customer’s electrical process. Generally, this part of furniture is relevant to AREVA and
corresponds to AREVA system process definition to respond customer’s needs.
The second one is the electrical topology. It consists of the customer’s electrical process
definition in term of typed electrical devices (transformer, disconnector, circuit-breaker…)
that are connected each other through busbars or lines. Generally, this part of furniture is
relevant to the customer.
The third one is the graphical topology. It consists of the mimic and their graphical animation
descriptions that appear at substation control points (operator interface) and bay control
points (MiCOM C264 Computer local HMI).
When creating a new configuration using SCE, these 3 topologies are automatically
instantiated via root objects:

− A ‘Site’ object for the electrical topology, containing one ‘Substation’ object

− A ‘Scs’ object for the system topology, containing one ‘Station network’ object (Scs is
an abbreviation of Substation Control System)

− A ‘Graphic’ object for the graphical topology.

FIGURE 1 : GENERAL ARCHITECTURE OF A PACiS CONFIGURATION IN SCE

3.2 MiCOM C264 Computer configuration in PACiS system configuration
In PACiS global system configuration, MiCOM C264 Computer is concerned by the 3
topologies:

− System topology (Scs) : MiCOM C264 Computer is a direct sub-component of the

Ethernet network used for communication at station bus level.

− Electrical topology (Site): MiCOM C264 Computer manages bays and relevant
modules or substation information.

− Graphical topology (Graphic): MiCOM C264 Computer can own an LCD display used
for animated graphical bay panel representation and others list panels
C264/EN AP/B30 Application

Page 8/396 MiCOM C264/C264C

3.3 Sparing object

At SCE level, A spare object is an object having its spare attribute set to true. The
configuration of this object and of its spare attribute are the same as for any other object and
attribute. Any object can be spare and particularly those concerning MiCOM C264 Computer
configuration.
Spare objects are not provided to the generator tools, respecting the following rules :

− An object O2, not spare, linked directly or not to a spare composite parent object O1,
is considered as spare.

O1 (Spare = Yes)

O2 (Spare = No)
S0387ENa

− A relation defined on an object O1, not spare, and linked to a spare object O2, is
considered as a relation without link.

O1 (Spare = No)

link
Relation O2 (Spare = Yes)
S0388ENa
Application C264/EN AP/B30

MiCOM C264/C264C Page 9/396

4. DEFINING MiCOM C264 COMPUTER CONFIGURATION IN SYSTEM

ARCHITECTURE
4.1 Setting general system configuration relevant to MiCOM C264 Computers
System configuration is done at Scs root. It is relevant to some general behaviour of PACiS
devices.
It concerns those specific attributes:

− Common labels used for control acknowledgement, time quality logging, alarm
management logging, MiCOM C264 Computer board management;

− Alarm management characteristics (alarm processing type, audibility delays, alarm

clearing mode per gravity basis);

− And those specific relations:

− Designation of the master clock device in the system. This system device gives the
time reference to all others devices through the station-bus network.

− Designation of elementary action rights by default used by system datapoints of the

Scs tree.

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

As system device, MiCOM C264 Computer can be master clock of the system and is always
located in a substation.
Some attributes of Scs objects concern all the MiCOM C264 Computers defined under the
station network. Hereafter, are listed these attributes:
1. Time zone used for timestamp information
2. MiCOM C264 Computer behaviour on DOU failure (control refused by faulty board /
MiCOM C264 Computer goes in faulty mode)
3. Local HMI password by default
4. Default board labels and status
5. Control acknowledgement labels used for order logging
C264/EN AP/B30 Application

Page 10/396 MiCOM C264/C264C

(1)

(2)

(3)

(4)

(unused at
computer
level)

C0161ENa
Application C264/EN AP/B30

MiCOM C264/C264C Page 11/396

(5)

(unused at
computer
level)

C0162ENa

(unused at
computer
level)

(6)

C0163ENa

FIGURE 2 : MiCOM C264 COMPUTER PARAMETERISATION AT GENERAL SYSTEM LEVEL

At MiCOM C264 Computer level, default alarm processing type is not significant, because
alarm processing is always ‘data basis’ for MiCOM C264 Computer.
Audibility features are not applicable to MiCOM C264 Computer configuration.
C264/EN AP/B30 Application

Page 12/396 MiCOM C264/C264C

4.2 Adding a MiCOM C264 Computer in the system architecture

4.2.1 Kind of MiCOM C264 Computers
There are two models of MiCOM C264 Computers: C264 and C264C.
The C264 is a large size MiCOM C264 Computer (80TE) and C264C is the compact one
(40TE). The height for the both MiCOM C264 Computers is 4U.
The different kinds of MiCOM C264 Computer have the following features:

Type Width Mandatory hardware Bus width Input/Output

C264C 40TE BIU with 2 serial ports 4/6 free slots DIU, DOU,
CPU with 2 optional serial ports CCU, TMU, AIU
(only 4 if TMU
GHU with optional LCD and with
board is present)
leds
C264 80TE BIU with 2 serial ports 14/15 free slots DIU, DOU,
CPU with 2 serial ports optional CCU, TMU, AIU
(only 14 if TMU
GHU with optional LCD and with
board is present)
leds

An addition of a MiCOM C264 Computer definition is done under SCE via the “Object entry”
area at Ethernet network level by clicking on mouse’s right button as the following:

FIGURE 3 : ADDING A MiCOM C264 COMPUTER

Default components of MiCOM C264 Computer
When you add from the “Objects Entry” view, for example a MiCOM C264 Computer you will
obtain the following sub-tree of the MiCOM C264 Computer definition with the default
components as follow:
Application C264/EN AP/B30

MiCOM C264/C264C Page 13/396

(1)

(2)

(3)

(4)

FIGURE 4 : DEFAULT COMPONENTS OF THE MiCOM C264 COMPUTER

1. Binder ‘Hardware’, that groups all defined boards and printers of the MiCOM C264
Computer (see 4.4 Adding MiCOM C264 Computer hardware components)
2. Binder ‘System infos’, that groups all general system datapoints of the MiCOM C264
Computer (see chapter 4.10 Setting system information for MiCOM C264 Computer
components)
3. ‘PLC’ object for Programming Logic Chart, that corresponds to ISaGRAF and PSL
project directory (see chapter
4. ‘UCA2 Mapping’ object, that describes the station-bus network addressing mapping of
datapoints managed by the MiCOM C264 Computer (see chapter 4.5 Networking
MiCOM C264 Computer on the station-bus network)
C264/EN AP/B30 Application

Page 14/396 MiCOM C264/C264C

4.3 Setting specific parameterisation of MiCOM C264 Computer

When adding a MiCOM C264 Computer on Ethernet network, some of its attributes must be
set and verified. Hereafter are listed these attributes (same list for C264 or C264C).

(1)

(2)

(3)

(4)

FIGURE 5 : GENERAL ATTRIBUTES

1. Name used for logging, alarms, …
2. Date format for local HMI
3. Indicates if the MiCOM C264 Computer is synchronised through IRIG B. The relation
at Scs level “Has for master clock” defines which device is the master clock in the
system. A master clock MiCOM C264 Computer is necessary synchronised through
IRIG B.
4. MiCOM C264 Computer network alias name and TCP/IP address
Configuration rules and checks

• The "TCP/IP address" value of a device, must be unique among all the devices per
Ethernet Network (except for OI server and OI client).

• The "network name" value of a device, must be unique among all the devices per
Ethernet Network (except for OI server and OI client).
Application C264/EN AP/B30

MiCOM C264/C264C Page 15/396

4.3.1 Configuring binary input (BI) filtering

There exist two types of input signal handling :

• Debouncing:
The start transition is signalled with the correct time, the following changes within the
debounce time are ignored. The range of the debounce time is 0..20 ms (with a 1 ms
step).
The event is time tagged at the instant of the first transition.

Debouncing time

t0 t1
C0164ENa

FIGURE 6 : DEBOUNCING

• Filtering:
The transition is only signalled if the signal is stable for minimum as long as the
filtering time. The range of the filtering time is 0-20 ms (with a 1 ms step). The filtering
is allowed only if the debouncing is applied (i.e. the filtering cannot be applied if there
is no debouncing before).
The event is time tagged at the instant of the first transition.

Filtering time

Debouncing
time

t0 t1 t2
C0127ENa

FIGURE 7 : FILTERING
A value of 0 means that no filter is applied : a change of state is validated as soon as it is
detected.
Three couple of delays (debouncing / filtering) are defined :

• one for all Digital Input which will be used as Binary Input

• one for all Digital Input which will be used as Digital Measurements

• one for all Digital Input which will be used as counters

C264/EN AP/B30 Application

Page 16/396 MiCOM C264/C264C

(1)

(2)

(3)

FIGURE 8 : SETTING BI FILTERING

1. Debouncing delay: debouncing time in ms, range [0..20] by step of 1 ms
2. Filtering delay in ms range [0..20] by step of 1ms
3. Toggling delays are defined as the following:
A digital input (DI) is said to be toggling if its state has changed more than N times in a given
period of time T1.
A toggling DI returns in the normal state if its state has not changed within another period of
time T2.
N (toggling transition number), T1 (toggling delay) and T2 (toggling end delay) are parameters
determined at configuration time on a per MiCOM C264 Computer basis.
Configuration rules and checks

• If the attribute "debouncing delay" is set to 0 value, then the attribute "filtering delay"
must be set to 0 value.
Application C264/EN AP/B30

MiCOM C264/C264C Page 17/396

4.3.2 Configuring measurement acquisition and transmission

(1)

(2)

(3)

(4)

FIGURE 9 : MEASURMENTS VALUES ATTRIBUTES

1. Debouncing and filtering delays: used for digital measurements (see 4.3.1 Configuring
binary input (BI) filtering for details)
2. Analogue measurements acquired on AIU board: acquisition samples ranges for long
scanning ([500..10000] by 500 ms) and short scanning ([100..1000] by 100 ms). For
each channel of AIU board, short or long scan period should be chosen (refer to
chapter 4.4.5 Configuring an AI channel).
3. Acquisition on TMU board with CTVT fundamental 50 or 60 Hz (number of harmonics
is fixed to 16)
4. Short transmission period on station bus ([0..60000] by 100 ms) and long transmission
period given by a multiple of the short period ([0..600]x short transmission period).
Configuration rules and checks

• If the attribute "debouncing delay" is set to 0 value, then the attribute "filtering delay"
must be set to 0 value.
4.3.3 Configuring counter acquisition

(1)

FIGURE 10: COUNTER ATTRIBUTES

1. Debouncing and filtering delays: used for digital counters (see 4.3.1 Configuring binary
input (BI) filtering for details)
Configuration rules and checks

• If the attribute "debouncing delay" is set to 0 value, then the attribute "filtering delay"
must be set to 0 value.
C264/EN AP/B30 Application

Page 18/396 MiCOM C264/C264C

4.3.4 Configuring MiCOM C264 Computer internal fault characteristics

(1)

FIGURE 11: MISCALLENEOUS ATTRIBUTES

1. Number of software faults allowed in a given period else the MiCOM C264 Computer
remains in HALT mode. MiCOM C264 Computer reboots automatically as long as it
does not reach the ‘fault max number’ in the ‘fault detection time’ period. When this
criteria is reached, MiCOM C264 Computer remains in HALT mode.
4.3.5 Locating MiCOM C264 Computer in a substation (mandatory)
As said in chapter 4.1 Setting general system configuration relevant to MiCOM C264
Computers, each system device has to be located in a specific substation. This is done by
entering the mandatory relation (1) “is located in:“ for each system device, especially MiCOM
C264 Computers.

(1)

FIGURE 12: LOCATING MiCOM C264 COMPUTER IN A SUBSTATION

Application C264/EN AP/B30

MiCOM C264/C264C Page 19/396

4.3.6 Defining a MiCOM C264 Computer as system master clock

As said in chapter 4.1 Setting general system configuration relevant to MiCOM C264
Computers, only one system device can be master clock for the system. This is done by
entering the mandatory relation (1) “has for master clock:“ at Scs level. Only a MiCOM C264
Computer can be defined as system master clock.

(1)

FIGURE 13: DEFINING A MiCOM C264 COMPUTER AS SYSTEM MASTER CLOCK

4.3.7 Defining a redundant MiCOM C264 Computer (optional)
To define a redundant MiCOM C264 Computer:

• Create the main MiCOM C264 Computer, considered as master one

• Via the contextual menu of the MiCOM C264 Computer, run “Create backup” (1)
Then:

• An extra MiCOM C264 Computer (considered as slave one) is automatically created

with an implicit relation of backup between the 2 MiCOM C264 Computers.

• Extra relations ‘has for UCA2/IEC server’ are automatically created between the 2
MiCOM C264 Computers.

• Once the backup MiCOM C264 Computer has been created, its attributes and
constitution are locked for updating and follows the main MiCOM C264 Computer
ones. The only exceptions are its short and long names and network identification (IP
address and network name) that must be correctly updated.
To finalise redundant MiCOM C264 Computer configuration, an extra system datapoint
‘redundancy mode’ has to be added in ‘System infos’ binder of the main MiCOM C264
Computer. UCA2 addressing of this datapoint is required and automatically done during its
creation (see chapter 4.5.2 Defining addressing mapping of station-bus network for details
about UCA2). Do not forget to configure a relevant SPS profile for ‘redundancy mode’ SPS
datapoint (refer to chapter 5 DEFINING DATAPOINT)
C264/EN AP/B30 Application

Page 20/396 MiCOM C264/C264C

(1)

FIGURE 14: DEFINING A REDUNDANT MiCOM C264 COMPUTER (CREATION ACTION)

Slave co mputer once

created after manual
updating of its short and
long names, and IP
characteristics

Constitution of the slave

computer is locked for
updating (gray aspect)

• Automatic creat ion of

‘backup’ relat ion between
the 2 computers
• Automatic relation of
‘station-bus client/server’
relation between the 2
computers

C0166ENa

FIGURE 15: DEFINING A REDUNDANT MiCOM C264 COMPUTER (ONCE CREATED)

Application C264/EN AP/B30

MiCOM C264/C264C Page 21/396

FIGURE 16: ADDING ‘REDUNDANCY MODE’ DATAPOINT TO THE MAIN MiCOM C264 COMPUTER
C264/EN AP/B30 Application

Page 22/396 MiCOM C264/C264C

4.4 Adding MiCOM C264 Computer hardware components

4.4.1 Adding boards
PACiS MiCOM C264 Computers are composed of boards, responding to specific functions:

• DIU200-210 - Digital input boards with 16 digital input channels:

- digital and counter acquisition
- digital measurement acquisition

• AIU201 - Analogue input boards with 4 analogue input channels:

- analogue measurement acquisition

• AIU210 - Analogue input boards with 8 analogue input channels:

- analogue measurement acquisition

• TMU200 - CT and VT input boards with 4 CT and 4 VT input channels:

- ct/vt sampling acquisition
- MV computations based on acquired samples

• DOU200 - Digital output boards with 10 digital output channels:

- execution of single or dual, transient or permanent commands
- setting of digital setpoints

• CCU200 - Mixed digital 8 input and 4 output boards with digital input and output
channels (take good care the DO 4,5,6,7 are defined but not used):
- Circuit breaker Control Unit

• CPU260, BIU241 - CPU and communication boards with communication channels (or
communication ports)

• GHU200 - Graphical panel boards with led channels

MiCOM C264 Computer hardware definition is done in SCE by adding typed boards below
MiCOM C264 Computer object. Some boards can be automatically created at MiCOM C264
Computer’s creation when mandatory (CPU260, GHU200, BIU241). Implicit typed channel
creations are done at board’s creation.
Linking datapoint to channels (see chapter 5 DEFINING DATAPOINT) does datapoint wiring.
An addition of a board definition is done under SCE via the “Object entry” area by clicking on
mouse’s right button as the following:

FIGURE 17: ADDING A MiCOM C264 COMPUTER BOARD

Application C264/EN AP/B30

MiCOM C264/C264C Page 23/396

Configuration rules and checks

Slots and boards in a C264 MiCOM C264 Computer

A B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
BIU CPU

• Slots from 1 to 14 may contain a board of the following types : AIU201, AIU210,
DOU200, DIU20x or CCU20x

• Slot 15 may contain 1 TMU200 board or 1 board of the above types.

• If a TMU200 is present, then the maximum count of boards must be ≤ 14; else the
maximum count of boards must be ≤ 15
Slots and boards in a C264C MiCOM C264 Computer

A B 1 2 3 4 5 6
BIU CPU

• Slots from 1 to 4 may contain a board of the following types : AIU201, AIU210,
DOU200, DIU20x or CCU20x

• Slots 5, 6 may contain 1 TMU200 board or 2 boards of the above types.

• If a TMU200 is present, then the maximum count of boards must be ≤ 4; else the
maximum count of boards must be ≤ 6
4.4.2 Setting specific attributes to MiCOM C264 Computer’s boards
4.4.2.1 Setting common attributes to MiCOM C264 Computer board
Whatever the kind of board, the physical board number attribute (2) must be updated.
It is not significant for stand-alone board type (CPU, BIU, TIU, and GHU).
Short and long name attributes of boards (1) must also be updated for correct logging and
alarm discrimination concerning board status datapoint.

(1)

(2)

FIGURE 18 : BOARD GENERAL ATTRIBUTES

Configuration rules and checks

• Per board type (AIU201, AIU210, DOU200, DIU20x, CCU20x), the "physical board
number" attribute values must begin from 0, be unique and contiguous.
C264/EN AP/B30 Application

Page 24/396 MiCOM C264/C264C

4.4.2.2 Setting specific features of GHU200 board

For GHU board, the specific attribute ‘HMI type’ (1) has to be set:

• ‘Simple’, if GHU board without LCD is used,

• ‘Complete’, if not.

(1)

FIGURE 19 : GHU200 BOARD SPECIFIC ATTRIBUTES

NOTE: The value ‘Old’ for ‘HMI type’ must not be used. It is still proposed for
maintenance reason.
For complete HMI, the extra relation ‘has for workspace’ (1) must be
filled at board level. For details about MiCOM C264 Computer
workspace, refer to chapter Defining MiCOM C264 Computer
workspace.

(1)

FIGURE 20: DEFINING WORKSPACE FOR COMPLETE GHU200 BOARDFOR MiCOM C264
Computer LED configuration, refer to chapter 7.4 Displaying datapoint status with Led.
Configuration rules and checks

• If the value of the "HMI type" attribute is "Simple", then "Led#4" must not be used (no
relation link from "Led#4" to a Datapoint)

• If the value of the "HMI type" attribute is different from "Complete", then the relation
"has for workspace" must not be linked.
Application C264/EN AP/B30

MiCOM C264/C264C Page 25/396

4.4.2.3 Setting specific attributes of TMU200 board

For TMU200 board, the following attributes have to be set for correct CT/VT computation of
extra measurements:
1. Electrical network topology (star or delta)
2. The reference phase (phase A, B or C)
3. The side where the reference phase is located (line or busbar)
4. The nominal current and voltage values.
Extra attributes are reserved for future use.

(1)

(2)

(3)

(4)

FIGURE 21 : TMU200 BOARD SPECIFIC ATTRIBUTES

If reference phase signal is absent, values transmitted by TMU board are set to invalid.
4.4.3 Adding extra communication channels to CPU board
Depending on CPU type, 2 extra communication channels can be added for a CPU260
board from SCE object entry available at CPU260 board level.

FIGURE 22: ADDING COMMUNICATION CHANNELS

At CPU260 board level, the frontal RS232 port is mandatory and automatically created at
board creation (see Figure 24 : CONFIGURING A COMMUNICATION CHANNEL).
C264/EN AP/B30 Application

Page 26/396 MiCOM C264/C264C

4.4.4 Configuring a communication channel

A communication channel is a physical port available on CPU or the BIU board at their
creation (see chapter 4.4.1 Adding boards) or manually added as option (see chapter 4.4.3
Adding extra communication channels to CPU board).
A communication channel can be used exclusively for:
1. Communication with a IED legacy network (see chapter 4.6.1.1 Adding a legacy
network),
2. Communication with a SCADA network (see chapter 4.7.1.1 Adding a SCADA
network),
3. Communication with a serial printer (see chapter 4.4.6 Adding a printer)

(1)

(2)

mandatory frontal port

(3)

C0167ENa

FIGURE 23 : USAGE OF COMMUNICATION CHANNEL

Once used by a communication link, the physical port has to be set relatively to the
communication link characteristics:
1. kind of port (RS232 or RS485)
2. Transmission parameters
Application C264/EN AP/B30

MiCOM C264/C264C Page 27/396

(1)

(2)

FIGURE 24 : CONFIGURING A COMMUNICATION CHANNEL

4.4.5 Configuring an AI channel
An AI channel is an analogue input available on AIU201 and AIU210 boards at their creation
(see chapter 4.4.1 Adding boards). AI channels are used for analogue measurement
acquisition (for details see chapter 5.1.5.3 Analogue measurement acquisition)

implicit AI#0 to
AI#3 channels
creation on
AIU200 board

C0168ENa

FIGURE 25 : USAGE OF ANALOGUE CHANNELS

Once used by a MV, the AI has to be set relatively to the acquisition characteristics (for
meaning see chapter 5.1.5.3 Analogue measurement acquisition):
1. Sensor range
2. Acquisition period (refer to chapter 4.3.2 Configuring measurement acquisition and
transmission)

(1)

(2)

FIGURE 26 : CONFIGURING AN AI CHANNEL

4.4.6 Adding a printer
SCE data modelling describes printers used in PACiS system for ‘sequence of events’ and
log book functions at operator interface level and MiCOM C264 Computer level.
C264/EN AP/B30 Application

Page 28/396 MiCOM C264/C264C

A printer at MiCOM C264 Computer level must be a serial one connected to a

communication channel of the MiCOM C264 Computer.
To create a MiCOM C264 Computer printer:

• Add a serial printer from object entry available at MiCOM C264 Computer level,

• Update its ‘has for communication port’ relation (1) and its attribute ‘printer control’ (2).

FIGURE 27: ADDING A SERIAL PRINTER

(2)

(1)

FIGURE 28: UPDATING THE COMMUNICATION PORT RELATION FOR A SERIAL PRINTER
To control the way logging is managed and formatted on a serial printer, updating printer
attributes is necessary:
1. Page size
2. Buffer size
3. Number of events to suppress when buffer is saturated
Application C264/EN AP/B30

MiCOM C264/C264C Page 29/396

4. Rank of the different columns used for printing formats

(1)

(2)

(3)

FIGURE 29: MANAGING THE BUFFER OF A SERIAL PRINTER

Configuration rules and checks

• The following constraint must be respected : "buffer size" > "nb of events to suppress
when saturated"
Hereafter an extract of logging that illustrates the different columns used for printing formats:

origine

time stamp object name

chronology object message

C0169ENa

FIGURE 30: THE DIFFERENT COLUMNS USED FOR PRINTING FORMATS

C264/EN AP/B30 Application

Page 30/396 MiCOM C264/C264C

(4)

FIGURE 31: DEFINING PRINTING FORMATS OF A SERIAL PRINTER

Configuration rules and checks

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

Application C264/EN AP/B30

MiCOM C264/C264C Page 31/396

4.5 Networking MiCOM C264 Computer on the station-bus network

MiCOM C264 Computer connection to the station-bus is implicitly done by adding the
MiCOM C264 Computer hierarchically to the Ethernet network (see chapter 4.2 Adding a
MiCOM C264 Computer in the system architecture) and by setting the IP characteristic of the
MiCOM C264 Computer (see 4.3 Setting specific parameterisation).
4.5.1 Connecting MiCOM C264 Computer to others station-bus sub-systems
To transmit information between PACiS sub-systems, UCA2 protocol is used.
The data modelling of UCA2 protocol is based on client-server architecture. Each UCA2
communicant PACiS sub-system (OI server, PACiS MiCOM C264 Computer, and telecontrol
gateway) owns a UCA2 mapping of data which it is server of. A PACiS sub-system is server
of a datapoint if it manages it, that is to say it produces its real-time value (in case of input
datapoint such as status, measurement, counter) or executes its real-time controls (in case
of output datapoint such as binary controls and setpoints).
To connect a MiCOM C264 Computer (A) to a specific UCA2 communicant sub-system (B)
on the station-bus, an extra relation ‘has for UCA2/IEC server’ must be created for (A) and
point to (B). That means MiCOM C264 Computer (A) is client of sub-system (B) and can
access to data managed by the sub-system (B), i.e. read relevant real-time values from (B)
and send real-time controls to (B).

FIGURE 32: CONNECTING MiCOM C264 COMPUTER TO OTHERS STATION-BUS SUB-SYSTEMS

C264/EN AP/B30 Application

Page 32/396 MiCOM C264/C264C

When adding the ‘has for UCA2/IEC server’ relation to MiCOM C264 Computer (A), a
specific attribute of the relation, modelling/goose usage (1), can be set to precise the way
data are transmitted from server (B) to MiCOM C264 Computer (A). There are three
possibilities:

• Data model only (or report mode only),

• Goose only,

• Data model and goose.

Basically, the Report mode is used to transmit filtered data for displaying, printing and
archiving. The Goose mode is used to transmit data as soon as possible after their
acquisition and as quickly as possible, for automation purpose.
Goose transmission must be used if MiCOM C264 Computer (A) uses BIs served by MiCOM
C264 Computer (B), for ISaGRAF, FBD or interlock computation (refer to chapter 6.6
Defining electrical regulation by user function).
During a loss of communication between a client and a server, all server BIs are set to
UNKNOWN on the client.
Configuration rules and checks

• A Client must not be linked to the same Server through multiple relations "has for
UCA2/IEC server".
Report based mode
Via its UCA2 address, a BI (see chapter 5.1.1 Overview of binary input processing) can be
configured to be transmitted in Report mode. In this mode, a confirmed change of status is
spontaneously transmitted to the subscribers.
The BI information transmitted in a report is :

• the state and quality (the BI resulting state is split in state and quality on UCA2)

• the time stamping (in GMT time) and time quality

• the reason for change, which could be one of the below values :

− change of data (set if the state has changed, before persistence or motion filtering)

− change of quality (set if the quality has changed, before persistence or motion
filtering)

− change due to control (set if the state or quality change is due to a control)
From one server, all BI reports are not transmitted in a chronological order (it is a UCA2
client feature to put, if needed, all information in a chronological order).
During a loss of communication, the events detected on the MiCOM C264 Computer are not
buffered.
Application C264/EN AP/B30

MiCOM C264/C264C Page 33/396

GOOSE based mode

A BI (only SPS and DPS) can be configured to be transmitted in GOOSE mode. In this
mode, the change of status is transmitted in multicast to the configured receivers. Only the
BI unfiltered states are transmitted, the time stamping and the reason for change are not.
Due to GOOSE format, all BI resulting states given below cannot be transmitted. So, the
following mapping is applied :

BI Resulting State GOOSE value

RESET, FORCED RESET, SUBSTITUTED RESET, 01
CLOSE, FORCED CLOSE, SUBSTITUTED CLOSE
SET, FORCED SET, SUBSTITUTED SET, 10
OPEN, FORCED OPEN, SUBSTITUTED OPEN
MOTION00 00
MOTION11, TOGGLING, SELFCHECK FAULTY, JAMMED, 11
SUPPRESSED, UNKNOWN

Be careful
If an UCA2 client needs to use a measurement or counter, a non-goosed status or a control
managed by a server, setting the attribute (1) to ‘Data model only’ or ‘Data model and goose’
is required.
MPS, measurement and counters are only transmitted by reports.
For details about goose configuration see chapter 4.5.2.3 Configuring goose manually.

computer A has for

UCA 2 server
computer B

computer B has for

UCA 2 client
computer A

(1)

C0170ENa

FIGURE 33: MiCOM C264 COMPUTER (A) AS UCA2 CLIENT OF MICOM C264 COMPUTER (B)
C264/EN AP/B30 Application

Page 34/396 MiCOM C264/C264C

4.5.2 Defining addressing mapping of station-bus network

An UCA2 mapping is an aggregation of logical devices, composed of bricks. Generally, a
brick corresponds to an electrical device or function. It provides its real-time data (status,
measurements, and controls …) and some configuration aspects. To do that, a brick groups
data by categories (Status, measurements, Control, Configuration), called functional
components.
A functional component groups data objects. A data object must be seen as a real-time
equivalent of a PACiS datapoint. So, when a PACiS sub-system (UCA2 client) needs the
real-time value of a datapoint manages by an other sub-system (UCA2 server), this last one
transmits the information via a data object of its own UCA2 mapping. At SCE data modelling
level, UCA2 clients must precise which UCA2 servers it retrieves information from (see
chapter 4.5.1 Connecting MiCOM C264 Computer to others station-bus sub-systems).
Generally, an UCA2 data object has a stereotype, called common class. The structures of
these ones are known by all PACiS UCA2 communicant sub-systems. For PACiS sub-
systems, the number and structure of common classes are fixed. They are the terminal
description of UCA PACiS data modelling.
In UCA2 Mapping of PACiS sub-system, there is a native logical device LD0 with fixed and
hard-coded bricks (DBID, DI, GLOBE, and DIAG). When creating a PACiS MiCOM C264
Computer at SCE level, an UCA2 mapping with LD0 and its default bricks is also created.
LD0 is a system logical device that groups all system diagnostics and controls relevant to the
MiCOM C264 Computer. Datapoints addressed in the brick of LD0 are only relevant to
system topology.
Extra logical devices can be created in the UCA2 mapping of a MiCOM C264 Computer.
Generally, there is one logical device for each bay managed by the MiCOM C264 Computer,
and, in each logical device, there is one brick for each module or built-in function.
4.5.2.1 Updating LD0 of MiCOM C264 Computer UCA2 mapping
In LD0 of PACiS MiCOM C264 Computer, the fixed part is composed of the following bricks:

• DBID (DataBase IDentity) used for MiCOM C264 Computer databases identification
and management,

• DI (Device IDentity) used for MiCOM C264 Computer identification,

• GLOBE used for MiCOM C264 Computer mode management,

• C26xDIAG brick.

standard LD0
for computer

C0171ENa

FIGURE 34 : STANDARD LD0 EXTENSION FOR C26X MiCOM C264 COMPUTER (SCE)
Application C264/EN AP/B30

MiCOM C264/C264C Page 35/396

The LD0 can be completed with extra DIAG bricks, relative to some optional components of
the MiCOM C264 Computer. For ease of use, such extra DIAG bricks are seen as elements
of an “extended UCA2 mapping” object generally added automatically under the system
component associated to the extra DIAG.
Hereafter, are listed these extra DIAG bricks:

• For each IED connected to a PACiS MiCOM C264 Computer via an IED legacy
network, an implicit IEDDIAG (diagnostic for the IED) brick exists, and an extra brick
RDRE (for disturbance information) can be added.
Be careful, when creating an IED on a MiCOM C264 Computer legacy network, its
IEDDIAG brick name must be updated to avoid double values of bricks in the MiCOM
C264 Computer LD0.

LD0 extension optional RDRE

for IED brick for IED

C0172ENa

FIGURE 35 : LD0 EXTENSION FOR IED

• For each SCADA network connected to a PACiS MiCOM C264 Computer, an implicit
TCIDIAG (diagnostic for the SCADA network) brick exists.
Be careful, when creating a SCADA network on a MiCOM C264 Computer, its
TCIDIAG brick name must be updated to avoid double values of bricks in the MiCOM
C264 Computer LD0.

LD0 extension for

SCADA network

C0173ENa

FIGURE 36 : LD0 EXTENSION FOR SCADA NETWORK

C264/EN AP/B30 Application

Page 36/396 MiCOM C264/C264C

• An extra brick RDRE (for disturbance information) can be added in LD0 of the MiCOM
C264 Computer if it manages its own disturbance file.

optional
standard LD0 RDRE brick
for computer for computer
C0174ENa

FIGURE 37 : LD0 EXTENSION FOR C26X MiCOM C264 COMPUTER (SCE)

4.5.2.2 Creating application Logical device manually
Real-time data exchange between PACiS sub-systems is required for many purposes:

• At OI level:

− System and electrical process supervision and control (mimic animation,

controlpopup)

− Alarm management (generation, viewing, acknowledgement, clearing …)

− Logging (Sequence of event, log book)

− Event and value archiving (curve viewing, event analysis)

• At SMT level:

− System management (database loading and switching, device mode supervision

and control)

− Disturbance file storing

• At PACiS MiCOM C264 Computer level:

− Sharing datapoint for automation and built-in function,

− Feeding OI acquisition to insure its system functionality

− Feeding PACiS Gateway acquisition to transmit data between PACiS system and
SCADA

− Responding to system specific needs (command uniqueness)

• At PACiS gateway level:

− Transmit data between PACiS system and SCADA

To insure real-time data exchange on station-bus, specific logical devices (called here
application logical devices) must be created in the UCA2 mapping of the PACiS sub-system
that is server of the exchanged data (for definition of client/server, see chapter 4.5.1
Connecting MiCOM C264 Computer to others station-bus sub-systems). PACiS MiCOM
C264 Computer is the only PACiS sub-system that allows user-defined application logical
devices.
Application C264/EN AP/B30

MiCOM C264/C264C Page 37/396

The general philosophy to create manually application logical devices is:

• one application logical device per bay managed by MiCOM C264 Computer,

• in each application logical device, one brick per module or function contained in the
bay,

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

Type of datapoint Type of UCA2 data object

Relation: has for UCA2 address (->)
SPS SI
DPS SIT
MPS SIG
MV AI, WYE phase or DELTA phase, ISI
Counter ACCI
SPC BO
DPC DCO
SetPoint AO
C264/EN AP/B30 Application

Page 38/396 MiCOM C264/C264C

Manual creation of an application logical device

To create manually an application logical device:

• add ‘LD’ from object entry available at UCA2 mapping level,

• update its UCA2 name attribute (1), that must be unique for a given UCA2 mapping.

FIGURE 38: ADDING AN APPLICATION LOGICAL DEVICE

(1)

FIGURE 39 : UPDATING THE UCA2 NAME OF AN APPLICATION LOGICAL DEVICE

Naming rule
‘UCA2 name’ is a free name up to 32 characters, made with the following characters: 0-9, a-
z, A-Z. It can not begin with a digit.
Configuration rules and checks

• For each Logical Device defined under the UCA2/IEC Mapping, its name must be
unique in the mapping

• if the Logical Device is a generic one, its name must not contain the sub-string "LD0"
(reserved for system Logical Devices)
Application C264/EN AP/B30

MiCOM C264/C264C Page 39/396

Manual creation of an UCA2 brick

To create manually an UCA2 brick:

• add ‘GenBRIC’ from object entry available at UCA2 logical device level; do not use
RDRE brick reserved for non-PACiS UCA2 IED.

• update its UCA2 name attribute (1), that must be unique for a given UCA2 logical
device.

FIGURE 40: ADDING AN UCA2 BRICK

(1)

FIGURE 41 : UPDATING THE UCA2 NAME OF A BRICK

Naming rule
‘UCA2 name’ is a name made with 3 parts:

• optional wrapper (up to 6 characters), that can not begin with a digit

• standard brick name (4 uppercase characters)

• optional index (1 character)

Each part is made with the following characters: 0-9, a-z, A-Z
Configuration rules and checks

• For each Brick defined under a Logical Device, its name must be unique in the Logical
Device
Manual creation of an UCA2 functional component
To create manually an UCA2 functional component, add specific functional component from
object entry available at MiCOM C264 Computer UCA2 brick level. For MiCOM C264
Computers, useful functional components are:
C264/EN AP/B30 Application

Page 40/396 MiCOM C264/C264C

• ST to group statuses,

• CO to group controls,

• MX to group measurements,

• SP to group setpoints,

• CF to group configuration information relevant to CO or SP data objects.

FIGURE 42: ADDING AN UCA2 FUNCTIONAL COMPONENT

Manual creation of an UCA2 data object
To create manually an UCA2 data object:

• add specific data object from object entry available at UCA2 functional component
level. Each kind of functional components owns its own available list of data objects.
The following table shows the different lists useful for MiCOM C264 Computer UCA2
mapping:

Functional component Available data object

ST GenSI
GenSIT
GenSIG
MX GenAI
GenWYE
GenDELTA
GenACCl
CO GenBO
GenDCO
SP GenAO
CF GenSBOCF

• update its UCA2 name attribute (1), that must be unique for a given UCA2 functional
component.
Application C264/EN AP/B30

MiCOM C264/C264C Page 41/396

FIGURE 43: ADDING AN UCA2 DATA OBJECT

(1)

FIGURE 44 : UPDATING THE UCA2 NAME OF A DATA OBJECT

Naming rule
‘UCA2 name’ is a free name up to 9 characters, made with the following characters: 0-9, a-z,
A-Z. It can not begin with a digit.
Configuration rules and checks

• For each Data Object defined under a Functional Component (CO), its name must be
unique in the Functional Component

• For the following Functional Component types of a MiCOM C264 Computer: CO, MX
and ST, the maximum count of Data Objects is 50
Managing SBO mode during manual creation of UCA2 data object
When creating a GenBO, GenDCO or GenAO data object (A) , relevant to a datapoint with
SBO mode set to once or many:
C264/EN AP/B30 Application

Page 42/396 MiCOM C264/C264C

• a GenSBOCF (B) data object must be created in the CF functional component of the
brick

• extra relation ‘has for UCA2 deselect address’ must be added at (A) level and linked to
(B), in order to insure SBO un-selection functionality at UCA2 protocol level.

mandatory link to GenSBOCF

data object, if GenDCO is
relevant to a datapoint with
SBO mode facility

C0175ENa

FIGURE 45: MANAGING SBO MODE FOR UCA2 DATA OBJECT

Configuration rules and checks

• For each SPC, DPC or Setpoint datapoint having a profile with "SBO mode" attribute
set to "SBO Operate Once" or "SBO Operate Many" value :

− if the datapoint is linked to an UCA2 address through the relation "has for UCA2
address", then this address must be linked to a deselection UCA2 address through
the relation "has for UCA2 deselect address".

− Furthermore, for an SPC or DPC datapoint, the UCA2 name of the deselection
address must be made of the UCA2 name of the address followed by the "SBO"
string.
Application C264/EN AP/B30

MiCOM C264/C264C Page 43/396

4.5.2.3 Configuring goose manually

Goose is a mean given by UCA2 protocol to send and take into account faster the binary
status changes of state. That is very useful for time-critical fast automation or interlocking. In
a given UCA2 mapping, only its SI and SIT data objects are goose-able. Goose is attached
to and managed by the UCA2 server of the goosed data objects.
Two kinds of goose exists and one instance of each kind is managed by MiCOM C264
Computer:

• DNA vector, where up to 23 bit-pairs can be configured, i.e. 23 SI/SIT

• User status vector, where up to 64 bit-pairs can be configured, i.e. 64 SI/SIT.

To obtain the best performance in goose management, begin to affect DNA vector
increasingly and continuously, then if necessary affect User status vector increasingly and
continuously.
Up to 87 SI/SIT can be set as goose-able per MiCOM C264 Computer basis.
An UCA2 goose can be seen as a bit-string, where elementary information is grouped on a
bit-pair basis. Each bit-pair corresponds to a specific SI or SIT. In DNA vector, bit-pair rank is
in the range [10..32] (ones under 10 are reserved); In User status vector, the range is [0..63].
Goose configuration is done at SI/SIT data object level via specific attributes:
Goose transmission:
0. Specifies if the data-object is goose-able,
and if yes in which goose (DNA or User status) and the way its bit-pair rank is affected
(Manual or Automatic).
In case of automatic affectation, the rank of bit-pair is fixed at MiCOM C264 Computer
databag generation.
In case of manual affectation, the rank of bit-pair must be filled by user in the following
attribute:
1. Rank in goose: appears and must be filled for manual goose affectation

(1)

(2)

FIGURE 46: CONFIGURING GOOSE MANUALLY

C264/EN AP/B30 Application

Page 44/396 MiCOM C264/C264C

Configuration rules and checks

• Among all the SI and SIT Data Objects having their attribute "goose transmission" set
to the "Manual DNA vector" value, the value of the attribute "rank in goose" must be
unique.

• Among all the SI and SIT Data Objects having their attribute "goose transmission" set
to the "Manual user status vector" value, the value of the attribute "rank in goose"
must be unique.
4.5.2.4 Creating application Logical device automatically by using UCA automatic addressing
UCA2 automatic addressing function is based on the substation electrical topology and
especially on bays. For details about the way to configure this topology see chapter
DEFINING MICOM C264 COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE)
The easiest way to create application logical devices relevant to electrical bays managed by
a MiCOM C264 Computer, is to run UCA2 automatic addressing function for the MiCOM
C264 Computer. The contextual menu (mouse right click) of the MiCOM C264 Computer
UCA2 mapping (1) can launch this function.
UCA2 automatic addressing for a given MiCOM C264 Computer concerns only the bays and
ATCC function it manages, i.e. whose relation ‘is managed by’ has been filled to the MiCOM
C264 Computer. So, for extra UCA2 addressing concerning non-ATCC datapoints whose
level is higher than bay (substation, site or voltage level), manual creation of application
logical device must be done (see chapter 4.5.2.2 Creating application Logical device
manually).
UCA2 automatic addressing procedure includes GOOSE addressing: GOOSE bit-pair
buffers DNA and User status are sequentially filled with automatism datapoints exchanged
between servers. As for GOOSE manual addressing, result of GOOSE automatic addressing
is set for a datapoint as a “Manual attachment” to the selected DNA or User status bit-pair,
thus preserving this association over any new automatic-addressing session. Size limit of
DNA and User status buffers result in considering priority levels for GOOSE addressing:
existing “Manual attachments” (operator’s manual selections and previous GOOSE
addressing results) are considered first and left unchanged, than fast automation datapoints
are processed and finally slow automation datapoints. Case of GOOSE buffer overflow is
signalled and stop the process of GOOSE addressing.
For details about Goose modelling and configuration see chapter 4.5.2.3 Configuring goose
manually)
Application C264/EN AP/B30

MiCOM C264/C264C Page 45/396

(1)

FIGURE 47: UCA2 AUTOMATIC ADDRESSING

C264/EN AP/B30 Application

Page 46/396 MiCOM C264/C264C

4.5.3 Addressing datapoint on station-bus network

For details about datapoint, refer to chapter 5 DEFINING DATAPOINT.
To exchange datapoint values between station-bus sub-systems, datapoints should be
linked to specific UCA2 data objects. There are 2 ways to resolve this link:

• Doing a manual addressing, by adding at datapoint level the relation ‘has for UCA2
address’ (1) and filling it with the corresponding UCA2 data object in a pre-configured
UCA2 addressing mapping (refer to chapter 4.5.2.2 Creating application Logical
device manually for manual definition of an UCA2 addressing mapping).

(1)

FIGURE 48: REALISING UCA2 MANUAL ADDRESSING OF DATAPOINT

(E.G. FOR BAY SPS DATAPOINT)

• Using automatic UCA2 addressing, function available at SCE level (refer to chapter
4.5.2.4 Creating application Logical device automatically by using UCA automatic
addressing), whose objectives are:

− automatic UCA2 mapping creation at MiCOM C264 Computer level,

− automatic linking between data objects in this UCA2 mapping and datapoints
managed by the MiCOM C264 Computer.
4.6 Networking IED on MiCOM C264 Computer legacy network
4.6.1 Creating a legacy network of IED
Generally, specific devices called relays or IEDs insure protection of electrical modules and
bays.
IED connection to PACiS system is commonly done via IED legacy networks managed by
PACiS MiCOM C264 Computer as master.
At SCE data modelling level, up to 4 IED legacy network (relevant to a specific protocol) can
be located under a PACiS MiCOM C264 Computer C264 or C264C. Each IED legacy
network has to be linked to communication port embedded in MiCOM C264 Computer
boards. Up to 16 IED can be added under a legacy network.
Application C264/EN AP/B30

MiCOM C264/C264C Page 47/396

4.6.1.1 Adding a legacy network

To create a legacy network on a MiCOM C264 Computer:

• Add a legacy network relevant to a specific protocol from object entry available at
MiCOM C264 Computer level (1),

• Update the legacy network attributes relevant to its protocol characteristics (see
chapters 4.6.1.2 to 4.6.1.6),

• Update its ‘has for main communication port’ relation and the communication port
characteristics (see chapter 4.4.4 Configuring a communication channel),

(1)

FIGURE 49: ADDING A LEGACY NETWORK

4.6.1.2 Setting common attributes to legacy network
Whatever the kind of legacy network, its short and long name attributes (1) must be updated
for correct logging and alarm discrimination concerning IED status datapoint connected to
the legacy network.

(1)

FIGURE 50 : SETTING COMMON ATTRIBUTES TO LEGACY NETWORK

4.6.1.3 Setting specific attributes of T103 legacy network
When adding a T103 legacy network, some specific attributes available for all its IEDs must
be updated:
C264/EN AP/B30 Application

Page 48/396 MiCOM C264/C264C

1. Number of retries:
- number of tries of the same frame without IED response, the MiCOM C264
Computer will send it before setting it disconnected
2. Acknowledgement time-out:
- maximum delay a IED answer is awaited when the MiCOM C264 Computer asks it a
information
3. Synchronisation cycle:
- time synchronisation period of the IED by the MiCOM C264 Computer
4. Downgraded cycle:
- If a IED is set disconnected by the MiCOM C264 Computer, it tries to re-connect it
regularly at this cycle.

(1)
(2)

(3)
(4)

FIGURE 51 : SETTING SPECIFIC ATTRIBUTES TO T103 LEGACY NETWORK

Application C264/EN AP/B30

MiCOM C264/C264C Page 49/396

4.6.1.4 Setting specific attributes of T101 legacy network

When adding a T101 legacy network, some specific attributes available for all its IEDs must
be updated:
1. Number of retries:
corresponds to number of tries of the same frame without IED response, the MiCOM
C264 Computer will send it before setting it disconnected
2. Station address size:
size (in byte) of the IED addresses (1 or 2 bytes)
3. ASDU address size:
size (in byte) of the ASDU addresses (1 or 2 bytes)
4. Information address size:
size (in byte) of the information addresses (1 to 3 bytes)
5. Transmission cause size:
size (in byte) of the transmission cause (1 or 2 bytes)
6. Frame length:
If a IED can not managed frame whose length is superior to 255, frame length
attribute must be set to the available length for the IED (from 64 to 255)
7. Acknowledgement time-out:
maximum delay a IED answer is awaited when the MiCOM C264 Computer asks it a
information
8. Synchronisation cycle:
time synchronisation period of the IED by the MiCOM C264 Computer
9. Downgraded cycle:
If a IED is set disconnected by the MiCOM C264 Computer, it tries to re-connect it
regularly at this cycle.
10. Type of link (balanced or unbalanced):
If unbalanced link, only master (here MiCOM C264 Computer) asks IED.
If balanced link, IED can also asks the master (here MiCOM C264 Computer) without
solicitation
11. Test frame time-out:
In case of ‘balanced link’ (cf. attribute (10)), a life message (test frame) is sent
periodically between MiCOM C264 Computer and IED. This attribute corresponds to
maximum delay to receive this life message, to MiCOM C264 Computer’s point of
view. If no reception within this delay, IED is set disconnected.

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)

FIGURE 52 : SETTING SPECIFIC ATTRIBUTES TO T101 LEGACY NETWORK

C264/EN AP/B30 Application

Page 50/396 MiCOM C264/C264C

4.6.1.5 Setting specific attributes of Modbus legacy network

When adding a Modbus legacy network, some specific attributes available for all its IEDs
must be updated:
1. Number of retries:
corresponds to number of tries of the same frame without IED response, the MiCOM
C264 Computer will send it before setting it disconnected
2. Acknowledgement time-out:
maximum delay a IED answer is awaited when the MiCOM C264 Computer asks it a
information
3. Synchronisation existence:
If the MiCOM C264 Computer must synchronise the time of the IED, set this flag to
‘Yes’, otherwise to ‘No’
4. Synchronisation cycle:
time synchronisation period of the IED by the MiCOM C264 Computer.
Significant if (3) is set to ‘Yes’
5. Downgraded cycle:
If a IED is set disconnected by the MiCOM C264 Computer, it tries to re-connect it
regularly at this cycle.

(1)
(2)

(3)
(4)
(5)

FIGURE 53 : SETTING SPECIFIC ATTRIBUTES TO MODBUS LEGACY NETWORK

Application C264/EN AP/B30

MiCOM C264/C264C Page 51/396

4.6.1.6 Setting specific attributes of DNP3 legacy network

When adding a DNP3 legacy network, some specific attributes available for all its IEDs must
be updated:
1. Master address:
MiCOM C264 Computer address on the DNP3 legacy network
2. Acknowledgement time-out:
maximum delay a IED answer is awaited when the MiCOM C264 Computer asks it a
information
3. Number of retries
corresponds to number of tries of the same frame without IED response, the MiCOM
C264 Computer will send it before setting it disconnected
4. Application time-out:
Time-out used by MiCOM C264 Computer, at application layer of DNP3 protocol
5. Synchronisation cycle:
time synchronisation period of the IED by the MiCOM C264 Computer
6. Downgraded cycle:
If a IED is set disconnected by the MiCOM C264 Computer, it tries to re-connect it
regularly at this cycle.

(1)
(2)

(3)
(4)
(5)
(6)

FIGURE 54 : SETTING SPECIFIC ATTRIBUTES TO DNP3 LEGACY NETWORK

C264/EN AP/B30 Application

Page 52/396 MiCOM C264/C264C

4.6.1.7 Adding an IED to a legacy network

To create an IED on a legacy network:

• Add an IED from object entry available at legacy network level (1),

• Update the IED attributes relevant to its protocol characteristics (see chapter 4.6.1.8
Setting attributes of legacy IED)

• For DNP3, T103, or Mobdus IED, update the ‘has for acquisition profile’ relation with a
previously created IED acquisition type (for creation of IED acquisition type see
chapters 4.6.1.9 to 4.6.1.12)

(1)

FIGURE 55: ADDING AN IED TO A LEGACY NETWORK

updated relation
between IED and IED
acquisition type

C0176ENa

FIGURE 56: LINKING IED ACQUISITION PROFILE TO AN IED

Application C264/EN AP/B30

MiCOM C264/C264C Page 53/396

4.6.1.8 Setting attributes of legacy IED

Whatever the kind of IED, the following attributes must be updated:
1. Short and long name attributes for correct logging and alarm discrimination concerning
IED status datapoint
2. Network address of the IED on the legacy network
3. Automatic disturbance availability, unavailable for DNP3 IED
4. Localisation for disturbance file non-significant for DNP3 IED, used for basic file
name upload by SMT on OWS hard disk: <localisation>_N#

(1)

(2)

(3)

(4)

FIGURE 57 : SETTING ATTRIBUTES OF LEGACY IED

Configuration rules and checks

• For each IED, its "network address" and its "short name" attributes value must be
unique, per Legacy Network.
4.6.1.9 Adding an IED acquisition type to a legacy network
Common acquisition and communication characteristics are shared by IEDs. These ones are
grouped in an object called ‘IED acquisition type’, similar to acquisition profile. It is available
for DNP3, T103 and Modbus protocols.
To create an IED acquisition type on a legacy network:

• Add an IED acquisition from object entry available at legacy network level (1),

• Update the IED acquisition type attributes relevant to its protocol characteristics (see
chapter 4.6.1.8 Setting attributes of legacy IED)

(1)

FIGURE 58 : ADDING AN IED ACQUISITION TYPE TO A LEGACY NETWORK

(E.G. FOR DNP3)
Configuration rules and checks

• For each MiCOM C264 Computer and all its Legacy Networks, the maximum count of
"xxx acq type" components is 10.
C264/EN AP/B30 Application

Page 54/396 MiCOM C264/C264C

4.6.1.10 Setting attributes of T103 acquisition type

When adding a T103 acquisition type, some attributes available for all its linked IEDs must
be updated:
1. IED type, whose list depends on kinds of T103 IED integrated in PACiS system:
By default use ‘T103 standard IED’
2. T103 function type used for acquisition:
see IED documentation to set correctly this attribute
3. General interrogation period:
cycle used to fetch regularly statuses and measurements from IED and to avoid loss
of event information
4. Measurement reduction coefficient used for scaling (ASDU 3 usage):
refer to T103 documentation for details about this scaling
5. 4 sets of nominal values (voltage, current an frequency) used for scaling:
refer to T103 documentation for details about this scaling

(1)

(2)

(3)

(4)

(5)

FIGURE 59 : SETTING ATTRIBUTES OF T103 ACQUISITION TYPE

Application C264/EN AP/B30

MiCOM C264/C264C Page 55/396

4.6.1.11 Setting attributes of Modbus acquisition type

When adding a Modbus acquisition type, some attributes available for all its linked IEDs
must be updated:
1. IED type, whose list depends on kinds of Modbus IED integrated in PACiS system:
By default use ‘Modicon’
2. Modbus function type used for polling frame:
To test the IED connection, this attribute gives which Modbus function is used. For
AREVA IED product, the function 7 is generally used.
3. Mapping address:
- bit address (in case of function 1 and 2),
- word address (in case of function 3 and 4),
- sub code (in case of function 8)
Non significant if attribute (2) equal to 7.
Associated to attribute (2), it gives which start address is used to test the IED
connection
4. Size to read:
- number of bits (in case of function 1 and 2) between 0 and 2048,
- number of words (in case of function 3 and 4) between 0 and 128
Non significant if attribute (2) equal to 7 or 8.
Associated to attribute (3), it gives which length is used to test the IED connection
5. Data frame length in number of bytes:
If a IED can not managed frame whose length is superior to 255, frame length
attribute must be set to the available length for the IED (from 64 to 255)

(1)

(2)
(3)
(4)

(5)

FIGURE 60 : SETTING ATTRIBUTES OF MODBUS ACQUISITION TYPE

C264/EN AP/B30 Application

Page 56/396 MiCOM C264/C264C

4.6.1.12 Setting attributes of DNP3 acquisition type

When adding a DNP3 acquisition type, some attributes available for all its linked IEDs must
be updated:
1. DNP3 class usage for addressing:
Not yet implemented
Always considered as ‘True’ at MiCOM C264 Computer level
2. Synchronisation type (network or external):
In case of ‘network’ synchronisation, MiCOM C264 Computer synchronises the time of
the IED, otherwise the synchronisation is assumed independently by an external
equipment directly connected to the IED.
Not yet implemented
Always considered as ‘Network’ at MiCOM C264 Computer level

(1)

(2)

FIGURE 61 : SETTING ATTRIBUTES OF DNP3 ACQUISITION TYPE

4.6.2 Defining addressing mapping of legacy IED
To transmit information between IED and PACiS system, an IED legacy network connected
to a PACiS MiCOM C264 Computer is used.
To receive or send information between legacy IED and PACiS system, each concerned
data must have a specific address on the legacy network relatively to its protocol. General
modelling of legacy network address mapping can be done. At SCE level, an IED of a legacy
network owns an “IED mapping” object, that is split in categories of mapping on a per
datapoint kind basis. In each category of mapping, elementary IED addresses can be
created. For details about datapoint, refer to chapter 5 DEFINING DATAPOINT. This
mapping is implicitly created during IED adding at legacy network level.Addressing MPS
datapoint on legacy IED is not available.
Application C264/EN AP/B30

MiCOM C264/C264C Page 57/396

Entry point of IED

mapping

Categories per
datapoint kind basis

C0177ENa

FIGURE 62 : STRUCTURE OF THE ADDRESSING MAPPING OF LEGACY IED

(E.G. FOR T101 IED)
For details about addressing mapping of a given IED on a specific protocol, refer to relay
documentation.
Configuration rules and checks
In the IED Mapping, the address identification of each "xxx addr. on IED" must be unique.

• DNP3:
address identification is given by the attribute "address" of the "xxx addr. on IED".

• MODBUS:
address identification is made of the following combinations of its attribute values:
- { "mapping address" , "function" , "bit number" }
- { "mapping address" , "function" }

• T103:
address identification is made of the following combinations of its attribute values:
- { "ASDU number" , "function type" , "information number" , "common address of
ASDU" , "index in the ASDU" }
- { "ASDU number" , "function type" , "information number" , "common address of
ASDU" }
- { "ASDU number" , "function type" , "information number" }

• T101:
address identification is made of the following combinations of its attribute values:
- { "information object address" , "common address of ASDU" }
- { "information object address" }
C264/EN AP/B30 Application

Page 58/396 MiCOM C264/C264C

4.6.2.1 Defining an IED address for SPS datapoint

An addition of an IED address for SPS datapoint is done under SCE via the “Object entry”
area at IED SPS mapping level by clicking on mouse’s right button.

FIGURE 63: ADDING AN IED SPS ADDRESS

(E.G. FOR T101 IED)
Once added, IED SPS address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Mapping address:
Word address or Bit address depending on bit number attribute
3. Bit number:
Used only if Word read or status read is used (see function attribute)
4. Function:
Modbus function to use to read the SPS:
- 1, 2 : read bit,
- 3, 4 : read word,
- 7 : read status
For T101 protocol:
5. Information object address:
6. Common address of ASDU:
by default (–1) is equal to IED address (see chapter 4.6.1.8 Setting attributes of legacy
IED)
For T103 protocol:
7. ASDU number (by default 1):
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
8. Function type:
9. Information number
10. Common address of ASDU:
by default (–1) is equal to IED address (see chapter 4.6.1.8 Setting attributes of legacy
IED)
Application C264/EN AP/B30

MiCOM C264/C264C Page 59/396

For DNP3 protocol:

11. Address

(1)

(2)
(3)
(4)

(5)
(6)

(7)
(8)
(9)
(10)

(11)

FIGURE 64: DEFINING AN IED ADDRESS FOR SPS DATAPOINT

C264/EN AP/B30 Application

Page 60/396 MiCOM C264/C264C

4.6.2.2 Defining an IED address for DPS datapoint

An addition of an IED address for DPS datapoint is done under SCE via the “Object entry”
area at IED DPS mapping level by clicking on mouse’s right button.

FIGURE 65: ADDING AN IED DPS ADDRESS

(E.G. FOR T101 IED)
Once added, IED DPS address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Mapping address:
Word address or Bit address depending on bit number attribute
3. Bit number:
Used only if Word read or status read is used (see function attribute)
4. Function:
Modbus function to use to read the DPS:
- 1, 2 : read bit,
- 3, 4 : read word,
- 7 : read status
For T101 protocol:
5. Information object address
6. Common address of ASDU:
by default (–1) is equal to IED address (see chapter 4.6.1.8 Setting attributes of legacy
IED)
For T103 protocol:
7. ASDU number (by default 1):
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
8. Function type: refer to relay documentation
9. Information number: refer to relay documentation
10. Common address of ASDU:
by default (–1) is equal to IED address (see chapter 4.6.1.8 Setting attributes of legacy
IED)
For DNP3 protocol:
11. Address
For all protocol type, DPS acquisition on IED can also be done via 2 different addresses. In
that case, 2 ‘DPS address on IED’ must be created for this DPS. For each of them, the
Application C264/EN AP/B30

MiCOM C264/C264C Page 61/396

attribute ‘contact identifier’ (12) must be set to ‘Open’ or ‘Closed’, to precise which state of
the DPS is concerned by the IED address. If DPS status is given by only one IED address,
let ‘contact identifier’ value to ‘unused’.

(1)

(2)
(3)
(4)

(12)

(5)
(6)

(12)

(7)
(8)
(9)
(10)

(12)

(11)

(12)

FIGURE 66: DEFINING AN IED ADDRESS FOR DPS DATAPOINT

4.6.2.3 Defining an IED address for MV datapoint
An addition of an IED address for MV datapoint is done under SCE via the “Object entry”
area at IED MV mapping level by clicking on mouse’s right button.
C264/EN AP/B30 Application

Page 62/396 MiCOM C264/C264C

FIGURE 67: ADDING AN IED MV ADDRESS

(E.G. FOR T101 IED)
Once added, IED MV address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Mapping address:
Word address
3. Function:
Modbus function to use to read the MV:
- 3, 4 : read word,
- 7 : read status
4. Data format:
see following paragraph
For T101 protocol:
5. Information object address
6. Common address of ASDU:
by default (–1) is equal to IED address (see chapter 4.6.1.8 Setting attributes of legacy
IED)
For T103 protocol:
7. ASDU number (by default 1):
- 3, 4, 9 (for all IED)
- 77 (Only for Px2x)
- 73 (Only for Px3x)
8. Function type
9. Information number
10. Index of the MV in the ASDU
11. Common address of ASDU:
by default (–1) is equal to IED address (see chapter 4.6.1.8 Setting attributes of legacy
IED)
12. Unit:
Voltage, Current, Power, Frequency or ‘No Unit’
Application C264/EN AP/B30

MiCOM C264/C264C Page 63/396

For DNP3 protocol:

13. Address

(1)

(2)
(3)
(4)

(5)
(6)

(7)
(8)
(9)

(10)
(11)
(12)

(13)

FIGURE 68: DEFINING AN IED ADDRESS FOR MV DATAPOINT

C264/EN AP/B30 Application

Page 64/396 MiCOM C264/C264C

Measurement formats that can be used with the MODBUS protocol

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

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

MiCOM C264/C264C Page 65/396

Transmission
Format Description
order
REAL32_LW_HB Transmission of a 32 bit real value. The low word is 2-1-4-3
transmitted first. The high byte of each word is transmitted
first.
REAL32_HW_LB Transmission of a 32 bit real value. The high word is 3-4-1-2
transmitted first. The low byte of each word is transmitted
first.
REAL32_HW_HB Transmission of a 32 bit real value. The high word is 4-3-2-1
transmitted first. The high byte of each word is transmitted
first.
M230_T5_TYPE Transmission of a 32 bit : Unsigned Measure 4-3-2-1
Bit 31to 24 decimal exposant ( signed 8 bytes)
Bit 23…00 binary unsigned value 24 bytes
M230_T6_TYPE Transmission of a 32 bit : Signed Measure 4-3-2-1
Bit 31to 24 decimal exposant ( signed 8 bytes)
Bit 23…00 binary signed value 24 bytes
M230_T7_TYPE Transmission of a 32 bit: power factor 4-3-2-1
Bit 31to 24 Signed :Import / Export ( 00/FF)
Bit 23…16 Signed :Inductive / capacitive ( 00/FF)
Bit 15…00 Unsigned value ( 16 bytes)
ION_MODULUS_100 Transmission of a 32 bit: ION Energy values 4-3-2-1
00_unsigned
Bit 31to 16 reg Hight: RH= unsigned value/10000
Bit 15…00 reg Low : RL = unsigned value modulus 10000
Value = RH*10000+RL
ION_MODULUS_100 Transmission of a 32 bit: ION Energy values 4-3-2-1
00_signed
Bit 31to 16 reg Hight: RH= signed value/10000
Bit 15…00 reg Low : RL = signed value modulus 10000
Value = RH*10000+RL
Both reg high and low are signed
C264/EN AP/B30 Application

Page 66/396 MiCOM C264/C264C

4.6.2.4 Defining an IED address for Counter datapoint

An addition of an IED address for Counter datapoint is done under SCE via the “Object
entry” area at IED Counter mapping level by clicking on mouse’s right button.

FIGURE 69: ADDING AN IED COUNTER ADDRESS

(E.G. FOR T101 IED)
Once added, IED Counter address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Mapping address:
Word address
3. Function:
Modbus function to use to read the MV:
- 3, 4 : read word
4. Data format:
similar to MV (cf. chapter 4.6.2.3 Defining an IED address for MV datapoint)
For T101 protocol:
5. Information object address
6. Common address of ASDU:
by default (–1) is equal to IED address (see chapter 4.6.1.8 Setting attributes of legacy
IED)
For T103 protocol:
Not significant: There is no Counter in T103
For DNP3 protocol:
7. Address
Application C264/EN AP/B30

MiCOM C264/C264C Page 67/396

(1)

(2)
(3)
(4)

(5)
(6)

(7)

FIGURE 70: DEFINING AN IED ADDRESS FOR COUNTER DATAPOINT

C264/EN AP/B30 Application

Page 68/396 MiCOM C264/C264C

4.6.2.5 Defining an IED address for SPC datapoint

An addition of an IED address for SPC datapoint is done under SCE via the “Object entry”
area at IED SPC mapping level by clicking on mouse’s right button.

FIGURE 71: ADDING AN IED SPC ADDRESS

(E.G. FOR T101 IED)
Once added, IED SPC address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Mapping address:
Bit address for function 5 or 15,
Word address for function 6
3. Bit number:
Used only if Function 6 is used (see function attribute)
The range value is [0 .. 15]
4. Function:
Modbus function to use to send the SPC:
- 5 : write 1 bit (Mapping address indicates the address of the bit),
- 6 : write 1 word (Mapping address indicates the address of the word, bit number
indicates the number of the bit in the word),
- 15 : write N bits (used to set only 1 bit at a time, Mapping address indicates the
address of the bit)
For T101 protocol:
5. Information object address
6. Common address of ASDU:
by default (–1) is equal to IED address (see chapter 4.6.1.8 Setting attributes of legacy
IED)
For T103 protocol:
7. ASDU number (by default 1):
- 20 (for all IED)
- 45,46 (Only for Px3x)
8. Function type: refer to relay documentation
9. Information number: refer to relay documentation
For DNP3 protocol:
10. Address
Application C264/EN AP/B30

MiCOM C264/C264C Page 69/396

(1)

(2)
(3)
(4)

unused

(5)
(6)

unused

(7)
(8)
(9)

unused

(10)

unused

C0178ENa

FIGURE 72: DEFINING AN IED ADDRESS FOR SPC DATAPOINT

C264/EN AP/B30 Application

Page 70/396 MiCOM C264/C264C

4.6.2.6 Defining an IED address for DPC datapoint

An addition of an IED address for DPC datapoint is done under SCE via the “Object entry”
area at IED DPC mapping level by clicking on mouse’s right button.

FIGURE 73: ADDING AN IED DPC ADDRESS

(E.G. FOR T101 IED)
Once added, IED DPC address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Mapping address:
Bit address for function 5 or 15,
Word address for function 6
3. Bit number:
Used only if Function 6 is used (see function attribute)
The range value is [0 .. 15]
4. Function:
Modbus function to use to send the DPC:
- 5 : write 1 bit (Mapping address indicates the address of the bit),
- 6 : write 1 word (Mapping address indicates the address of the word, bit number
indicates the number of the bit in the word),
- 15 : write N bits (used to set only 1 bit at a time, Mapping address indicates the
address of the bit)
For T101 protocol:
5. Information object address
6. Common address of ASDU:
by default (–1) is equal to IED address (see chapter 4.6.1.8 Setting attributes of legacy
IED)
For T103 protocol:
7. ASDU number (by default 1):
- 20 (for all IED)
- 45,46 (Only for Px3x)
8. Function type: refer to relay documentation
9. Information number: refer to relay documentation
For DNP3 protocol:
10. Address
For all protocol type, DPC control on IED can also be done via 2 different addresses. In that
case, 2 ‘DPC address on IED’ must be created for this DPC. For each of them, the attribute
‘contact identifier’ (12) must be set to ‘Open’ or ‘Close’, to precise which order of the DPC is
concerned by the IED address. If DPC control is given by only one IED address, set ‘contact
identifier’ value to ‘unused’.
Application C264/EN AP/B30

MiCOM C264/C264C Page 71/396

(1)
(2)
(3)
(4)

unused
(11)

(5)
(6)

unused

(11)

(7)
(8)
(9)

unused

(11)

(10)
unused

(11)

C0179ENa

FIGURE 74: DEFINING AN IED ADDRESS FOR DPC DATAPOINT

C264/EN AP/B30 Application

Page 72/396 MiCOM C264/C264C

4.6.2.7 Defining an IED address for SetPoint datapoint

An addition of an IED address for SetPoint datapoint is done under SCE via the “Object
entry” area at IED SetPoint mapping level by clicking on mouse’s right button.

FIGURE 75: ADDING AN IED SETPOINT ADDRESS

(E.G. FOR T101 IED)
Once added, IED SetPoint address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
SetPoint address on Modbus is only available for WAGO relay, where output format is fixed
to UINT16.
2. Mapping address:
Word address for function 6
3. Function:
Modbus function to use to send the SetPoint:
- 6 : write 1 word (Mapping address indicates the address of the word, bit number
indicates the number of the bit in the word),
For T101 protocol:
4. Information object address
5. Output format:
available values are: REAL32 (IEEE 754), Normalized, Scaled
For T103 protocol:
SetPoint address on T103 is only available for REGD relay, where output format is
configurable.
6. ASDU number (by default 1): : refer to relay documentation
7. Function type: refer to relay documentation
8. Information number: refer to relay documentation
9. Output format:
available values are: INT8, UINT8, INT16, UNIT16, REAL32 (IEEE 754)
For DNP3 protocol:
10. Address
For all protocol type, values of SetPoint control on IED must be verified and scaled
depending on output format, before transmission. This is done via 2 extra attributes ‘minimal
value’ (11) and ‘maximal value’ (12).
Application C264/EN AP/B30

MiCOM C264/C264C Page 73/396

(1)

(2)
(3)
unused
(11)
(12)

(4)
unused
(5)

(11)
(12)

(6)
(7)
(8)

unused
(9)
(11)
(12)

(10)

unused
(11)
(12)

C0180ENa

FIGURE 76: DEFINING AN IED ADDRESS FOR SETPOINT DATAPOINT

4.6.3 Addressing datapoint on IED legacy network
Refer to chapters:

• 5.6.2 Acquiring input datapoint via IED legacy network

• 5.7.2 Controlling output datapoint via IED legacy network

C264/EN AP/B30 Application

Page 74/396 MiCOM C264/C264C

4.7 Networking SCADA on MiCOM C264 Computer SCADA network

4.7.1 Creating a SCADA network
An electrical substation can be supervised and controlled from many points inside the
substation via PACiS operator interfaces (Substation Control Point or SCP) and/or PACiS
MiCOM C264 Computer bay panels (Bay Control Point or BCP), and outside the substation.
Generally, the distant control of the substation (Remote Control Point or RCP) is done via
specific networks called SCADA legacy network.
Several SCADA legacy networks can be connected to a PACiS system, via PACiS MiCOM
C264 Computer or PACiS telecontrol gateway sub-systems. SCADA legacy networks are
managed as master by distant SCADA and can be redundant for safety reason. A PACiS
MiCOM C264 Computer can manage up to 2 SCADA networks.
At SCE data modelling level, only SCADA legacy networks and their protocol are modelled
and connected to gateway sub-systems. Each SCADA network has to be linked to a main
communication port and eventually an auxiliary communication port in case of redundancy.
4.7.1.1 Adding a SCADA network
To create a SCADA network on a MiCOM C264 Computer:

• Add a SCADA network from object entry available at MiCOM C264 Computer level
(1),

• Update the SCADA network attributes relevant to its protocol characteristics (see
chapter 4.7.2 Defining addressing mapping of SCADA legacy network),

• If SCADA does not use the substation network to communicate with the MiCOM C264
Computer, update its ‘has for main communication port’ relation and the
communication port characteristics (see chapter 4.4.4 Configuring a communication
channel),

• For DNP3 and T101 protocol on serial line, SCADA link can be redundant. To create a
redundant SCADA link, jus add the relation ‘has for auxiliary communication port’
(2) extra relation on MiCOM C264 Computer SCADA network and fill it with the
relevant serial port.
Application C264/EN AP/B30

MiCOM C264/C264C Page 75/396

(1)

FIGURE 77: ADDING A SCADA NETWORK

(2)

FIGURE 78: CREATING A REDUNDANT SCADA LINK

C264/EN AP/B30 Application

Page 76/396 MiCOM C264/C264C

4.7.1.2 Setting common attributes to SCADA network

Whatever the kind of SCADA network, its short and long name attributes (1) must be
updated for correct logging and alarm discrimination concerning status datapoints managed
by the MiCOM C264 Computer for each connected SCADA network.

(1)

FIGURE 79 : SETTING COMMON ATTRIBUTES TO SCADA NETWORK

4.7.1.3 Setting specific attributes of T101 SCADA network
When adding a SCADA network, the supported protocol must be updated (1). Here, set it to
‘T101’. Then SCADA network tab-panes are refreshed relatively to the selected protocol.

(1)

FIGURE 80 : SETTING PROTOCOL TYPE OF SCADA NETWORK

When setting a T101 SCADA network, some specific attributes available for the protocol
must be updated (Protocol and SOE tab-panes):
1. Link address length (in byte)
2. Link address
3. ASDU common address length (in byte)
4. ASDU common address
5. Address structure (byte combination)
6. Frame maximum length
7. Cause of transmission length
8. MV periodic cycle
9. Time format
10. Background scan cycle
11. Type of link
12. T3: test frame time-out
13. SBO time-out
14. SOE file support
15. SOE file address, visible and significant if SOE file support set to Yes
Application C264/EN AP/B30

MiCOM C264/C264C Page 77/396

16. SOE file format (T101/S900 extension), visible and significant if SOE file support set to
Yes
17. Maximum number of events per SOE file, visible and significant if SOE file support set
to Yes
18. Number of events for full SOE file message sent to SCADA (<Maximum number of
events per SOE file) , visible and significant if SOE file support set to Yes

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)

(16)
(17)

(18)

FIGURE 81 : SETTING SPECIFIC ATTRIBUTES TO T101 SCADA NETWORK

Configuration rules and checks

• The following constraints between the attributes must be respected :

"SOE file nb of events" > "'full' SOE file nb of events"
C264/EN AP/B30 Application

Page 78/396 MiCOM C264/C264C

4.7.1.4 Setting specific attributes of DNP3 SCADA network

When adding a SCADA network, the supported protocol must be updated (1). Here, set it to
‘DNP3’. Then SCADA network tab-panes are refreshed relatively to the selected protocol.

(1)

FIGURE 82 : SETTING PROTOCOL TYPE OF SCADA NETWORK

When setting a DNP3 SCADA network, some specific attributes available for the protocol
must be updated (Protocol tab-pane):
1. TCP/IP usage (Yes/No):
set to ‘Yes’ if substation network is used by the DNP3 SCADA to communicate with
the MiCOM C264 Computer
2. Link address, not significant if TCP/IP usage is set to ‘Yes’.
3. DNP3 class used for SPS and DPS
4. DNP3 class used for MV
5. DNP3 class used for Counter
6. MV format
7. Counter format
8. SBO time-out
Setting SOE information SOE tab-panes, for DNP3 SCADA network is not significant (not
implemented).

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)

FIGURE 83 : SETTING SPECIFIC ATTRIBUTES TO DNP3 SCADA NETWORK

Application C264/EN AP/B30

MiCOM C264/C264C Page 79/396

4.7.1.5 Setting specific attributes of T104 SCADA network

When adding a SCADA network, the supported protocol must be updated (1). Here, set it to
‘T104’. Then SCADA network tab-panes are refreshed relatively to the selected protocol.

(1)

FIGURE 84 : SETTING PROTOCOL TYPE OF SCADA NETWORK

When setting a T104 SCADA network, some specific attributes available for the protocol
must be updated (Protocol and SOE tab-panes):
1. ASDU common address
2. Address structure (byte combination)
3. Frame maximum length
4. MV periodic cycle
5. Time format
6. Background scan cycle
7. T0: connection time-out
8. T1: APDU time-out
9. T2: acknowledgement time-out
10. T3: test frame time-out
11. K: sent unacknowledged frames (APDU)
12. W: acknowledged received frames (APDU)
13. Maximal command delay
14. SBO time-out
15. SOE file support
16. SOE file address, visible and significant if SOE file support set to Yes
17. SOE file format (T101/S900 extension), visible and significant if SOE file support set to
Yes
18. Maximum number of events per SOE file, visible and significant if SOE file support set
to Yes
19. Number of events for full SOE file message sent to SCADA (<Maximum number of
events per SOE file) , visible and significant if SOE file support set to Yes
C264/EN AP/B30 Application

Page 80/396 MiCOM C264/C264C

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)

(19)

FIGURE 85 : SETTING SPECIFIC ATTRIBUTES TO T104 SCADA NETWORK

Configuration rules and checks

• The following constraints between the attributes must be respected :

"SOE file nb of events" > "'full' SOE file nb of events"
"T2" < "T1"
"T3" > "T1"
"W" ≤ "K"
Application C264/EN AP/B30

MiCOM C264/C264C Page 81/396

4.7.1.6 Setting specific attributes of MODBUS SCADA network

When adding a SCADA network, the supported protocol must be updated (1). Here, set it to
‘MODBUS’. Then SCADA network tab-panes are refreshed relatively to the selected
protocol.

(1)

FIGURE 86 : SETTING PROTOCOL TYPE OF SCADA NETWORK

When setting a MODBUS SCADA network, some specific attributes available for the protocol
must be updated (Protocol tab-pane):
1. TCP/IP usage (Yes/No):
set to ‘Yes’ if substation network is used by the MODBUS SCADA to communicate
with the MiCOM C264 Computer
2. Link address, not significant if TCP/IP usage is set to ‘Yes’.
Setting SOE information SOE tab-panes, for MODBUS SCADA network is not significant
(not implemented).

(1)
(2)

FIGURE 87 : SETTING SPECIFIC ATTRIBUTES TO MODBUS SCADA NETWORK

C264/EN AP/B30 Application

Page 82/396 MiCOM C264/C264C

4.7.2 Defining addressing mapping of SCADA legacy network

To transmit information between PACiS system and SCADA, a SCADA legacy network is
used.
To receive or send information between legacy IED and PACiS system, each concerned
data must have a specific address on the legacy network relatively to its protocol. General
modelling of SCADA legacy network address mapping can be done. At SCE level, a SCADA
legacy network owns a “SCADA mapping” object, that is split in categories of mapping on a
per datapoint kind basis. In each category of mapping, elementary SCADA addresses can
be created. For details about datapoint, refer to chapter 5 DEFINING DATAPOINT. This
mapping is implicitly created during IED adding at legacy network level.
ADDRESSING MPS DATAPOINT ON SCALA LEGACY NETWORK IS NOT AVAILABLE.

Entry point of
SCADA mapping

Categories per
datapoint kind basis

C0181ENa

FIGURE 88 : STRUCTURE OF THE ADDRESSING MAPPING OF LEGACY SCADA NETWORK

Configuration rules and checks

• In the SCADA Mapping, the address identification of each "Gtw xxx addr." must be
unique. In the particular cases of T101 and T104 protocols, the uniqueness constraint
is applicable only for addresses of the same type. Addresses of different types can
have identical addresses and therefore this does not lead to an error but to a warning.

• On a DNP3 protocol, a "Gtw MV addr.", which is the SCADA address of a "Tap pos
ind" datapoint, must have its "Format" attribute set to the "Natural" value.
Application C264/EN AP/B30

MiCOM C264/C264C Page 83/396

4.7.2.1 Defining a SCADA address for SPS datapoint

An addition of a SCADA address for SPS datapoint is done under SCE via the “Object entry”
area at SCADA SPS mapping level by clicking on mouse’s right button.

FIGURE 89: ADDING A SCADA SPS ADDRESS

Once added, SCADA SPS address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Object address (register)
For T101/T104 protocol:
3. Object address
4. Event: (No / Yes with time tag)
when set to ‘Yes with time tag’, indicates if change of state of the datapoint are
transmitted spontaneously with time Tag
5. Event record:
When set to a value different from ‘Not involved in a transfer of file’, indicates if
change of state of the datapoint must be saved in Sequence of Event file. At MiCOM
C264 Computer level, values different from ‘Not involved in a transfer of file’ are
associated to the same treatment, because only one SOE file is managed by MiCOM
C264 Computer. The set of available values is maintained for compatibility with
MiCOM gateway addressing in MiCOM gateway.
6. Inversion: (No/Yes)
Indicates that the datapoint value needs to be inverted before transmission
7. Background scan: (No/Yes)
Indicates if the datapoint belongs to the background scan cycle
8. Group: (from 0 to 16)
Indicates to which “T101/T104 General Interrogation group” the datapoint is assigned.
0 means ‘no group’ assignation
For DNP3 protocol:
9. Object address (index)
10. Event: (No / Yes with time tag)
when set to ‘Yes with time tag’, indicates if change of state of the datapoint are
transmitted spontaneously with time Tag
11. Inversion: (No/Yes)
Indicates that the datapoint value needs to be inverted before transmission
C264/EN AP/B30 Application

Page 84/396 MiCOM C264/C264C

(1)

(2)

(3)
(4)
(5)
(6)
(7)
(8)

(9)

(10)

(11)

FIGURE 90: DEFINING A SCADA ADDRESS FOR SPS DATAPOINT

Application C264/EN AP/B30

MiCOM C264/C264C Page 85/396

4.7.2.2 Defining a SCADA address for DPS datapoint

An addition of a SCADA address for DPS datapoint is done under SCE via the “Object entry”
area at SCADA DPS mapping level by clicking on mouse’s right button.

FIGURE 91: ADDING A SCADA DPS ADDRESS

Once added, SCADA DPS address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Double address usage: (Yes/No)
only available for Modbus SCADA protocol.
If set to ‘Yes’, DPS is transmitted to SCADA via two distinct SCADA address, one for
the open state, the other one for the close state.
3. Object address:
used if ‘Double address usage’ is set to ‘No’
4. Open state address:
used if ‘Double address usage’ is set to ‘Yes’,
gives the SCADA address for the open state of the DPS
5. Closed state address:
used if ‘Double address usage’ is set to ‘Yes’,
gives the SCADA address for the closed state of the DPS
For T101/T104 protocol:
6. Object address
7. Event: (No / Yes with time tag)
when set to ‘Yes with time tag’, indicates if change of state of the datapoint are
transmitted spontaneously with time Tag
8. Event record:
When set to a value different from ‘Not involved in a transfer of file’, indicates if
change of state of the datapoint must be saved in Sequence of Event file. At MiCOM
C264 Computer level, values different from ‘Not involved in a transfer of file’ are
associated to the same treatment, because only one SOE file is managed by MiCOM
C264 Computer. The set of available values is maintained for compatibility with
MiCOM gateway addressing in MiCOM gateway.
9. Inversion: (No/Yes)
Indicates that the datapoint value needs to be inverted before transmission
10. Background scan: (No/Yes)
Indicates if the datapoint belongs to the background scan cycle
11. Group: (from 0 to 16)
C264/EN AP/B30 Application

Page 86/396 MiCOM C264/C264C

Indicates to which “T101/T104 General Interrogation group” the datapoint is assigned.

0 means ‘no group’ assignation
For DNP3 protocol:
12. Object address (index)
13. Event: (No / Yes with time tag)
when set to ‘Yes with time tag’, indicates if change of state of the datapoint are
transmitted spontaneously with time Tag
14. Inversion: (No/Yes)
Indicates that the datapoint value needs to be inverted before transmission

(1)

(2)

(3)
(4)
(5)

(6)
(7)
(8)
(9)
(10)

(11)

(12)

(13)

(14)

FIGURE 92: DEFINING A SCADA ADDRESS FOR DPS DATAPOINT

Application C264/EN AP/B30

MiCOM C264/C264C Page 87/396

4.7.2.3 Defining a SCADA address for MV datapoint

An addition of a SCADA address for MV datapoint is done under SCE via the “Object entry”
area at SCADA MV mapping level by clicking on mouse’s right button.

FIGURE 93: ADDING A SCADA MV ADDRESS

Once added, SCADA MV address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Address:
register number
3. Format: (Natural / unsigned normalized / signed normalized)
transmission format
4. Precision: (8 to 16)
number of transmitted bits
For T101/T104 protocol:
5. Address
6. Event: (No / Yes with time tag)
when set to ‘Yes with time tag’, indicates if change of state of the datapoint are
transmitted spontaneously with time Tag
7. Event record:
When set to a value different from ‘Not involved in a transfer of file’, indicates if
change of state of the datapoint must be saved in Sequence of Event file. At MiCOM
C264 Computer level, values different from ‘Not involved in a transfer of file’ are
associated to the same treatment, because only one SOE file is managed by MiCOM
C264 Computer. The set of available values is maintained for compatibility with
MiCOM gateway addressing in MiCOM gateway.
8. Format: (Normalized / Adjusted / Float)
transmission format
9. Cycle type: (None / Periodic / Background scan)
Indicates to which transmission cycle the MEAS belongs
10. Group: (from 0 to 16)
Indicates to which “T101/T104 General Interrogation group” the datapoint is assigned.
0 means ‘no group’ assignation
For DNP3 protocol:
11. Address
12. Event: (No / Yes with time tag)
C264/EN AP/B30 Application

Page 88/396 MiCOM C264/C264C

when set to ‘Yes with time tag’, indicates if change of state of the datapoint are
transmitted spontaneously with time Tag
13. Format: (Natural /Adjusted)

(1)

(2)
(3)
(4)

(5)
(6)
(7)
(8)
(9)
(10)

(11)
(12)
(13)

FIGURE 94: DEFINING A SCADA ADDRESS FOR MV DATAPOINT

Application C264/EN AP/B30

MiCOM C264/C264C Page 89/396

4.7.2.4 Defining a SCADA address for Counter datapoint

An addition of a SCADA address for Counter datapoint is done under SCE via the “Object
entry” area at SCADA Counter mapping level by clicking on mouse’s right button.

FIGURE 95: ADDING A SCADA COUNTER ADDRESS

Once added, SCADA Counter address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Address:
register number
3. Format: (Natural / unsigned normalized)
transmission format
For T101/T104 protocol:
4. Address
5. Event: (No / Yes with time tag)
when set to ‘Yes with time tag’, indicates if change of state of the datapoint are
transmitted spontaneously with time Tag
6. Group: (from 0 to ‘)
Indicates to which “T101/T104 General Interrogation group” the datapoint is assigned.
0 means ‘no group’ assignation
For DNP3 protocol:
7. Address
8. Event: (No / Yes with time tag)
when set to ‘Yes with time tag’, indicates if change of state of the datapoint are
transmitted spontaneously with time Tag
C264/EN AP/B30 Application

Page 90/396 MiCOM C264/C264C

(1)

(2)
(3)

(4)
(5)
(6)

(7)
(8)

FIGURE 96: DEFINING A SCADA ADDRESS FOR COUNTER DATAPOINT

Application C264/EN AP/B30

MiCOM C264/C264C Page 91/396

4.7.2.5 Defining a SCADA address for SPC datapoint

An addition of a SCADA address for SPC datapoint is done under SCE via the “Object entry”
area at SCADA SPC mapping level by clicking on mouse’s right button.

FIGURE 97: ADDING A SCADA SPC ADDRESS

Once added, SCADA SPC address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Address
For T101/T104 protocol:
3. Address
4. SCADA execute order type: (Select execute / Direct execute)
precise if SCADA uses a ‘Select execute” or a ‘Direct execute’ sequence to send
control on the datapoint.
For DNP3 protocol:
5. Address
6. SCADA execute order type: (Select execute / Direct execute)
precise if SCADA uses a ‘Select execute” or a ‘Direct execute’ sequence to send
control on the datapoint.
C264/EN AP/B30 Application

Page 92/396 MiCOM C264/C264C

(1)

(2)

(3)

(4)

(5)
(6)

FIGURE 98: DEFINING A SCADA ADDRESS FOR SPC DATAPOINT

Application C264/EN AP/B30

MiCOM C264/C264C Page 93/396

4.7.2.6 Defining a SCADA address for DPC datapoint

An addition of a SCADA address for DPC datapoint is done under SCE via the “Object entry”
area at SCADA DPC mapping level by clicking on mouse’s right button.

FIGURE 99: ADDING A SCADA DPC ADDRESS

Once added, SCADA DPC address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Address
For T101/T104 protocol:
3. Address
4. SCADA execute order type: (Select execute / Direct execute)
precise if SCADA uses a ‘Select execute” or a ‘Direct execute’ sequence to send
control on the datapoint.
For DNP3 protocol:
5. Address
6. SCADA execute order type: (Select execute / Direct execute)
precise if SCADA uses a ‘Select execute” or a ‘Direct execute’ sequence to send
control on the datapoint.
C264/EN AP/B30 Application

Page 94/396 MiCOM C264/C264C

(1)

(2)

(3)

(4)

(5)
(6)

FIGURE 100: DEFINING A SCADA ADDRESS FOR DPC DATAPOINT

Application C264/EN AP/B30

MiCOM C264/C264C Page 95/396

4.7.2.7 Defining a SCADA address for SetPoint datapoint

An addition of a SCADA address for SetPoint datapoint is done under SCE via the “Object
entry” area at SCADA SetPoint mapping level by clicking on mouse’s right button.

FIGURE 101: ADDING A SCADA SETPOINT ADDRESS

Once added, SCADA SetPoint address attributes must be set at SCE level:
1. Short and long names of the address used for internal SCE identification
For modbus protocol:
2. Address
For T101/T104 protocol:
3. Address
4. SCADA execute order type: (Select execute / Direct execute)
precise if SCADA uses a ‘Select execute” or a ‘Direct execute’ sequence to send
control on the datapoint.
5. Minimal value:
Available minimal value on the protocol (used for scaling and checks)
6. Maximal value:
Available maximal value on the protocol (used for scaling and checks)
7. Format: (Normalized / Adjusted / Float)
For DNP3 protocol:
8. Address
9. SCADA execute order type: (Select execute / Direct execute)
precise if SCADA uses a ‘Select execute” or a ‘Direct execute’ sequence to send
control on the datapoint.
10. Minimal value:
Available minimal value on the protocol (used for scaling and checks)
11. Maximal value:
Available maximal value on the protocol (used for scaling and checks)
12. Format: (Natural / Adjusted)
C264/EN AP/B30 Application

Page 96/396 MiCOM C264/C264C

(1)

(2)

(3)

(4)
(5)
(6)

(7)

(8)

(9)
(10)
(11)

(12)
Application C264/EN AP/B30

MiCOM C264/C264C Page 97/396

4.7.2.8 Figure 102: DEFINING A SCADA ADDRESS FOR SetPoint DATAPOINTDefining a SCADA
address for bypass synchrocheck
For details about synchronised circuit-breakers, refer to chapter 6.2 Defining Synchrocheck
function.
Synchronised circuit-breaker can be controlled through SCADA network. In that case, the
SPC (resp. DPC) control of the synchronised breaker is linked to a SCADA SPC (resp. DPC)
address. Unfortunately, bypass synchrocheck is not implemented in SCADA protocol. To
solve this problem, an extra SCADA SPC (resp. DPC) address that will bypass the
synchrocheck ,must be given to the SPC (resp. DPC) control of the breaker. At SCE level,
this extra address is linked to the SCADA address of the SPC (resp. DPC) control of the
synchronised breaker.
To define a SCADA address for bypass synchrocheck:

• Create the SCADA SPC (resp. DPC) address (A) to send SPC (resp. DPC) control of
the synchronised breaker

• Create a SCADA SPC (resp. DPC) address (B) for bypass synchrocheck in the
SCADA mapping,

• Add the relation ‘has for bypass synchrocheck address’ via the “Object entry” area at
SCADA address (A) and fill it with the SCADA address (B).

address (A)

address (B)

C0182ENa

FIGURE 103: ADDING A BYPASS SYNCHROCHECK ADDRESS TO A SCADA SPC/DPC ADDRESS

(E.G. FOR SCADA DPC ADDRESS)
4.7.3 Addressing datapoint on SCADA legacy network
For details about datapoint, refer to chapter 5 DEFINING DATAPOINT.
To exchange datapoint values between station-bus sub-systems and SCADA, datapoints
should be linked to specific SCADA addresses, by adding at datapoint level the relation ‘has
for SCADA address’ (1) and filling it with the corresponding SCADA address in a pre-
configured SCADA addressing mapping (refer to chapter 4.7.2 Defining addressing mapping
of SCADA legacy network, for SCADA mapping definition).
Addressing MPS datapoint on SCADA legacy network is not available.

(1)

FIGURE 104: REALISING SCADA ADDRESSING OF DATAPOINT

(E.G. FOR BAY SPS DATAPOINT)
C264/EN AP/B30 Application

Page 98/396 MiCOM C264/C264C

4.8 Defining wave record file management

PACiS MiCOM C264 Computers manage two kinds of wave recording file:

• IED connected to MiCOM C264 Computer legacy network, can produce disturbance
files. In that case, MiCOM C264 Computer monitors their availability. As soon as
available, they are uploaded and stored at MiCOM C264 Computer level. MiCOM
C264 Computer computes for System Management Tool (SMT) a real-time data per
IED basis, that gives the availability of a disturbance file, via station-bus network.
Then, SMT downloads it from MiCOM C264 Computer. At the end of successful
downloading, MiCOM C264 Computer erases the real-time data of availability.

• Via a CT/VT board (TMU200), MiCOM C264 Computer can manage its own waveform
record files. Waveform channels are directly acquired on CT/VT boards channels and
buffered. Triggered by pre-defined change of state, associated buffers are flushed on
files that corresponds to waveform record files. In that case MiCOM C264 Computer
computes for SMT a real-time data, that gives the availability of a MiCOM C264
Computer waveform record file, via station-bus network. Then processing is similar to
IED’s one.
4.8.1 Defining management of disturbance file for IED
Allowing MiCOM C264 Computer to manage IED disturbance is done at IED configuration
level by:

• Setting its ‘automatic disturbance’ attribute to yes (see chapter 4.6.1.8 Setting
attributes of legacy IED).

• Adding RDRE brick (1) for the IED in LD0 logical device of the UCA2 mapping of the
MiCOM C264 Computer (see chapter 4.5.2.1 Updating LD0 of MiCOM C264
Computer UCA2 mapping)

• Adding the system SPS datapoint ‘DREC ready’ (2) at IED level, linked to a pre-
defined datapoint profile,

• Fill the mandatory UCA2 address for this datapoint, with the relevant data object of the
RDRE brick (3)

(1)

(2)

FIGURE 105 : ADDING RDRE UCA2 BRICK AND DREC READY DATAPOINT FOR IED
Application C264/EN AP/B30

MiCOM C264/C264C Page 99/396

(3)

FIGURE 106 : SETTING UCA2 ADDRESS OF DREC READY DATAPOINT FOR IED
For T103 IED extra information must be configured to process correct disturbance file
COMTRADE structure at MiCOM C264 Computer level (see following chapter).
C264/EN AP/B30 Application

Page 100/396 MiCOM C264/C264C

4.8.2 Defining T103 IED extra information for disturbance file

T103 extra information for disturbance file are located at T103 acquisition type (whose
details are given in chapter 4.6.1.10 Setting attributes of T103 acquisition type) and concern
definition of analog and digital channels, stored in disturbance file, relatively to COMTRADE
format.
4.8.2.1 Adding an analog channel definition
An addition of an analog channel definition for T103 is done under SCE via the “Object entry”
area at T103 acquisition type level by clicking on mouse’s right button. Up to 15 analog
channels can be created under a T103 acquisition type.

FIGURE 107: ADDING A T103 ANALOG CHANNEL DEFINITION

Once added, channel definition attributes must be set at SCE level:
1. Channel label
2. Long names of the channel used for internal SCE identification
3. Phase name:
Label of the phase corresponding to the channel
4. Channel number:
(cf. mapping IED – field ACC in IEC 60870-5-103 documentation
5. Unit:
unit corresponding to the channel
6. Coefficient:
Value by which the samples must be multiplied in order to get the real value.
(0: not used)
Generally, data uploaded from IED allows to compute this ‘multiply coefficient’.
Unfortunately, some IED doesn’t give correct data ! In this case, this coefficient must
be set here.
7. Shift time:
elapsed time since the beginning of the sampling period
8. Maximal sample value
9. Minimal sample value
Application C264/EN AP/B30

MiCOM C264/C264C Page 101/396

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)

FIGURE 108: SETTING T103 ANALOG CHANNEL DEFINITION

For more details about the analog channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
C264/EN AP/B30 Application

Page 102/396 MiCOM C264/C264C

4.8.2.2 Adding a digital channel definition

An addition of a digital channel definition for T103 is done under SCE via the “Object entry”
area at T103 acquisition type level by clicking on mouse’s right button. Up to 255 digital
channels can be created under a T103 acquisition type.

FIGURE 109: ADDING A T103 DIGITAL CHANNEL DEFINITION

Once added, channel definition attributes must be set at SCE level:
1. Channel label
2. Long names of the channel used for internal SCE identification
3. Function number:
corresponds to function type of the channel in T103 protocol
4. Information number:
corresponds to information number of the channel in T103 protocol
5. Default state (Off/On)

(1)
(2)
(3)
(4)
(5)

FIGURE 110: SETTING T103 DIGITAL CHANNEL DEFINITION

For more details about the digital channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
Application C264/EN AP/B30

MiCOM C264/C264C Page 103/396

4.8.3 Defining management of wave record file for MiCOM C264 Computer CT/VT board
Allowing MiCOM C264 Computer to manage its own wave record file is done at MiCOM
C264 Computer configuration level by:

• Defining a fast and/or slow waveform recording (see following chapters):

− Fast waveform recording gives access to samples acquired via CT/VT board

− Slow waveform recording gives access to analogues (MV) and digital values
(SPS, DPS, SPC, DPC) file recording.

• Adding RDRE brick (1) for the MiCOM C264 Computer in LD0 logical device of the
UCA2 mapping of the MiCOM C264 Computer (see chapter 4.5.2.1 Updating LD0 of
MiCOM C264 Computer UCA2 mapping)

• Adding the system SPS datapoint ‘C26x DREC ready’ (2) at MiCOM C264 Computer
level, linked to a pre-defined datapoint profile,

• Fill the mandatory UCA2 address for this datapoint, with the relevant data object of the
RDRE brick (3)

(1)

(2)

FIGURE 111 : ADDING RDRE UCA2 BRICK AND DREC READY DATAPOINT FOR MICOM C264
COMPUTER

(3)

FIGURE 112 : SETTING UCA2 ADDRESS OF DREC READY DATAPOINT FOR MICOM C264
COMPUTER
C264/EN AP/B30 Application

Page 104/396 MiCOM C264/C264C

4.8.3.1 Defining fast waveform recording

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

Number of Files Number of cycles

8 60
4 120
2 240
1 480

The waveform recorder can be triggered by the following events, each of which is user
configurable :

• Changes in state of binary inputs (SPS or DPS datapoint)

• Changes in state of digital outputs (SPC or DPC datapoint)

• Measurement threshold violations (MV datapoint)

• Operator request
Only one re-trig is allowed : it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are stored using COMTRADE 97 binary format.
An addition of a fast waveform recording is done under SCE via the “Object entry” area at
MiCOM C264 Computer level by clicking on mouse’s right button. Only one fast waveform
recording can be created under a MiCOM C264 Computer.

FIGURE 113: ADDING A FAST WAVEFORM RECORDING

Application C264/EN AP/B30

MiCOM C264/C264C Page 105/396

Once added, fast waveform recording attributes must be set at SCE level:
1. Short and long names of the recording used for internal SCE identification
2. Pre-trigger cycle:
corresponds to number of cycles (up to 480), that are stored before triggering.
3. Total cycles:
see previous description
4. Number of files:
see previous description

(1)

(2)
(3)
(4)

FIGURE 114: SETTING FAST WAVEFORM RECORDING

To define the inputs of a fast waveform recording, just add the relevant relation (1) available
at recording level and fill the relation with proper CT/VT channel or datapoint. Be careful,
only CT/VT channels and datapoints acquired on the MiCOM C264 Computer can be
defined as input of its fast waveform recording.

(1)

FIGURE 115: DEFINING INPUTS OF FAST WAVEFORM RECORDING

To define the triggers of a fast waveform recording, just add the relevant relation (2)
available at recording level and fill the relation with proper datapoint. Be careful, only
datapoints acquired on the MiCOM C264 Computer can be defined as input of its fast
waveform recording.
C264/EN AP/B30 Application

Page 106/396 MiCOM C264/C264C

(2)

FIGURE 116: DEFINING TRIGGERS OF FAST WAVEFORM RECORDING

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

Triggering state for SPS :

Off,On or Off+On

Triggering state for DPS :

Open,Closed or Open+Closed

Triggering state for SPC :

Reset,Set or Reset+Set

Triggering state for DPC :

Open,Close or Open+Close

Triggering thresholds for

MV .
For each threshold:
- No t rigger
- trigger on threshold shot
- trigger on threshold reset
- trigger on threshold shot
and reset

C0183ENa

FIGURE 117: DEFINING TRIGGERS CONDITIONS OF FAST WAVEFORM RECORDING

Configuration rules and checks

• The following constraints between the attributes must be respected :

- "pre-trigger cycle" ≤ "total cycles"
- "number of files" ∗ "total cycles" ≤ 480 cycles
Application C264/EN AP/B30

MiCOM C264/C264C Page 107/396

4.8.3.2 Defining slow waveform recording

The inputs for the slow waveform records are :

• MV datapoint coming from CT VT computation (refer to chapter 5.6.4.4 Explicit

electrical input datapoint via CT/VT computation)

• MV datapoint coming from AIU boards.

• SPS or DPS datapoints

• SPC or DPC datapoints

The slow wave form manages up to 24 analogues (MV) and 48 digital values (SPS, DPS,
SPC, DPC).
MiCOM C264 stores at maximum 5000 integrated values as follow:

Number of Files Number of integrated values

1 5000
2 2500
5 1000
10 500
20 250
50 100

The integrated value has duration up to one hour. It is defined in configuration.

For analogue, the stored value is the average value during integrated period.
For digital, the stored value depends also on the average:
If average value > x then the stored value is 1 else it is 0, x is defined in configuration and it
is a value between 0.1 and 0.9.
The slow waveform recorder can be triggered by the following events, each of which is user
configurable :

• Changes in state of binary inputs (SPS or DPS datapoint)

• Changes in state of digital outputs (SPC or DPC datapoint)

• Measurement threshold violations (MV datapoint)

• Operator request

• Periodically ( i.e. every day at 00h00)

An addition of a slow waveform recording is done under SCE via the “Object entry” area at
MiCOM C264 Computer level by clicking on mouse’s right button. Only one slow waveform
recording can be created under a MiCOM C264 Computer.
C264/EN AP/B30 Application

Page 108/396 MiCOM C264/C264C

FIGURE 118: ADDING A SLOW WAVEFORM RECORDING

Once added, slow waveform recording attributes must be set at SCE level:
1. Short and long names of the recording used for internal SCE identification
2. Pre-trigger cycle:
corresponds to number of cycles (up to 480), that are stored before triggering.
3. Total records (up to 5000):
see previous description
4. Number of files (up to 50):
see previous description
5. Arbitration period:
This data represents the % of time during which the logical data must be set to 1 to
consider the integrated data set to 1
6. Integration time:
see previous description.
Data unit is number of cycles and has the following range:
- [1, 180000] if electric network frequency is 50 Hz
- [1, 216000] if 60 Hz
(for network frequency configuration, refer to chapter 4.3.2 Configuring measurement
acquisition and transmission)
7. Activation period:
see previous description
Available value are: non periodic, daily, weekly or daily+weekly

(1)

(2)
(3)
(4)
(5)
(6)

(7)

FIGURE 119: SETTING FAST WAVEFORM RECORDING

Application C264/EN AP/B30

MiCOM C264/C264C Page 109/396

To define the inputs of a slow waveform recording, just add the relevant relation (1) available
at recording level and fill the relation with proper datapoint. Be careful, only datapoints
acquired on the MiCOM C264 Computer can be defined as input of its slow waveform
recording.

(1)

FIGURE 120: DEFINING INPUTS OF SLOW WAVEFORM RECORDING

To define the datapoint-triggers of a slow waveform recording, just add the relevant relation
(2) available at recording level and fill the relation with proper datapoint. Be careful, only
datapoints acquired on the MiCOM C264 Computer can be defined as input of its slow
waveform recording. A slow waveform can be configured without any datapoint-trigger, if a
daily or weekly activation period has been defined for it.

(2)

FIGURE 121: DEFINING TRIGGERS OF FAST WAVEFORM RECORDING

Depending on datapoint type, extra attributes must be set for ‘has for trigger’ relation. These
attributes gives the datapoint states (or thresholds for MV) that trig the record (see following
figure)
C264/EN AP/B30 Application

Page 110/396 MiCOM C264/C264C

Triggering state for SPS:

Off,On or Off+On

Triggering state for DPS:

Open,Closed or Open+Closed

Triggering state for SPC:

Reset,Set or Reset+Set

Triggering state for DPC:

Open,Close or Open+Close

Triggering thresholds for

MV .
For each threshold:
- No t rigger
- trigger on threshold shot
- trigger on threshold reset
- trigger on threshold shot
and reset

C0184ENa

FIGURE 122: DEFINING TRIGGERS CONDITIONS OF SLOW WAVEFORM RECORDING

Configuration rules and checks

• The following constraints between the attributes must be respected :

- "pre-trigger cycle" < "total records"
- "number of files" ∗ "total records" < 5000 records

• If "electrical frequency" ≡ 50 Hz :
- The "integration time" value must be in the range [1..180000].
- If the "integration time" value is > 5, then no DPC, SPC, DPS, SPS recording is
allowed.

• If "electrical frequency" ≡ 60 Hz :
- The "integration time" value must be in the range [1..216000].
- If the "integration time" value is > 6, then no DPC, SPC, DPS, SPS recording is
allowed.
Application C264/EN AP/B30

MiCOM C264/C264C Page 111/396

4.9 Defining MiCOM C264 Computer klaxon

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

(1)

FIGURE 123: DEFINING MICOM C264 COMPUTER KLAXON

Configuration rules and checks

• The "SPC" link of the relation "has its klaxon controlled by" must be wired on a DO
channel of the MiCOM C264 Computer.
C264/EN AP/B30 Application

Page 112/396 MiCOM C264/C264C

4.10 Setting system information for MiCOM C264 Computer components

When creating a MiCOM C264 Computer, specific datapoints are automatically added in
‘system infos’ binder (1) at MiCOM C264 Computer level or PLC sub-component.
So it is when adding a board (2), an IED on legacy network (3), a serial printer (4), or a
SCADA network (5) attached to a MiCOM C264 Computer. In that case, the ‘system infos’
binder is located under the relevant added object.
For extra MiCOM C264 Computer functionalities (wave recording, redundancy), some
optional datapoints can be required.
SCE calls such ‘system infos’ datapoints, system datapoints.
System datapoints provide real-time statuses and controls on system software or hardware
components, and generally can not be wired on board channels except for redundancy
function.
As datapoint, system datapoints must be linked to a profile. For details about datapoint and
datapoint profile configuration, refer to chapter 5 DEFINING DATAPOINT). Depending on its
the kind, the system datapoint and its relevant profile have specific attributes to be set
correctly to insure healthy behaviour of MiCOM C264 Computer. Hereafter, are listed the
datapoint and profile requirements for each kind of system datapoint.
Generally system datapoints are automatically addressed in UCA2 mapping of the relevant
MiCOM C264 Computer at their creation. If manual addressing is necessary, it is stressed in
following chapters by given the associated available data object of a given MiCOM C264
Computer brick in LD0 (⇔<brick name>.<data object name>). For details about UCA2
addressing see chapter 4.5 Networking MiCOM C264 Computer on the station-bus network.

(2)

(4)

(3)

(1)

(5)

FIGURE 124 : ‘SYSTEM INFOS’ BINDERS FOR MiCOM C264 COMPUTER

Application C264/EN AP/B30

MiCOM C264/C264C Page 113/396

4.10.1 Setting general system information of MiCOM C264 Computer

When creating a MiCOM C264 Computer, the following mandatory datapoints are implicitly
added and must be configured (see chapter 5 DEFINING DATAPOINT) according to their
described features:

• Controls and statuses for functioning mode

− Device mode DPS (11)

Gives the current functioning mode of the MiCOM C264 Computer.

UCA2 addressing Available states

⇔ GLOBE.ModeDS • ‘JAMMED’: Test
Automatic at datapoint creation • ‘OPEN’: Maintenance
• ‘CLOSED’: Operational/Run
• ‘UNDEFINED’: Faulty

− Operating mode MPS (13)

Is the MPS equivalence of Device mode DPS (11)
Can not be used by other PACiS sub-system (no UCA2 address).

UCA2 addressing Available states

Can not be addressed on UCA2 • ‘STATE0’: Faulty
• ‘STATE1’: Operational/Run
• ‘STATE3’: Test
• ‘STATE5’: Maintenance

− Mode control DPC (18)

Only used by SMT tools to turn device functioning mode to Maintenance or
Operational/Run

UCA2 addressing Available states

⇔ GLOBE.ODMode • ‘OPEN’: Maintenance
Automatic at datapoint creation • ‘CLOSE’: Operational/Run

− Test control DPC (19)

Only used by SMT tools to turn device functioning mode to Test or Normal

UCA2 addressing Available orders

⇔ GLOBE.ODTest • ‘OPEN’: Test
Automatic at datapoint creation • ‘CLOSE’: Normal

• Control and status for local/remote

− Local/remote DPS (12)

Is a synthesis of all Local/remote of bays managed by the MiCOM C264
Computer: as soon as one bay is in remote, the MiCOM C264 Computer is in
remote; when all managed bays are in local, the MiCOM C264 Computer is in
local.

UCA2 addressing Available states

⇔ GLOBE.LocRemDS • ‘OPEN’: Remote
Automatic at datapoint creation • ‘CLOSED’: Local
C264/EN AP/B30 Application

Page 114/396 MiCOM C264/C264C

− Local/remote control DPC (17)

Is required by UCA2 protocol but is meaningless for MiCOM C264 Computer

UCA2 addressing Available orders

⇔ GLOBE.ODLocRem • ‘OPEN’: Remote
Automatic at datapoint creation • ‘CLOSE’: Local

• Control and status for database management

− Database compatibility SPS (1)

Is put in ‘RESET’ state if current database is not compatible with the MiCOM C264
Computer release. In that case, MiCOM C264 Computer goes in Maintenance.
Can not be used by other PACiS sub-system (no UCA2 address).

UCA2 addressing Available states

Can not be addressed on UCA2 • ‘RESET’: Not compatible
• ‘SET’: Compatible

− Database incoherency SPS (2)

Is put in ‘SET’ state if current database is not self-consistent. In that case, MiCOM
C264 Computer goes in Maintenance.
Can not be used by other PACiS sub-system (no UCA2 address).

UCA2 addressing Available states

Can not be addressed on UCA2 • ‘RESET’: Coherent
• ‘SET’: Not coherent

− Database switch control SPC (14)

Only used by SMT tools to turn device functioning mode to Maintenance or
Operational/Run

UCA2 addressing Available states

⇔ DBID.ODDBSw • ‘ON’: Switch
Automatic at datapoint creation

• Synchronisation status

− Synchronisation SPS (9)

Is put in ‘SET’ state if device is synchronised.

UCA2 addressing Available states

⇔ C26xDIAG.SyncSt • ‘RESET’: Not synchronised
Automatic at datapoint creation • ‘SET’: Synchronised

• Communication status

− Device link SPS (3)

Although this datapoint is under the MiCOM C264 Computer, it is not managed by
it. Each UCA2 client of the MiCOM C264 Computer computes locally this
datapoint status by supervising the UCA2 real-time link with the MiCOM C264
Computer. In fact, there are as many ‘Device link SPS’ per MiCOM C264
Computer basis as UCA2 clients connected to the MiCOM C264 Computer.
Is put in ‘SET’ state if device link is operational.
Application C264/EN AP/B30

MiCOM C264/C264C Page 115/396

UCA2 addressing Available states

Can not be addressed on UCA2. • ‘RESET’: Not OK
Managed locally by each UCA2 • ‘SET’: OK
client

• Health statuses

− Acquisition stopped SPS (4)

In case of saturation of acquisition on DIU board (internal fifo overflow), DI
acquisition is automatically stopped and this datapoint is put in ‘SET’ state. As
soon as fifo is un-saturated, the datapoint is reset and DI acquisition restarts.

UCA2 addressing Available states

Can not be addressed on UCA2. • ‘RESET’: Acquisition running
• ‘SET’: Acquisition stopped

− Software error SPS (7)

In case of software error, this datapoint is set and MiCOM C264 Computer goes in
faulty mode.
Can not be used by other PACiS sub-system (no UCA2 address).

UCA2 addressing Available states

Can not be addressed on UCA2. • ‘RESET’: Software running
• ‘SET’: Software error

− Software compatibility SPS (8)

<ADU>

− Watchdog SPS (10)

In case of software watchdog time-out, this datapoint is put in ‘SET’ state and
MiCOM C264 Computer goes in Faulty mode.

UCA2 addressing Available states

Can not be addressed on UCA2. • ‘RESET’: Watchdog OK
• ‘SET’: Watchdog time-out

− ISaGRAF status MPS (26)

<ADU>

• Control and statuses for redundancy management:

The following datapoints are used internally by MiCOM C264 Computer if it is
redunded. these datapoints must be linked to datapoint profiles by default for proper
behaviour of redundancy. No UCA2 address are available.

− Redundancy change mode SPS (5)

− Redundancy change status SPS (6)
− Redundancy mode control SPC (15)
− Redundancy status control SPC (16)
− Main status MV (20)
C264/EN AP/B30 Application

Page 116/396 MiCOM C264/C264C

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
(26)

FIGURE 125 : MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR MiCOM C264 COMPUTER
At MiCOM C264 Computer level, the following optional datapoint can be added and must be
configured (see chapter 5 DEFINING DATAPOINT) according to their described features:

• C26x disturbance status SPS (21)

This datapoint indicates the availability of a waveform record file for the MiCOM C264
Computer (for details, refer to chapter 4.8 Defining wave record file management). It is
put to ‘SET’ state, if file is available.

UCA2 addressing Available states

⇔ RDRE.DrSt • ‘RESET’: No file available
Must be explicitly addressed on • ‘SET’: File available
UCA2.
Application C264/EN AP/B30

MiCOM C264/C264C Page 117/396

• Counter Top SPS (22)

This datapoint is used to launch the transmission of counters value on UCA2 and
SCADA networks. Launching is done when the datapoint goes in ‘SET’ state. This
datapoint is generally wired.

UCA2 addressing Available states

Can be manually addressed on • ‘RESET’: No transmission
UCA2.
• ‘SET’: Transmission

• External clock status SPS (23)

This datapoint indicates the status of the IRIG-B synchronisation. This datapoint is
mandatory if ‘synchronisation source’ attribute at MiCOM C264 Computer level is set
to IRIG-B (for details, refer to chapter 4.3 Setting specific parameterisation of MiCOM
C264 Computer). It is put to ‘SET’ state, if IRIG-B signal is present.

UCA2 addressing Available states

Can be manually addressed on • ‘RESET’: Lack of signal
UCA2.
• ‘SET’: Signal present

• Redundancy mode SPS (24)

The following datapoint must be added and is used internally by MiCOM C264
Computer if it is redunded. this datapoint must be linked to datapoint profiles by
default for proper behaviour of redundancy. No UCA2 address is available.

• Signal on time SPS (25)

<ADU>

(21)
(22)
(23)
(24)
(25)

FIGURE 126 : OPTIONAL ‘SYSTEM INFOS’ DATAPOINT FOR MICOM C264 COMPUTER
C264/EN AP/B30 Application

Page 118/396 MiCOM C264/C264C

4.10.2 Setting system information of board

When creating a board (except CPU board), the following mandatory datapoint is implicitly
added and must be configured (see chapter 5 DEFINING DATAPOINT) according to its
described features:

• Board status MPS (1)

This datapoint indicates the status of the board.
Addressing this datapoint on UCA2 can be done :
- by using ‘UCA2 automatic addressing function’ (refer to chapter 4.5.2.4 Creating
application Logical device automatically by using UCA automatic addressing).
- Manually. In that case, the relevant data object given the UCA2 address of the
status, must be coherent with the board number (e.g. if AIU board number is 3,
corresponding data object is AIUSt3)

UCA2 addressing Available states

⇔ C26xDIAG.<kind>St<i> • ‘STATE0’: Board OK
where
-<kind> corresponds to board type • ‘STATE1’: Self-check failure
(GHU, BIU, CCU, DIU, DOU, AIU,
TMU) • ‘STATE2’: Configured but missing
- <i> corresponds to the board • ‘STATE3’: Not configured but present
number (from 0). <i> does not exist if
board is unique (GHU, BIU, TMU) • ‘STATE4’: Missing
• Manually addressed in UCA2
DIAG brick of the MiCOM
C264 Computer.
Or
• UCA2 Automatic addressing
usage.

(1)

FIGURE 127 : MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR BOARD

(E.G. FOR AIU BOARD)
Application C264/EN AP/B30

MiCOM C264/C264C Page 119/396

4.10.3 Setting system information of legacy IED

When creating a legacy IED, the following mandatory datapoints are implicitly added and
must be configured (see chapter 5 DEFINING DATAPOINT) according to their described
features:

• IED communication status SPS (1)

Is put in ‘SET’ state if communication with the IED is operational.

UCA2 addressing Available states

⇔ <IED>DIAG.CommSt • ‘RESET’: Communication not OK
Automatic at datapoint creation • ‘SET’: Communication OK

• IED synchronisation status SPS (2)

Is put in ‘SET’ state if IED is synchronised.

UCA2 addressing Available states

⇔ <IED>DIAG.SyncSt • ‘RESET’: Not synchronised
Automatic at datapoint creation • ‘SET’: Synchronised

(1)

(2)

FIGURE 128 : MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR LEGACY IED

At IED level, the following optional datapoint can be added and must be configured (see
chapter 5 DEFINING DATAPOINT) according to their described features:

• IED disturbance status SPS (3)

This datapoint indicates the availability of a disturbance file for the IED (for details,
refer to chapter 4.8.1 Defining management of disturbance file for IED). It is put to
‘SET’ state, if file is available.

UCA2 addressing Available states

⇔ <IED>RDRE.DrSt • ‘RESET’: No file available
Must be explicitly addressed on • ‘SET’: File available
UCA2.

(3)

FIGURE 129 : OPTIONAL ‘SYSTEM INFOS’ DATAPOINT FOR LEGACY IED

C264/EN AP/B30 Application

Page 120/396 MiCOM C264/C264C

4.10.4 Setting system information of serial printer

When creating a serial printer, the following mandatory datapoint is implicitly added and must
be configured (see chapter 5 DEFINING DATAPOINT) according to its described features:

• Printer status MPS (1)

This datapoint indicates the status of the printer.
Addressing this datapoint on UCA2 can be done :

− By using ‘UCA2 automatic addressing function’ (refer to chapter 4.5.2.4 Creating

application Logical device automatically by using UCA automatic addressing).

− Manually. In that case, the relevant data object given the UCA2 address of the
status, must be ‘PrintSt’ in the MiCOM C264 Computer C26xDIAG brick.

UCA2 addressing Available states

⇔ C26xDIAG.PrintSt • ‘STATE0’: Printer OK
Manually addressed in UCA2 • ‘STATE1’: Self-check failure
DIAG brick of the MiCOM C264
Computer. • ‘STATE2’: Configured but missing

Or • ‘STATE3’: Not configured but present

UCA2 Automatic addressing • ‘STATE4’: Missing
usage.

(1)

FIGURE 130 : MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR SERIAL PRINTER

Application C264/EN AP/B30

MiCOM C264/C264C Page 121/396

4.10.5 Setting system information of SCADA network

When creating a SCADA network, the following mandatory datapoints are implicitly added
and must be configured (see chapter 5 DEFINING DATAPOINT) according to their described
features:

• SCADA communication status SPS (1)

Is put in ‘SET’ state if communication with the SCADA is operational.

UCA2 addressing Available states

⇔ <TCI>DIAG.CommSt • ‘RESET’: Communication not OK
Automatic at datapoint • ‘SET’: Communication OK
creation

• SCADA redundancy status SPS (2)

Is put in ‘SET’ state if redundancy with the SCADA is active.

UCA2 addressing Available states

⇔ <TCI>DIAG.RedSt • ‘RESET’: StandBy
Automatic at datapoint • ‘SET’: Active
creation

(2)

(1)

FIGURE 131 : MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR SCADA NETWORK

C264/EN AP/B30 Application

Page 122/396 MiCOM C264/C264C

5. DEFINING DATAPOINT
5.1 Creating datapoint
Electrical and system topologies share entities called Datapoint. Datapoint corresponds to
atomic object with real-time value, status or control relevant to electrical or system process.
Moreover, datapoint supports extra system function like forcing, suppression, filtering, and
alarms, logging (cf. ALSTOM PACiS Product Specifications).
Several kinds of datapoint exist:

• Input datapoint kinds used for supervision:

− SPS (Single Point Status), DPS (Double Point Status), MPS (Multiple Point
Status)

− MV (Measurement Value), Counter

• Output datapoint kinds used for control:

− SPC (Single Point Control), DPC (Double Point Control)

− Setpoint
Input datapoints can be acquired through sensors (input channels), addressed on IED at
IED legacy network level or substation network level. They can also be calculated or
deduced by the system devices. They can be sent to SCADA by addressing them on
SCADA networks.
Output datapoints can be controlled through relays (output channels), addressed on IED at
IED legacy network level or substation network level or on SCADA networks. They can also
be managed by built-in or user functions.
At SCE level, datapoints belonging to the system topology are called system datapoints, and
those of the electrical topology are named electrical datapoints.
Generally, system datapoint creation is automatic when adding system devices or sub-
components to system devices. They are never wired, except for system datapoint used by
redundancy and more often correspond to system diagnostics (device, printer board status,
control of device mode, …).
Electrical datapoint creation is rarely automatic except when they are required for correct
PACiS system behaviour (for instance, ‘Order running SPS’ at bay level, ‘Computed
switchgear position’ at circuit-break level), or relevant to an electrical built-in function that
imposes their existence.
Be careful:
(Refer to chapter 4.5.1 Connecting MiCOM C264 Computer to others station-bus sub-
systems, for Client / Server definition)
In the set of all the MiCOM C264 Computers of a Scs, the previous described SPS attributes
(except short and long names) are only useful and given to the MiCOM C264 Computer that
serves the datapoint because the relevant functions are always done at MiCOM C264
Computer server level.
Application C264/EN AP/B30

MiCOM C264/C264C Page 123/396

5.1.1 Overview of binary input processing

This chapter is an introduction to SPS, DPS and MPS datapoint definition. It deals with
general processing and features associated to these kinds of datapoints, for better
comprehension of their configuration.

There are five types of Binary inputs :

• Single Point Status (SPS) : derived from one Digital input

• Double Point Status (DPS) : derived from two Digital inputs

• Multiple Point Status (MPS) : derived from N Digital inputs

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

SPS, DPS and MPS are mainly acquired via digital input boards (DIU board) or via IEDs
connected by a serial link (for details see chapter 5.6 Defining acquisition source for input
datapoints).
By extension, at SCE level:

• System inputs (SI) are seen as particular SPS, DPS or MPS depending on the number
of elementary information they represents (for details about SI, see chapter4.10
Setting system information for MiCOM C264 Computer components).

• Group binary input is seen as particular SPS (for detail about Group, see chapter
5.6.4.2 Implicit electrical input datapoint via built-in function)
5.1.1.1 Toggling inputs
A digital input is said to be toggling if its state has changed more than N times within a given
period of time T (for details, see chapter 4.3.1 Configuring binary input (BI) filtering).
A SPS associated with a toggling DI is in the TOGGLING state.
A DPS or a MPS whose one of the associated DI is toggling is in the TOGGLING state.
5.1.1.2 Manual suppression
A binary input can be suppressed by an order issued from an operator. No subsequent
change of state on a suppressed BI can trigger any action e.g. display, alarm, transmission.
The BI takes the “SUPPRESSED” state. When the operator unsuppresses the BI, this one
takes its actual state.
5.1.1.3 Substitution
An operator can substitute a BI to a manual set state (state “SUBSTITUTED xxx”). The BI
stays in the state determined by the operator until he unsubstitutes it.
When a BI is substituted, no changes of state are transmitted, and computations, for
instance groupings, are made with the substituted state. When the BI is unsubstituted, the
actual state is transmitted to higher control levels and subsequent changes of state are
transmitted again.
5.1.1.4 Forcing of invalid BI's
When an information is invalid (i.e. SELFCHECK FAULTY, TOGGLING, UNDEFINED or
UNKNOWN), it can be manually forced by a user (state “FORCED xxx”). This feature is
similar to the substitution but the information is automatically updated when valid information
is available again. A SUPPRESSED or SUBSTITUTED datapoint cannot be forced.
The forcing could also be automatic : in this case, the invalid information takes automatically
the state defined in configuration.
C264/EN AP/B30 Application

Page 124/396 MiCOM C264/C264C

5.1.1.5 Faulty indication

Following a faulty indication of a physical DI, the associated SPS, DPS or MPS becomes
SELFCHECK FAULTY.
5.1.1.6 Transmission
The BIs are transmitted on a client-server basis on the UCA2 network. Refer to chapter 4.5
Networking MiCOM C264 Computer on the station-bus network for more information on
UCA2.
During a loss of communication between a client and a server, all server BI are set to
UNKNOWN state on the client.
5.1.2 Defining SPS datapoint
5.1.2.1 Overview of SPS processing
At MiCOM C264 Computer level, the processing of a SPS can be represented by the
following data flow :

Toggle filtering
(DI acquisition)

IED inputs
(IED acquisition)

System Inputs

Manual suppression DI/DO

association
Substitution
Group
Forcing
processing

Persistance filtering Transmission–

Report based

To RCP
To HMI (views, lists)
To Data Logging
To archive

Transmission–
GOOSE based

To automation
C0185ENa

FIGURE 132 : SPS PROCESSING

Application C264/EN AP/B30

MiCOM C264/C264C Page 125/396

5.1.2.2 Definition of SPS states

Basically, a SPS is acquired on one digital input channel of a DIU board, and so has got two
fundamental states: RESET and SET depending on the physical state of the associated DI.
By combination with binary input processing done at MiCOM C264 Computer level (see
chapter 5.1.1 Overview of binary input processing), the SPS resulting states are :

• RESET

• SET

• TOGGLING

• SELFCHECK FAULTY

• UNKNOWN

• SUPPRESSED

• FORCED RESET

• FORCED SET

• SUBSTITUTED RESET

• SUBSTITUTED SET
5.1.2.3 Definition of SPS persistence filtering
For some SPS, a transition must be confirmed on a certain period of time. If the opposite
transition occurs before this delay, both transitions are discarded.
Two time-out values can be associated with each SP :

• TS : delay for the SET state confirmation

• TR : delay for the RESET state confirmation

Both delays are in the range 0 to 120 s by step of 100 ms. A value of 0 means that no filter is
applied.
The time tag is user-selectable :

• Mode 1 : the status is stamped with the time of the transition

• Mode 2 : the status is stamped at the end of the delay.

C264/EN AP/B30 Application

Page 126/396 MiCOM C264/C264C

TS TS
TR TR

SET
SP before filtering
RESET

SET
SP after filtering, mode 1
RESET

SET
SP after filtering, mode 2
RESET

t0 t1 t2 t3 t4 t5 t6 t7

· t0 : RESET to SET transition

· t1 : SET to RESET transition ; SET state not confirmed. The
transitionis discarded (TR is not launched because there is no
change of state).
· t2 : RESET to SET transition
· t3 : SET state confirmed (stamped t2 if mode 1, stamped t3
if mode 2)
· t4 : SET to RESET transition
· t5 : RESET to SET transition; RESET state not confirmed. The
transitionis discarded (TS is not launched because there is no
change of state).
· t6 : SET to RESET transition
· t7 : RESET state confirmed (stamped t6 if mode 1, stamped t7 if
mode 2)
C0186ENa

FIGURE 133 : SPS PERSISTENCE FILTERING

5.1.2.4 Creating SPS datapoint
To create SPS datapoint:

• Add a SPS from object entry available at the wished system or electrical object level
(1). Depending of the object level, different pre-defined kinds of SPS exist. They are
used for specific needs at electrical topology level (for details see relevant sub-chapter
in 6 DEFINING MICOM C264 COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see chapter 4.10 Setting
system information for MiCOM C264 Computer components).

• Update the SPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPS.

• Update its relation ‘has for profile’ to point to a specific existing profile (2). See chapter
5.2 Linking datapoint to profile, for details about profile definition and setting.
Application C264/EN AP/B30

MiCOM C264/C264C Page 127/396

(1)

FIGURE 134: ADDING A SPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)

(2)

FIGURE 135: LINKING SPS DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
Updating SPS attributes (description for generic SPS)
When adding a generic SPS datapoint, some general attributes must be updated:
1. Short and long names of the datapoint used for logging, alarms ...
2. Detection mode : Permanent or Transient
3. Time reference for stable state: at start of filtering or end of filtering
4. TR : Confirmation delay for stable ‘reset’ state (0 to 120 s by 100 ms)
5. TS : Confirmation delay for stable ‘set’ state (0 to 120 s by 100 ms)
6. Forcing management:
when a SPS goes in invalid state, MiCOM C264 Computer can force or not its status
to set or reset state automatically. This attribute defines the way this forcing
management is done (Not automatic, automatic to reset state, automatic to set state).
Automatic forcing management is independent of FSS facility gives at user by the SPS
profile.
7. State panel assignment (Yes/No): set to ‘yes’ to enable SPS state display at MiCOM
C264 Computer local HMI level.
C264/EN AP/B30 Application

Page 128/396 MiCOM C264/C264C

(1)

(2)

(3)

(4)
(5)

(6)
(7)

FIGURE 136 : SETTING GENERAL ATTRIBUTES TO SPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
5.1.3 Defining DPS datapoint
5.1.3.1 Overview of DPS processing
At MiCOM C264 Computer level, the processing of a DPS can be represented by the
following data flow :

System Inputs

IED inputs

Toggle filtering
For closed contact
(DI acquisition)

DI/DO association
Toggle filtering
For open contact
(DI acquisition) Group
processing

Manual suppression Motion filtering

Substitution Persistance filtering

Transmission–
Report based
Forcing

To RCP
To HMI (views, lists)
To Data Logging
To archive

Transmission–
GOOSE based

To automation
C0134ENb

FIGURE 137 : DPS PROCESSING

5.1.3.2 Definition of DPS states
Basically, a DPS is acquired on two digital input channels of a DIU board: one for the open
contact and one for closed contact. And so it has got four fundamental steady states:

• OPEN when only OPEN channel is set,

Application C264/EN AP/B30

MiCOM C264/C264C Page 129/396

• CLOSED when only CLOSE channel is set,

• JAMMED when none channel is set,

• UNDEFINED when both channels are set.

Two extra transient states can be defined:

• MOTION00 when going from OPEN to CLOSED state or vice-versa, with none set
channel

• MOTION11 when going from OPEN to CLOSED state or vice-versa, with both set
channels
By combination with binary input processing done at MiCOM C264 Computer level (see
chapter 5.1.1 Overview of binary input processing), the DPS resulting states are :

• JAMMED

• OPEN

• CLOSE

• UNDEFINED

• TOGGLING

• SELFCHECK FAULTY

• UNKNOWN

• SUPPRESSED

• FORCED JAMMED

• FORCED OPEN

• FORCED CLOSED

• SUBSTITUTED JAMMED

• SUBSTITUTED OPEN

• SUBSTITUTED CLOSED
C264/EN AP/B30 Application

Page 130/396 MiCOM C264/C264C

5.1.3.3 Definition of DPS motion filtering

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

• T00 : delay for the MOTION00 state filtering

• T11 : delay for the MOTION11 state filtering

Both delays are in the range 0 to 120 s by step of 100 ms. A value of 0 means that no filter is
applied.
The time tag is user-selectable :

• Mode 1 : the valid state (OPEN or CLOSE) is stamped with the time of the beginning
of the MOTION state

• Mode 2 : the valid state (OPEN or CLOSE) is stamped with the time of this valid
transition
This time stamping can be superseded if a persistence filtering apply (see chapter 5.1.3.4
Definition of DPS persistence filtering).
If the MOTION state is confirmed, it is always stamped with the time of the beginning of the
MOTION state. Furthermore, the BI takes the state JAMMED (in case of confirmed
MOTION00 state) or UNDEFINED (in case of confirmed MOTION11 state). In this case, the
following valid state (OPEN or CLOSE) is always time-stamped with the time of this valid
transition (depending of the persistence-filtering feature).

OPEN

T00 T00 T11 T11

CLOSE

t0 t1 t2 t3 t4 t5 t6 t7 t8

• t0 : MOTION00 transition
• t1 : MOTION00 state not confirmed, CLOSE state time-stamped t0 if mode 1, t1 if mode 2 (if no
persistence filtering applies)
• t2 : MOTION00 transition
• t3 : MOTION00 state confirmed, state JAMMED time-stamped t2
• t4 : OPEN transition, time-stamped t4 whatever was the mode (if no persistence filtering applies)
• t5 : MOTION11 transition
• t6 : MOTION11 state not confirmed
• t7 : MOTION11 transition

C0188ENa

FIGURE 138 : DPS MOTION FILTERING

Application C264/EN AP/B30

MiCOM C264/C264C Page 131/396

5.1.3.4 Definition of DPS persistence filtering

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

• TC : delay for the CLOSE state confirmation

• TO : delay for the OPEN state confirmation

Both delays are in the range 0 to 120 s by step of 100 ms. A value of 0 means that no filter is
applied.
The time tag is user-selectable :

• Mode 1 : the status is stamped with the time of the transition

• Mode 2 : the status is stamped at the end of the delay.

NOTE : if a persistence filtering is applied, the OPEN or CLOSE state cannot
be time-stamped from the beginning of non-complementarity (i.e.
mode 1 of motion filtering cannot apply, see chapter 5.1.3.3 Definition
of DPS motion filtering).

TO TO

OPEN

TC TC

CLOSE

t0 t1 t2 3t t4 t5 t6 t7

· t0 : CLOSE transition
· t1 : CLOSE state not confirmed
· t2 : CLOSE transition
· t3 : CLOSE state confirmed (stamped t2 if mode 1, stamped t 3 if mode 2)
· t4 : OPEN transition
· t5 : OPEN state not confirmed
· t6 : OPEN transition
· t7 : OPEN state confirmed (stamped t 6 if mode 1, stamped t 7 if mode 2)

C0189ENa

FIGURE 139 : DPS PERSISTENCE FILTERING

C264/EN AP/B30 Application

Page 132/396 MiCOM C264/C264C

5.1.3.5 Creating DPS datapoint

To create DPS datapoint:

• Add a DPS from object entry available at the wished system or electrical object level
(1). Depending of the object level, different pre-defined kinds of DPS exist. They are
used for specific needs at electrical topology level (for details see relevant sub-chapter
in 6 DEFINING MICOM C264 COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see chapter 4.10 Setting
system information for MiCOM C264 Computer components).

• Update the DPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPS.

• Update its relation ‘has for profile’ to point to a specific existing profile (2). See chapter
5.2 Linking datapoint to profile, for details about profile definition and setting.

(1)

FIGURE 140: ADDING A DPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPS)

(2)

FIGURE 141: LINKING DPS DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPS)
Application C264/EN AP/B30

MiCOM C264/C264C Page 133/396

Updating DPS attributes (description for generic DPS)

When adding a generic DPS datapoint, some general attributes must be updated:
1. Short and long names of the datapoint used for logging, alarms ...
2. Detection mode : Permanent or Transient
3. Time reference for stable state: at start of filtering or end of filtering
4. T00 : motion delay for ‘jammed’ (00) state (0 to 60 s by 100 ms)
5. T11 : motion delay for ‘undefined’ (11) state (0 to 60 s by 100 ms)
6. TO : confirmation delay for stable ‘open’ state (0 to 120 s by 100 ms)
7. TC : confirmation delay for stable ‘closed’ state (0 to 120 s by 100 ms)
8. Forcing management:
when a DPS goes in invalid state, MiCOM C264 Computer can force or not its status
to set or reset state automatically. This attribute defines the way this forcing
management is done (Not automatic, automatic to open state, automatic to closed
state).
Automatic forcing management is independent of FSS facility gives at user by the
DPS profile.
9. State panel assignment (Yes/No): set to ‘yes’ to enable DPS state display at MiCOM
C264 Computer local HMI level.

(1)

(2)

(3)

(4)

(5)
(6)

(7)
(8)

(9)

FIGURE 142 : SETTING GENERAL ATTRIBUTES TO DPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPS)
C264/EN AP/B30 Application

Page 134/396 MiCOM C264/C264C

5.1.4 Defining MPS datapoint

5.1.4.1 Overview of MPS processing
At MiCOM C264 Computer level, the processing of a MPS can be represented by the
following data flow :

Toggle filtering
For contact 1
(DI acquisition)
Manual suppression

Toggle filtering Substitution

For contact n Transmission–
MPS filtering
(DI acquisition) Forcing Report based

System Inputs

To RCP
To HMI (views, lists)
To Data Logging
To archive
To automation
C0135ENb

FIGURE 143 : MPS PROCESSING

5.1.4.2 Definition of MPS states
A MPS is derived from N Digital Inputs : it could also be called “1 among N” BI. It is used as
a status where N is up to 16.
Basically, a MPS is acquired on N digital input channels of a DIU board: one contact for each
specific state. And so it has got up the fundamental steady states:

• STATE<i> when only <i> channel is set,

• UNDEFINED when none channel is set, or more than one is set.

By combination with binary input processing done at MiCOM C264 Computer level (see
chapter 5.1.1 Overview of binary input processing), the MPS resulting states are :

• STATE1 to STATE32

• UNDEFINED

• TOGGLING

• SELFCHECK FAULTY

• UNKNOWN

• SUPPRESSED

• FORCED STATE1 to FORCED STATE32

• SUBSTITUTED STATE1 to SUBSTITUTED STATE32

Application C264/EN AP/B30

MiCOM C264/C264C Page 135/396

5.1.4.3 Definition of MPS filtering

MPS is not being considered in the UNDEFINED state if the position has changed by more
than one step.
MPS is UNDEFINED after a user selectable time filtering (from 0 to 10 seconds, step 10 ms)
when no DI is in the SET state (all RESET) or if more than one are in the SET state :

Time-out Time-out

undefined
MP before
filtering
valid

undefined
MP after
filtering valid

C0253ENa

FIGURE 144 : MPS FILTERING

The MPS is time-tagged with the date of the last BI change.
5.1.4.4 Definition of MPS inhibition filtering
For some MPS, reading on its DI channels can be inhibit by the presence of a read inhibit
signal wired on an other DI channel. In that case, the previous selectable filtering is replaced
by a inhibition delay (from 0 to 10 seconds, step 10 ms): If read inhibit signal is not reset
within this delay, MPS becomes UNDEFINED.
5.1.4.5 Creating MPS datapoint
To create MPS datapoint:

• Add a MPS from object entry available at the wished system or electrical object level
(1). Depending of the object level, different pre-defined kinds of DPS exist. They are
used for specific needs at electrical topology level (for details see relevant sub-chapter
in 6 DEFINING MICOM C264 COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see chapter 4.10 Setting
system information for MiCOM C264 Computer components).

• Update the MPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of MPS.

• Update its relation ‘has for profile’ to point to a specific existing profile (2). See chapter
5.2 Linking datapoint to profile, for details about profile definition and setting.
C264/EN AP/B30 Application

Page 136/396 MiCOM C264/C264C

(1)

FIGURE 145: ADDING A MPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)

(2)

FIGURE 146: LINKING MPS DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
Updating MPS attributes (description for generic MPS)
When adding a generic DPS datapoint, some general attributes must be updated:
1. Short and long names of the datapoint used for logging, alarms ...
2. Filtering delay (0 to 10 s by 10 ms): see chapter 5.1.4.3
3. Inhibition delay (0 to 10 s by 10 ms) : see chapter 5.1.4.4
4. Forcing management:
when a MPS goes in invalid state, MiCOM C264 Computer can force or not its status
to set or reset state automatically. This attribute defines the way this forcing
management is done (Not automatic, automatic to state <i>).
Automatic forcing management is independent of FSS facility gives at user by the
MPS profile.
5. State panel assignment (Yes/No): set to ‘yes’ to enable MPS state display at MiCOM
C264 Computer local HMI level.
Application C264/EN AP/B30

MiCOM C264/C264C Page 137/396

(1)

(2)

(3)

(4)

(5)

FIGURE 147 : SETTING GENERAL ATTRIBUTES TO MPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
5.1.5 Overview of measurement processing
This chapter is an introduction to Measurement Value (MV) datapoint definition. It deals with
general processing and features associated to these kinds of datapoints, for better
comprehension of their configuration.
MV are mainly acquired via (for details see chapter 5.6 Defining acquisition source for input
datapoints):

• An analogue input channel (AIU board); it is called ‘analogue measurement’

• Digital input channels (DIU board); it is called ‘digital measurement’

• IEDs connected by a serial link

• Deduction from CT/VT input acquisition

At MiCOM C264 Computer level, the general processing of a measurement is represented
by the following data flow :

From IED
acquisition
Manual
suppression
Open Circuit Scaling Thresholds
From analogue
Management detection Substitution
acquisition

Forcing
From digital
acquisition

Transmission
CT/VT
From CT/VT
Calculations
acquisition

To RCP
To HMI
To Printer
To archive
To automation
C0136ENa

FIGURE 148 : MEASUREMENT PROCESSING

5.1.5.1 Open Circuit Management
For 4-20 mA transducers (useable for analogue MV), a special feature is implemented to
avoid fleeting values around 4 mA :
C264/EN AP/B30 Application

Page 138/396 MiCOM C264/C264C

• in the range [0 .. 3 mA[, the measurement value is set to 0 and the status is set to
OPEN CIRCUIT

• in the range [3 .. 4 mA], the analogue input is considered to be equal to 0 mA.

5.1.5.2 Features of digital measurement acquisition
A digital measurement (DM) is a digital value coded on N wired inputs. Each wired input
represents a bit of the value, and can take only one among two values: low or high.
These Digital measurements are used to process measures and tap indications.
The digital measurements are acquired on the same boards as the digital inputs. The Digital
Inputs processing described above apply on Digital Measurements, except the toggle
filtering.
A Digital Measurement can be associated to a Read Inhibit (RI) signal. The acquisition
process is different depending of the presence of this signal.
Acquisition without RI
The DM is calculated at each change of state of one of its bits.
A stability processing is applied at each calculation to confirm the value :

• if the difference between the current value and the previous confirmed value is less or
equal than Vstab (value defined in configuration), then the current value is confirmed

• if the difference is greater than Vstab, then the Tstab delay is launched (value defined in
configuration, from 0 to 60s, with a 10 ms step). If a Tstab delay is already launched, this
one is cancelled. At the end of the delay, the DM value is confirmed.

Confirmed Confirmed Confirmed

DM value DM value DM value

Tstab
Tstab

Bit change => new Bit change => Bit change =>
calculation new calculation new calculation
∆≤V stab=> confirmed ∆>V stab => Tstab ∆>V stab => Tstab
DM value launched re-launched

Note : ∆= |confirmed DM value – new calculation|

C0130ENa

FIGURE 149 : CONFIRMATION OF DIGITAL MEASUREMENT VALUE (WITHOUT RI SIGNAL)

Furthermore, an invalidity processing is applied : at the first change of state of one bit
following a confirmed DM value, the TInv delay is launched (value defined in configuration,
from 0 to 300s, with a 10 ms step). If the value is not confirmed at the end of this delay, the
DM is declared UNDEFINED.
Application C264/EN AP/B30

MiCOM C264/C264C Page 139/396

TInv

Confirmed
DM value DM UNDEFINED
Tstab
Tstab
Tstab

Bit change => Bit change => Bit change =>

new calculation new calculation new calculation
∆>V stab => Tstab ∆>V stab => Tstab ∆>V stab => Tstab
launched re-launched re-launched
C0131ENa

FIGURE 150 : DIGITAL MEASUREMENT VALUE BECOMING UNDEFINED (WITHOUT RI SIGNAL)

If Vstab is equal to 0, there is no stability processing : all DM values are sent at each
calculation.
Acquisition with RI
When the RI signal changes to set state, the Tinh delay is launched. If the signal is always set
at the end of the delay, the DM is declared UNDEFINED. Otherwise, if the RI signal changes
to reset state before the end of the delay, the current DM value is transmitted.

Tinh Tinh

RI

DM value transmitted DM UNDEFINED

C0132ENa

FIGURE 151 : DIGITAL MEASUREMENT VALUE BECOMING UNDEFINED (WITH RI SIGNAL)

If the RI signal is invalid, the DM will be invalid.
C264/EN AP/B30 Application

Page 140/396 MiCOM C264/C264C

Digital Measurement encoding

The following code are allowed for DM :

Code Number of bits Range of value

BCD 4 (1 BCD decade) 0 to 9
8 (2 BCD decades) 0 to 99
12 (3 BCD decades) 0 to 999
16 (4 BCD decades) 0 to 9999
Binary 4 0 to 15
7 0 to 127
8 0 to 255
12 0 to 4095
16 0 to 65535
Gray (see following table) 8 0 to 255
16 0 to 65535
Decimal 16 (1 bit among 6 for the tens, 0 to 69
1 among 10 for the unit)
1 among N 2 0 to 2
to 32 to 0 to 32

One supplementary bit can be used for the sign (0 indicates a positive value, 1 indicates a
negative value)
The table below gives the Gray code implementation on 4 bits. Same principles are applied
for 8 and 16 bit values.

b4 b3 b2 b1 b0 Value
0 0 0 0 0 0
0 0 0 0 1 1
0 0 0 1 1 2
0 0 0 1 0 3
0 0 1 1 0 4
0 0 1 1 1 5
0 0 1 0 1 6
0 0 1 0 0 7
0 1 1 0 0 8
0 1 1 0 1 9
0 1 1 1 1 10
0 1 1 1 0 11
0 1 0 1 0 12
0 1 0 1 1 13
0 1 0 0 1 14
0 1 0 0 0 15
1 1 0 0 0 16
1 1 0 0 1 17
1 1 0 1 1 18
1 1 0 1 0 19
1 1 1 1 0 20
1 1 1 1 1 21
1 1 1 0 1 22
1 1 1 0 0 23
Application C264/EN AP/B30

MiCOM C264/C264C Page 141/396

Invalidity
Depending on the type of encoding, some combinations of the input bits are excluded,
otherwise, the DM is considered undefined :

• BCD : each quartet must be less than or equal to 9.

• 1 among N : one and only one bit must be asserted.

• Decimal : only one bit of units must be set; only one bit of tens can be set
Time tagging
The provided value of a DM is time stamped with the date/time of the last digital input that
has changed the DM value.
5.1.5.3 Analogue measurement acquisition
Analogue measurement are acquired via input analogue channel (AI) of AIU board. These
AI are voltage or current DC signals (only current for AIU210 board) delivered by
transducers, and representing an external value.
Input characteristics
Input range

• For voltage inputs :

± 10 V
±5V
± 2.5 V
± 1.25 V
• For current inputs :

0 - 1 mA
± 1 mA
0 - 5 mA
± 5 mA
0 - 10 mA
± 10 mA
4 - 20 mA
0 - 20 mA
± 20 mA
Each channel on a board can be assigned one of these ranges (voltage or current)
independently of the others channels (see chapter 4.4.5 Configuring an AI channel).
Each AI should be able to convert the nominal range +20%, this feature being configurable.
The same accuracy must be achieved over the whole range : nominal+20%.
For the 4-20 mA range, the value provided by the analogue board is 0-16 mA
Overall accuracy
The accuracy of the complete acquisition chain is 0.1 % of the full scale for each range at a
reference temperature of 25 °C.
The error due to a shift from the reference temperature is 30 ppm/°C between
–10°C and +55°C.
Rejection ratios
CMMR : The common mode rejection ratio of the 50 / 60 Hz is greater than
100 dB.
SMRR : The serial mode rejection ratio of the 50/60 Hz is greater than 40 dB.
C264/EN AP/B30 Application

Page 142/396 MiCOM C264/C264C

Overload condition
The saturation value, for each range, is the following :

Range Saturation values

± 10 V -12.6 V / +12.6 V
±5V -6.3 V / +6.3 V
± 2.5 V -3.2 V / +3.2 V
± 1.25 V -1.26 V / +1.26 V
0 - 1 mA 1.26 mA
± 1 mA -1.26 mA / +1.26 mA
0 – 5 mA 6.3 mA
± 5 mA -6.3 mA / +6.3 mA
0 – 10 mA 12.5 mA
± 10 mA -12.5 mA / +12.5 mA
0 – 20 mA 25 mA
± 20 mA -25 mA / +25 mA
4-20 mA 26 mA

Acquisition
Acquisition cycle
The analogue inputs are acquired on a periodical basis. Each channel on a board can be
assigned one of these cycles independently of the others channels (see chapter 4.4.5
Configuring an AI channel).
It exist two acquisition cycles :

− a short cycle (Nsc x 100ms, Nsc configurable from 1 to 10 with a default value of 1).

− a long cycle (Nlc x 500ms, Nlc configurable from 1 to 20, with a default value of 2)
AD conversion
The Analogue to Digital Converter has a 16 bits resolution (15 bits + sign bit).
The zero offset value is computed by the conversion of a 0 V voltage reference.
The gain is adjusted automatically by software by connecting a known voltage reference to
the amplifier.
The zero offset values and the gain are adjusted regularly in order to compensate for the
deviations caused by variations of temperature and ageing.
Self-checks
Two self-checks are performed :

• the board address coherency

• the complementarity control of the measured value

These self-checks are performed at each scan (defined during the configuration phase).
Time tagging
An AI is time stamped with the date/time of the scanned value.
Application C264/EN AP/B30

MiCOM C264/C264C Page 143/396

5.1.5.4 Scaling
A linear or a quadratic transformation can compute the real value represented by the
measurement :

• Linear, single slope

Value = A*X + B

• Linear, multisegments
Value = Ai*X + Bi with Xi-1≤X<Xi .
Up to 20 configurable segments [Xi-1 .. Xi] (1≤ i ≤ 20)

• Quadratic
Value = A X + B or
Value = AX+B
Transformation law and A / B coefficients are defined in configuration.
5.1.5.5 Thresholds detection
Six thresholds can be defined for each measurement : 3 upper and 3 lower thresholds.
A hysteresis value configured on a per measurement basis is associated to the threshold
management.

upper
HYST

t3 t4

t1 t2

HYST
lower

t1 : upper threshold violation

t2 : end of upper threshold violation
t3 : lower threshold violation
t4 : end of lower threshold violation
C0190ENa

FIGURE 152 : THRESHOLDS DETECTION

5.1.5.6 Manual suppression
A measurement can be suppressed by an order issued from an operator. No subsequent
change of value or state on a suppressed measurement can trigger any action e.g. display,
alarm, transmission. The measurement takes the “SUPPRESSED” state. When the operator
unsuppresses the measurement, this one takes its actual state.
5.1.5.7 Substitution
The value of a measurement can be substitute by an operator (state “SUBSTITUTED”, value
defined by the operator). The measurement stays in this state until he unsubstitutes it.
When a measurement is substituted, no changes of value or state are transmitted, and
computations are made with the substituted state. When the measurement is unsubstituted,
the actual state and value are transmitted to higher control levels and subsequent changes
of state and value are transmitted again.
C264/EN AP/B30 Application

Page 144/396 MiCOM C264/C264C

5.1.5.8 Forcing of invalid measurement

When a measurement is invalid (i.e. SELFCHECK FAULTY, UNDEFINED, OPEN CIRCUIT,
SATURATED or UNKNOWN), it can be manually forced by a user (state “FORCED”, value
defined by the operator). This feature is similar to the substitution but the information is
automatically updated when valid information is available again.
The forcing could also be automatic : in this case, the invalid information takes automatically
the FORCED state and the value defined in configuration.
5.1.5.9 Definition of MV states
The state of a measurement can be :

State Comment
VALID Not in one of the below states
SELFCHECK FAULTY Due to an AI board fault or a DI board fault for a digital
measurement
SUBSTITUTED See chapter5.1.5.7 Substitution
FORCED See chapter 5.1.5.8 Forcing of invalid measurement
SUPPRESSED See chapter 5.1.5.6 Manual suppression
UNKNOWN If the measurement is acquired via a transmission link, the
measurement is unknown when the link is disconnected.
SATURATED The measurement is saturated if it is beyond its nominal input
range.
Only available for analogue MV acquired on AIU board.
UNDEFINED Due to a wrong encoding, only for digital measurement.
Due to a scaling error, in calculation of quadratic law (negative X
value for example)
OPEN CIRCUIT See chapter 5.1.5.1 Open Circuit Management
OVERSHOOT[1..3] It exists 3 “Overshoot” states, one for each upper threshold
violation. Only one could be set at one time (see chapter 5.1.5.5
Thresholds detection)
UNDERSHOOT[1..3] It exists 3 “Undershoot” states, one for each lower threshold
violation. Only one could be set at one time (see chapter 5.1.5.5
Thresholds detection)
Application C264/EN AP/B30

MiCOM C264/C264C Page 145/396

5.1.5.10 Transmission
The measurements are transmitted on a client-server basis on the UCA2 network., using the
report mechanism. Refer to chapter 4.5 Networking MiCOM C264 Computer on the station-
bus network for more information on UCA2.
During a loss of communication between a client and a server, all server measurements are
set to UNKNOWN on the client.
The measurement information transmitted in a report are :

• the real value (i.e. after scaling)

• the resulting state (mapped on the quality field on UCA2)

• the time stamping (in GMT time) and time quality

• the reason for change, which could be one of the below values :

− change of quality (set if the measurement resulting state has changed)

− cyclic change (set if the measurement value has changed, without modification of
the resulting state)
All states changes (refer 5.1.5.9 Definition of MV states) are always transmitted. A
measurement value can be transmitted periodically or upon variation.
Periodic transmission
Two periods are defined in database, on a per MiCOM MiCOM C264 Computer basis (see
chapter 4.3.2 Configuring measurement acquisition and transmission):

• a short period, from 0 to 60 seconds (step 0,1 second)

• a long period, from 0 to 60 seconds (step 0,5 second)

(0 means there is no period).
Each measurement is associated to one of the two periods. All measurements of one period
are transmitted at the beginning of each cycle.
All measurements values transmitted within one transmission cycle are the latest acquired
values.
Transmission upon variation
Measurements can be transmitted upon variation : a value is sent if the acquired value
(Vacq) is different from more than a specified amount from the previously transmitted value
(Vt).

The minimal variation ∆V is computed from the last transmitted value (mode 1) or from the
full-scale value (mode 2) :

• ∆V = p % * |Vt|
Where p is a value in the range 0 .. 100 and Vt is the last transmitted value.
or

• ∆V = p % * |Vmax|
Where p is a value in the range 0 .. 100 and Vmax is the full scale value.

A new transmission occurs if |Vacq-Vt| > ∆V .

C264/EN AP/B30 Application

Page 146/396 MiCOM C264/C264C

Transmission upon trigger

One or more measurements can be associated to a single or double BI “trigger”. When the
BI goes to the state SET / CLOSED (or FORCED SET, SUBSTITUTED SET, FORCED
CLOSED / SUBSTITUTED CLOSED) all associated measurements are transmitted
immediately. The same behaviour if the BI is in this state at the initialisation of the MiCOM
C264 Computer. As much the BI is in this state the associated measurements are
transmitted after change of state (refer 5.1.5.9 Definition of MV states) or according to the
configuration( periodically, upon variation , threshold variation)
5.1.6 Defining MV datapoint
5.1.6.1 Adding a MV datapoint
To create MV datapoint:

• Add a MV from object entry available at the wished system or electrical object level
(1). Depending of the object level, different pre-defined kinds of MV exist. They are
used for specific needs at electrical topology level (for details see relevant sub-chapter
in 6 DEFINING MICOM C264 COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see chapter 4.10 Setting
system information for MiCOM C264 Computer components).

• Update the MV attributes (see following chapters); some attributes can be fixed or
masked depending on the pre-defined kind of MV.

• Update its relation ‘has for profile’ to point to a specific existing profile (2). See chapter
5.2 Linking datapoint to profile, for details about profile definition and setting.

(1)

FIGURE 153: ADDING A MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
Application C264/EN AP/B30

MiCOM C264/C264C Page 147/396

(2)

FIGURE 154: LINKING MV DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
5.1.6.2 Setting ‘General’ attributes of MV datapoint
When adding a generic MV datapoint, some general attributes must be updated:
1. Short and long names of the datapoint used for logging, alarms ...
2. MV type:
Available values are:

− Analogue (used for analogue acquisition, IED acquisition, CT/VT calculation or

system input)

− Digital coded ‘BCD’ (only used for digital acquisition)

− Digital coded ‘pure binary’ (only used for digital acquisition)

− Digital coded ‘gray’ (only used for digital acquisition)

− Digital coded ‘1 among n’ (only used for digital acquisition)

− Digital coded ‘decimal’ (only used for digital acquisition)

For details about digital encoding see chapter 5.1.5.2 Features of digital measurement
acquisition
3. Automatic forcing management (Yes/No):
when a MV goes in invalid state, MiCOM C264 Computer can force or not its value
automatically. Automatic forcing management is independent of FSS facility gives at
user by the MV profile.
4. MV value when automatic forcing
5. Transmission cycle: see chapter 5.1.5.10 Transmission for details
Available values are:

− Short cycle

− Long cycle

− According to a % of full scale value

− According to a % of current value

6. Deadband for transmission cycle set to ‘according to a % of ...’
This attribute corresponds to ‘p’ parameter described in chapter 5.1.5.10 Transmission
7. MV panel assignment (Yes/No): set to ‘yes’ to enable MV value display at MiCOM
C264 Computer local HMI level.
C264/EN AP/B30 Application

Page 148/396 MiCOM C264/C264C

(1)
(2)

(3)
(4)

(5)
(6)

obsolete

(7)

FIGURE 155 : SETTING GENERAL ATTRIBUTES TO MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
5.1.6.3 Setting ‘Value features’ attributes of MV datapoint
When adding a generic MV datapoint, some ‘Value features’ attributes must be updated:
1. Real minimal value (used for full scale calculation and scaling)
2. Real maximal value (used for full scale calculation and scaling)
3. hysteresis used for threshold detection (see chapter 5.1.5.5 Thresholds detection for
details)
For each available threshold (see chapter 5.1.5.5 Thresholds detection for details):
4. threshold usage (Yes/No)
5. threshold value

(1)

(2)

(3)
(4)
(5)

FIGURE 156 : SETTING VALUE FEATURES ATTRIBUTES TO MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
Application C264/EN AP/B30

MiCOM C264/C264C Page 149/396

5.1.6.4 Setting ‘Scaling’ attributes of MV datapoint

When adding a generic MV datapoint, some ‘Scaling’ attributes must be updated:
1. Scaling rule
Available values are (see chapter 5.1.5.4 Scaling):

− Linear

− Quadratic

− Quadratic with offset

− Linear per pieces

2. Minimum acquisition value (used for scaling)
3. Maximum acquisition value (used for scaling)
In case of multi-segment scaling
4. Upper bound of segment [Xi-1 .. Xi]
5. Ai coefficient
6. Bi coefficient

(1)

(2)

(3)

(4)
(5)
(6)

FIGURE 157 : SETTING SCALING ATTRIBUTES TO MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
C264/EN AP/B30 Application

Page 150/396 MiCOM C264/C264C

5.1.6.5 Setting ‘Digital acquisition’ attributes of MV datapoint

When adding a generic digital MV datapoint, some ‘Digital acquisition’ attributes must be
updated.
Refer to chapter 5.1.5.2 Features of digital measurement acquisition for attribute meaning.
1. Inhibition delay (x 10 ms): Tinh (used for digital measurement with read inhibit signal)
2. Stabilisation delay (x 10 ms): Tstab
3. Stabilisation value: Vstab
4. Validation delay (x 10 ms): TInv

(1)
(2)

(3)
(4)

FIGURE 158 : SETTING DIGITAL ACQUISITION ATTRIBUTES TO MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
Configuration rules and checks

• If the attribute "type" of the "MV" Datapoint is set to a "Digital…" value, then the
following constraint between the two attributes must be respected :
- "validation delay" ≥ 5 ∗ "stabilization delay"
5.1.7 Defining TPI datapoint
5.1.7.1 Overview of Tap Position Indicator processing
Tap Position Indicator (TPI) must be seen as MV with specific features:

• Its value is an integer in the range [1..64],

• Acquisition can be done via AI channel of AIU board:

The tap position is acquired by measuring a current input.

A minimum value Imin (mA) corresponds to the lowest position 1 of the tap , and a
maximum value Imax corresponds to the highest value N.

The input current should take only discrete values : Ik =Imin + (K -1)(Imax_Imin)/(N-1)
, with K the position of the tap.

However the tap is considered in the position K if the current is in the range [Ik-∆I/2 ..
Ik+∆I/2], with ∆I = N% of (Imax – Imin). The N percentage is defined in configuration.

The tap position is considered UNDEFINED outside of this range.

• Acquisition can be done on digital channels of DIU board (up to 64 DI channels):

In that case, available digital MV type are: Decimal, Gray, BCD or ‘1 among n’

• Manual suppression:
A TPI can be suppressed by an order issued from an operator. No subsequent change
of value or state on a suppressed TPI can trigger any action e.g. display, alarm,
transmission. The TPI takes the “SUPPRESSED” state. When the operator
unsuppresses the TPI, this one takes its actual state.
Application C264/EN AP/B30

MiCOM C264/C264C Page 151/396

• Substitution
The value of a TPI can be substitute by an operator (state “SUBSTITUTED”, value
defined by the operator). The TPI stays in this state until he unsubstitutes it.

When a TPI is substituted, no changes of value nor state are transmitted, and
computations, for instance groupings, are made with the substituted state. When the
TPI is unsubstituted, the actual state and value are transmitted to higher control levels
and subsequent changes of state and value are transmitted again.

• Forcing of invalid TPI

When a TPI is invalid (i.e. SELFCHECK FAULTY, UNDEFINED or UNKNOWN), it can
be manually forced by a user (state “FORCED”, value defined by the operator). This
feature is similar to the substitution but the information is automatically updated when
valid information is available again.

The automatic forcing function is not provided for TPI.

• TPI resulting states

The state of a tap position can be :

State Comment
VALID Not in one of the below states
SELFCHECK FAULTY Due to an AI board fault or a DI board fault
SUBSTITUTED See previously
FORCED See previously
SUPPRESSED See previously
UNKNOWN If the tap position is acquired via a transmission link, the
information is unknown when the link is disconnected.
UNDEFINED Due to a wrong encoding for a digital acquisition, or a saturation,
an open-circuit or an out-of-range value for an analogue
acquisition
OVERSHOOT[1..3] It exists 3 “Overshoot” states, one for each upper threshold
violation. Only one could be set at one time
UNDERSHOOT[1..3] It exists 3 “Undershoot” states, one for each lower threshold
violation. Only one could be set at one time

NOTE : TPI threshold is managed as for measurement

C264/EN AP/B30 Application

Page 152/396 MiCOM C264/C264C

5.1.7.2 Adding a TPI datapoint

TPI datapoint is automatically created when adding a tap changer built-in function under a
mandatory transformer module of a transformer bay. For details about transformer bay,
module or tap changer function creation see chapter 6 DEFINING MICOM C264
COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE.
Once a TPI has been created by adding a tap changer built-in function (1):

• Update the TPI attributes (see following chapters).

• Update its relation ‘has for profile’ to point to a specific existing MV profile (2). See
chapter 5.2 Linking datapoint to profile, for details about profile definition and setting.

Bay ‘Transformer’

Mandatory ‘Transformer’ module

(1) Tap changer built-in function

Mandatory TPI
C0191ENa

FIGURE 159: AUTOMATIC TPI CREATION FOR TAP-CHANGER BUILT-IN FUNCTION

(2)

FIGURE 160: LINKING TPI DATAPOINT TO ITS PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 153/396

5.1.7.3 Setting ‘General’ attributes of TPI datapoint

For a TPI datapoint, some general attributes similar to MV ones, must be updated:
1. Short and long names of the datapoint used for logging, alarms ...
2. TPI type:
Available values are:

− Analog (used for analog acquisition)

− Digital coded ‘BCD’ (only used for digital acquisition)

− Digital coded ‘gray’ (only used for digital acquisition)

− Digital coded ‘1 among n’ (only used for digital acquisition)

− Digital coded ‘decimal’ (only used for digital acquisition)

For details about digital encoding see chapter 5.6.1.4 Wiring MV and TPI datapoint
3. MV panel assignment (Yes/No): set to ‘yes’ to enable MV value display at MiCOM
C264 Computer local HMI level.

(1)

(2)

obsolete

(3)
C0192ENa

FIGURE 161 : SETTING GENERAL ATTRIBUTES TO TPI DATAPOINT

5.1.7.4 Setting ‘Value features’ attributes of TPI datapoint
Refer to 5.1.6.3 Setting ‘Value features’ attributes of MV datapoint
Configuration rules and checks

• The following constraint between the two attributes must be respected :

("maximum value" − "minimum value" + 1) ∈ [1..64]
C264/EN AP/B30 Application

Page 154/396 MiCOM C264/C264C

5.1.7.5 Setting ‘Tap position’ attributes of TPI datapoint

For a TPI datapoint, some specific attributes must be updated:
1. Filtering delay:

− for digital TPI, corresponds to Tstab of digital measurement

Refer to chapter 5.1.5.2 Features of digital measurement acquisition for attribute
meaning

− for analog TPI, corresponds to a delay to filter transient UNDEFINED state (delay
to confirm UNDEFINED state)
2. Inhibition delay:
only used for digital TPI with read inhibit signal
corresponds to Tinh of digital measurement
Refer to chapter 5.1.5.2 Features of digital measurement acquisition for attribute
meaning
3. Current valid range:
only used for analogue TPI
corresponds to N parameter described in chapter 5.1.7.1 Overview of Tap Position
Indicator processing

(1)
(2)

(3)

FIGURE 162 : SETTING TAP POSITION ATTRIBUTES TO TPI DATAPOINT

5.1.7.6 Setting ‘Scaling’ attributes of TPI datapoint
For an analogue TPI datapoint, some ‘Scaling’ attributes appears and must be updated:
1. Minimum acquisition value:
corresponds to Imin parameter described in chapter 5.1.7.1 Overview of Tap Position
Indicator processing
2. Maximum acquisition value:
corresponds to Imax parameter described in chapter 5.1.7.1 Overview of Tap Position
Indicator processing

(1)
(2)

FIGURE 163 : SETTING SCALING ATTRIBUTES TO TPI DATAPOINT

Application C264/EN AP/B30

MiCOM C264/C264C Page 155/396

5.1.8 Defining Counter datapoint

5.1.8.1 Overview of Counter processing
Some Digital Inputs are used to count the energy.
The accumulators are stored in non-volatile memory.
Acquisition
Single counter (SCT)
A SCT is acquired on a single contact.
The value of the accumulator is incremented after a low to high transition, confirmed after a
filtering time (Tcount). Tcount is defined on a counter per basis, with a step of 5 ms: the chosen
value must be coherent with the pulse frequency (i.e. all counters of a system use the same
Tcount).
A subsequent pulse can be taken into account only after a high to low transition.

Tcount Tcount

Transition validated,
Low to high transition
counter is incremented

Transition discarded
Low to high transition
C0128ENa

FIGURE 164 : SINGLE COUNTER ACQUISITION

Double counter (DCT)
A double counter is acquired on two contacts. One is called the true contact (TC), the other
is the complemented contact (CC). Normally these contacts should have complementary
states.
Pulses are detected in the same manner as for SCT, on the TC variations, using the Tcount
delay (the same Tcount value is used for SCT and DCT).
A subsequent pulse can be taken into account only after a high to low transition on TC (and
so a low to high transition on CC).
The difference is that both contacts should be in opposite states for transitions to be
detected and validated. The counter is invalid if it exists a non-complementarity between the
2 contacts during a delay Tdef. This delay is defined for the whole system (i.e. all DCT use the
same delay).
C264/EN AP/B30 Application

Page 156/396 MiCOM C264/C264C

Tcount Tcount Tdef

TC

CC

Low to high transition Low to high transition, but no

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

Low to high transition Non-complementarity

confirmed, counter is invalid
Transition validated,
counter is incremented Detection of non-complementarity
C0129ENa

FIGURE 165 : DOUBLE COUNTER ACQUISITION

Processing
Overview

Continuous register Scaling

From counters
acquisition
+
+1
Accumulator Transmission

= To RCP
To HMI
To archive
Periodic register Scaling To automation

in

24h - FIFO
C0195ENa

FIGURE 166 : COUNTER PROCESSING

• The accumulator is incremented at each valid counter pulse.

• The periodic register is used to store the accumulator value of the previous period.

• The continuous register is used to store the accumulator value since the origin.

• The FIFO memory is used to store the periodic register of each period (up to 16
counters), during 24h.
Application C264/EN AP/B30

MiCOM C264/C264C Page 157/396

Periodic processing
A period is defined either :

• By an external pulse on a digital input

• By the internal clock : the period length is settable : 10', 15', 30', 1h to 24h , each
period begins at a regular hour : 12:00 , 12:30 , 13:00 ...
This choice is defined during the configuration phase on a per MiCOM C264 Computer
basis. The period delimiter is also defined at configuration time for each counter.
At each period :

• The content of the accumulator is added to the continuous register

• The content of the accumulator is transferred to the periodic register

• The content of the periodic register is inserted into the FIFO queue

• The accumulator is reset to 0 ( a pending pulse is not lost )

• Either the continuous register or the periodic register is transmitted. The choice is
made by configuration on a per accumulator basis.
If the chosen transmitted register reaches its maximum value (232), the counter status is set
to OVERRANGE. Only a counter modification (see § 5.2.6) can re-validate the counter.
Scaling
Scaling is used for printing or displaying a counter. EPI is a parameter giving the amount of
energy in KW-h or KVAR-h equivalent to a pulse . The value displayed is :
N x EPI KW-h .
Where N is the value of a counter .
Counter resulting states
The state of a counter can be :

State Comment
VALID not in one of the below states
SELFCHECK FAULTY Due to the SELFCHECK FAULTY of the DI
UNKNOWN If the counter is acquired via a transmission link, the information
is unknown when the link is disconnected.
UNDEFINED Due to a counting failure of DCT (non-complementarity of the 2
contacts)
OVERRANGE when the maximum value is reached

Transmission
The counters are transmitted on a client-server basis on the UCA2 network using the report
mechanism.
During a loss of communication between a client and a server, all server counters are set to
UNKNOWN on the client.
The counter information transmitted in a report are :

• the number of pulses (i.e. accumulator value before scaling)

• the real value

• the time stamping (in GMT time) and time quality

• the resulting state (mapped on the quality field on UCA2)

C264/EN AP/B30 Application

Page 158/396 MiCOM C264/C264C

• the reason for change, which could be one of the below values :

− cyclic change (set if the value has changed)

− change of quality (set if the quality has changed)

− change due to control (set if the value or quality change is due to a control)
Counter modification
When an accumulator value is modified, the request is immediately taken into account. The
continuous register is set with the accumulator value.
The modification could be a reset of the counter.
5.1.8.2 Adding a Counter datapoint
To create Counter datapoint:

• Add a Counter from object entry available at the wished system or electrical object
level (1). Depending of the object level, different pre-defined kinds of MV exist. They
are used for specific needs at electrical topology level (for details see relevant sub-
chapter in 6 DEFINING MICOM C264 COMPUTER CONFIGURATION IN
ELECTRICAL ARCHITECTURE) or system topology level (for details see chapter
4.10 Setting system information for MiCOM C264 Computer components).

• Update the Counter attributes (see following chapters).

• Update its relation ‘has for profile’ to point to a specific existing profile (2). See chapter
5.2 Linking datapoint to profile, for details about profile definition and setting.

(1)

FIGURE 167: ADDING A COUNTER DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC COUNTER)

(2)

FIGURE 168: LINKING COUNTER DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC COUNTER)
5.1.8.3 Setting ‘General’ attributes of Counter datapoint
When adding a generic Counter datapoint, some general attributes must be updated:
Application C264/EN AP/B30

MiCOM C264/C264C Page 159/396

1. Short and long names of the datapoint used for logging, alarms ...
2. Validation duration:
corresponds to Tcount parameter described in chapter 5.1.8.1 Overview of Counter
processing
3. Invalidity duration:
corresponds to Tdef parameter described in chapter 5.1.8.1 Overview of Counter
processing
4. IED value already totalled (Yes/No): attribute must be set to Yes if counter value
acquired on IED must not be totalled periodically (total done at IED level)
5. Cumul period:
corresponds to period length of internal clock parameter described in chapter 5.1.8.1
Overview of Counter processing (periodic processing)
6. Reset at cumulative period (Yes/No): when set to ‘Yes’ that the way to transmit the
periodic register, if not the cumulative register is transmitted.
7. MV panel assignment (Yes/No): set to ‘yes’ to enable Counter value display at MiCOM
C264 Computer local HMI level.

(1)
(2)

(3)

(4)
(5)
(6)

obsolete

(7)

C0196ENa

FIGURE 169 : SETTING GENERAL ATTRIBUTES TO COUNTER DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC COUNTER)
C264/EN AP/B30 Application

Page 160/396 MiCOM C264/C264C

5.1.9 Overview of control sequence processing

This chapter is an introduction to SPC, DPC and SetPoint datapoint definition. It deals with
general control sequence and features associated to these kinds of datapoints, for better
comprehension of their configuration.
There are four types of Binary outputs :

• Single Point Status (SPC) : derived from one Digital output

• Double Point Status (DPC) : derived from two Digital outputs

• System output : control information related to the system, to configurable and built-in
automations or to electrical process but without acquisition possibilities

• Setpoint (SetPoint) : derived from n Digital outputs

SPC, DPC and SetPoints are mainly controlled via digital output boards (DOU board) or via
IEDs connected by a serial link (for details see chapter 5.6).
By extension, at SCE level, system outputs are seen as particular SPC or DPC depending
on the number of elementary information they represents (for details about system outputs,
see chapter 4.10 Setting system information for MiCOM C264 Computer components).
5.1.9.1 Device control mode and device type
By configuration a control may be executed to one of the following modes:

• “Select Before Operate once” mode (SBO once):

usually for circuits breakers and disconnect switches. The device must be select
before allow the execution. In that case the device is managed in two phases:
selection and execution. Device unselection is done automatically by the MiCOM
C264 Computer.

• “Select Before Operate many” mode (SBO many):

usually for transformers. The device must be selected before execute one or more
controls before reach the expected position (low/raise). In that case the device is
managed in three phases: selection, execution and unselection. The execution phase
is repeated for every new control. For ends the controls sequence, the initiator of the
request must sent an “unselection” request.

• “Direct Execute” mode:

usually for ancillary devices a control may be performed directly without need
selection.
Every control sequence may be different according the type of the device to control. The
complexity of the control sequence may be more or less important depending to the device:

• Synchronised or not synchronised Circuit breakers, disconnectors and earthling

switches :
They are managed in “Direct execute” mode or “SBO once” mode with optional
hardware selection of the device in SBO mode

• Transformers :
They are managed in the three modes: “Direct Execute”, “SBO once” and “SBO many”
mode with optional hardware selection of the device in SBO mode

• Ancillary devices :
They are usually managed in “Direct Execute” but can be managed also in “SBO
once” mode.

• System Controls:
System outputs are used to activate or inactivate automatic functions on the MiCOM
C264 Computer (e.g. Auto-recloser ON/OFF), change operating modes etc.

• Controls via Setpoints:

They are managed in “Direct Execute” and “SBO once” mode.
Application C264/EN AP/B30

MiCOM C264/C264C Page 161/396

5.1.9.2 Control’s sequence phase management

According to the configuration of the device control, a control sequence is performed in one,
two, or three phases. Each phase of control sequence (selection, execution and unselection)
may have a normal or abnormal termination and positive or negative acknowledgement is
sending to the UCA2 clients subscribed during the configuration process.
Negative acknowledgements, according the configuration, may generate spurious alarms.
Refer to 4.1 Setting general system configuration relevant to MiCOM C264 Computers for
the controls sequence acknowledgements.

• One phase - “Direct execute” mode

− Execution phase:
If the execution phase ends normally the MiCOM C264 Computer generates a
positive acknowledgement and the control sequence ends. In case of abnormal
termination, the control sequence is aborted and the MiCOM C264 Computer
generates a negative acknowledgement. The hardware selection of the device in
“Direct Execute” mode is not allowed.

• Two phases - “SBO once” mode:

− Selection phase:
In the selection phase for a normal termination the MiCOM C264 Computer
generates a positive acknowledgement and proceeds to the next phase of the
sequence (execution phase).

− Execution phase:
If the execution phase ends normally the MiCOM C264 Computer generates a
positive acknowledgement and the control sequence ends. In case of abnormal
termination, the control sequence is aborted and the MiCOM C264 Computer
generates a negative acknowledgement.

• Three phases - “SBO many” mode:

− Selection phase:
ditto “SBO once” mode

− Execution phase:
If the execution phase ends normally the MiCOM C264 Computer generates a
positive acknowledgement and waits for a new execution request. In case of
abnormal termination, the control sequence is aborted and the MiCOM C264
Computer generates a negative acknowledgement.

− Unselection phase:
The MiCOM C264 Computer proceeds to the deselection of the device and ends
control sequence sending a positive acknowledgement. In case of failure while
deselecting the device, the MiCOM C264 Computer sends a negative
acknowledgement.
The two following diagrams schematise the three control modes of the MiCOM C264
Computer.
C264/EN AP/B30 Application

Page 162/396 MiCOM C264/C264C

C0197ENa

FIGURE 170: CONTROL MODE OF THE MiCOM C264 COMPUTER (PART1)

Application C264/EN AP/B30

MiCOM C264/C264C Page 163/396

C0198ENa

FIGURE 171: CONTROL MODE OF THE MiCOM C264 COMPUTER (PART2)

C264/EN AP/B30 Application

Page 164/396 MiCOM C264/C264C

5.1.9.3 Direct execution mode

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

start of
Direct execution request
sequence

no
device direct execute

yes

execution already in
progress ?

execution in progress

Perform execution
checks

no
All checks OK

Perform execution

no
Execution OK

yes

End CO in progress End CO in progress

send negative send positive

acknowledge acknowledge

End of
sequence
C0199ENa

FIGURE 172: CONTROL SEQUENCE FOR DIRECT EXECUTE MODE

Application C264/EN AP/B30

MiCOM C264/C264C Page 165/396

5.1.9.4 SBO once mode

In this mode a control sequence is composed of two phases:

• Selection device phase

• Execution device phase

Selection phase in SBO once mode
During the selection phase initialised by a selection request of the control, the MiCOM C264
Computer performs selection’s checks in order to verify if the device is selectable or not.
If no fail occurs during these checks, the device is selected and positive acknowledgement is
sent. Otherwise the selection request is refused and a negative acknowledgement is sent
giving fails cause. If the selection of the device is accepted the MiCOM C264 Computer start
a delay in which it wait:

• An execution request (open/close , low/raise)

• A cancel of the selection request

After the end of this delay if the execution or the cancel request is not sent, the device is
automatically unselected and a negative acknowledgement is sent. The selection delay is
defined during the configuration process.
Note that only one selection is allowed at a time for a device. When a device is already
selected any other selection is not taken in account (none acknowledgement is sent)
whichever of the initiator.
C264/EN AP/B30 Application

Page 166/396 MiCOM C264/C264C

Unselected
device

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

C0200ENa

FIGURE 173: SELECTION PHASE IN SBO ONCE MODE

Application C264/EN AP/B30

MiCOM C264/C264C Page 167/396

Execution phase in SBO once mode

The execution phase can start only after reception of an execution request and if the device
has been selected before.
In this phase, the MiCOM C264 Computer performs the execution checks, and if no check
failure, it proceeds to the execution according to the configuration, via the IO boards or IED
communication .
If the execution ends normally, a positive acknowledgement is sent, and the control
sequence ends. In case of failure, the control sequence is aborted and the MiCOM C264
Computer sends a negative acknowledgement.
During this phase a “cancel request” is not guaranteed except for synchronised circuit
breakers devices (refer to specifics treatments for synchronised circuit breakers in chapter
6.2 Defining Synchrocheck function).

Execution request–SBO
once device selected

yes

Execution in progress

Execution in progress
to the device

Perform execution
checks
send negative
acknowledge no
All checks OK

Operator
Cancel reques
Perform execution

no
Execution OK

yes

send negative send positive

acknowledge acknowledge

Reset execution in
progress
deselect the device

End of
sequence

C0201ENa

FIGURE 174: EXECUTION PHASE IN SBO ONCE MODE

C264/EN AP/B30 Application

Page 168/396 MiCOM C264/C264C

5.1.9.5 SBO many mode

This mode allows performing one or more control executions after the selection phase. It is
usually used for the tap positioning process in which many controls are sent before reaching
the desired position.
Selection phase on SBO many mode
The selection phase is identical with the “SBO once mode”
Execution phase on SBO many mode
The difference with the SBO once mode is that after performing an execution request, the
MiCOM C264 Computer stays in execution phase waiting a new execution order or an
unselect request. The execution phase ends only after an unselect or cancel request by the
initiator.

Execution phase-device
SBO many selected

Wait request

Execution request

Unselect request cancel request

no
Device selected

yes

Execution in progess

Execution in progress
to the device

Perform execution
send negative checks
acknowledge
no
All checks OK

Perform execution

no
Execution OK

yes

send negative send positive

acknowledge acknowledge

Reset execution in
progress

Deselect the device

Unselection
phase

End of
sequence
C0202ENa

FIGURE 175: EXECUTION PHASE IN SBO MANY MODE

Upon reception of an unselect request the MiCOM C264 Computer ends the execution
phase and goes to the selection phase.
Application C264/EN AP/B30

MiCOM C264/C264C Page 169/396

Unselection phase in SBO many mode

The MiCOM C264 Computer deselects the device and sends a positive acknowledgement.
Note that due to UCA2 features a “cancel” request received during execution phase is
treated like an “unselect” request.

Unselection Phase SBO many Unselection phase

hardware selection

Error during
Not configured
deselection
Deselect the device

Send negative Send positive

acknowledge acknowledge

Set «device
deselected»

End of sequence

C0203ENa

FIGURE 176: UNSELECTION PHASE IN SBO MANY MODE

5.1.9.6 Generic selection checks
Selection checks during selection phase are the following:

• Inter-control delay

• MiCOM C264 Computer mode

• Substation and bay mode states

• Interlock and topological interlocking states

• Automation running control

• Device selectable

• Locked device state

• Status of the device

• Uniqueness
In case of failure, the initiator of the request may bypass some of them. Authorised bypasses
are different according to the control point:

Bypassed checks Control point authorised

Interlock and topological interlocking check Operator Interfaces,
MiCOM C264 Computer’s Automatisms
Substation and bay mode check MiCOM C264 Computer’s Automatisms
Locked device check MiCOM C264 Computer’s Automatisms
Automation running control check MiCOM C264 Computer’s Automatisms
Uniqueness check MiCOM C264 Computer’s Automatisms

The following diagram schematises checks and bypass according the description of the
device.
C264/EN AP/B30 Application

Page 170/396 MiCOM C264/C264C

Unselected device

Inter-control delay Not configured

expired
yes

yes
Computer faulty or in
maint

no

no Substation and bay Not configured

mode OK

Bypass mode check yes

no

Interlock checks
OK Not configured
no
Bypass interlock yes
checks

yes
Not configured
Automatism running

Bypass automatism no

no
Device selectable

yes
Device locked Not configured

no
no
Bypass locked device

no Not configured
Current status of the
device OK
yes

no Uniqueness
OK Not configured
no
Bypass uniqueness yes
check

Abort
selection Continue
selection
phase
phase
C0204ENa

FIGURE 177: GENERIC SELECTION CHECK

If the selection phase checks is not run with success, the control sequence is aborted giving
an explanatory acknowledgement.
Application C264/EN AP/B30

MiCOM C264/C264C Page 171/396

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.
MiCOM C264 Computer mode
Maintenance mode :
Control’s request are not accepted if the MiCOM C264 Computer is in maintenance mode
except some system controls.
Changing mode :

• from “operational” mode to “test” mode :

the specific control “test mode” is refused if there is at least one control in progress.

• from “test” mode to “ operational ” mode :

the specific control “test mode” is refused if there is at least one control in progress.

• from “operational” mode to “maintenance” mode :

all device controls in progress, are aborted and no acknowledgement is sent.
Faulty mode :
None control is accepted in this mode
Substation and bay mode control
A device control may be dependant or not to the substation mode and bay mode. For every
device control the configuration gives the dependency or not to the following modes:

• Substation mode dependency (local /remote)

• SBMC mode dependency ( Bay in maintenance or not)

• Bay mode dependency ( local /remote)

This modes are checked if the dependency is configured.
If the request is refused the selection sequence is aborted with negative acknowledgement.
Interlock control
The configuration process allows to assign or not a logical equation to each order (close and
open) towards the device. The resulting state of the interlock equation (true/false) may affect
the control sequence. If it is false, the selection is refused, except if the user bypasses this
control in the selection request.
In case of fail of this control the sequence is aborted with a negative acknowledgement.
Automation running control
Each device may be locked by the presence of a input information (digital input, IED input
etc) assigned during configuration, and used as a “system input information” giving
automatism’s state (active/inactive) to prevent manually control execution in case an
automatism is active for device monitoring (e.g. ATCC).
In this case the sequence is aborted with a negative acknowledgement, expect if the user
asks to bypass this check.
Device selectable
A device is selectable if during configuration process its control is described to be managed
in “SBO once” or “SBO many” mode and is not already selected. Otherwise the selection
request is refused with negative acknowledgement.
C264/EN AP/B30 Application

Page 172/396 MiCOM C264/C264C

Locked device control

The user may lock a device in order to avoid any wrong move. If the selection concerns a
locked device the request is refused, except if the user forces to bypass this control in the
selection request.
If the device is locked the sequence is aborted with a negative acknowledgement.
Current status of the device
The status check of the device is optional. It is given by a binary input or computed using
more than one binary input (case of circuit breakers).
If it is configured, the configuration process allows defining if it must be checked or not. If the
device status must be checked:

• The device is already in the requested position:

the request is refused with negative acknowledgement

• The device is in invalid position:

the request is refused with negative acknowledgement
If the device status must not be checked, the request is accepted whatever is the device
status.
Uniqueness
It is possible by configuration to prevent to have more than one control at a time:

• to the whole substation or,

• to the bay.
In case of uniqueness of the command at least to one of these levels the selection is
refused, with negative acknowledgement. The user may bypass this control during selection
request.
5.1.9.7 Selection behaviour
In SBO once and SBO many modes, the configuration process allows to describe optionally,
a device selection to control the device.
The following configurations must be considered:

• Configuration 1 :
device with a control for selection and its associated selection position information

• Configuration 2 :
device with a control for selection (without input selection information)
Whatever is the request control (select open/select close, select raise/select low) the
selection of the device is performed as follow:
Configuration 1
The MiCOM C264 Computer:
1. Verify the selection position information, it must be open: if is close, is an abnormal
situation, the selection sequence is stopped with a negative acknowledgement.
2. Send a “close” order of the selection control (via I/O boards or IED) and wait the
selection position information in a given delay (by configuration).
If the selection control has normally executed, and the selection position information of the
device become “set” in the given delay, the selection sequence ends sending a positive
acknowledgement. The MiCOM C264 Computer starts its execution sequence. In case of fail
of the execution of the selection control or if the selection position information remains open
in the given delay the selection sequence ends abnormally sending a negative
acknowledgement.
Application C264/EN AP/B30

MiCOM C264/C264C Page 173/396

Configuration 2
For this configuration, in which only the output control of the selection is configured the
MiCOM C264 Computer: send a “close” order of the selection control (via I/O boards or IED).
If the selection control has normally executed, the selection sequence ends sending a
positive acknowledgement and the MiCOM C264 Computer start its execution sequence.
In case of failure of the execution of the selection control, the sequence ends abnormally
sending a negative acknowledgement.
5.1.9.8 Generic execution checks
At the execution phase, whatever is the execution mode (SBO once, SBO many or Direct
Execute) the MiCOM C264 Computer, before proceeding to the execution of the request,
performs the following checks:

• Inter-control delay

• MiCOM C264 Computer mode

• Substation and bay mode states

• Interlock and topological interlocking states

• Automation running control

• Device selectable (SBO modes only)

• Locked device state

• Current status of the device

• Uniqueness
Execution checks and bypasses are identical to the selection phase. Moreover, in case of
SBO mode (once or many) the MiCOM C264 Computer verifies that the device was
previously selected.
The checks of the execution phase in “SBO many” mode are identical as above but they are
repeated for every execution request (low/raise).
In direct execute mode the device selection is not verified because is not allowed.
5.1.9.9 Execution behaviour
At this step the control request is executed via:

• I/O boards

• IED communication

• System supervisor of the MiCOM C264 Computer for system outputs

The execution via I/O boards is performed only if the MiCOM C264 Computer is in
“operational mode”. If the MiCOM C264 Computer is in “test mode”, the hardware final
execution is not performed. In this case the MiCOM C264 Computer simulates a positive
acknowledgement of hardware execution. It allows to perform control sequence safety in
order to test automatism configuration, control sequence configuration etc. Controls to IEDs
are sent if the MiCOM C264 Computer is in operational mode or test mode.
Execution via I/O boards
According devices features the execution of the control via I/O boards may be performed
using:

• Single Points Control

• Double Control Points

• Digital Setpoints
C264/EN AP/B30 Application

Page 174/396 MiCOM C264/C264C

The execution control sequence differs to the following points:

Single Points Control and Double Control Points:
By configuration, SPC and DPC may be “transient”, “permanent type 1” or “permanent type
2” :

• Transient:
the contact is closed and then re-opened automatically after a delay given by
configuration process. For DPC, configuration gives two delays, one for open and one
for close.

• Permanent type 1:
For this type of output control, The contact is held in the requested position until the
reverse order is received.

• Permanent type 2:
The contact is held in the requested position until confirmation of the position of the
device or after timeout awaiting the new position of the device. In this case, the input
information of the device status must be configured.
Digital SetPoints
A control sequence via Digital SetPoints has particular treatments during the control request.
Refer to the dedicated chapter below.
Execution via IED communication
When an execution request is performed via IED communication, the requested order is
converted to a message to be sending to the intelligent devices, according the
communication protocol.
System Controls execution
For systems outputs the MiCOM C264 Computer activate/deactivate the associated function
(ATCC, MiCOM C264 Computer mode, etc) and if a specific system input (SPS or DPS) is
configured for this control, it takes the requested state and it stored in non-volatile memory.
5.1.9.10 Controls time sequencing
Time sequencing of control is dependent of its configuration:

• Control mode:
Direct Execute, SBO once, SBO many

• Device features:
selection control wired/not wired,
selection position wired/not wired,
device position wired/not wired etc.

• Output control type :

permanent , pulse

• Destination :
I/O board, IED

• Time-out delays:
selection phase time-out,
selection Feedback delays,
open/close Feedback delay etc.
The following chronograms show time sequencing of a control request in the three control
modes.
Application C264/EN AP/B30

MiCOM C264/C264C Page 175/396

Direct Execute time sequencing

The following chronogram shows a example of normal termination on direct execute
sequence.

DPC open
(resp. close)

DPS open/ resp close

(close/resp open)

Feedback Delay

CO Pulse Delay
0-60s
0-5s
3 4 5

1 execution request

C0205ENa

FIGURE 178: NORMAL TERMINATION ON DIRECT EXECUTE

The following controls diagram shows an abnormal termination of Direct Execute sequence.
The device hasn’t took the expected position in the given delay

DPC open
(resp. close)

SPS close
(resp. open)

SPS open
(resp. close)

Feedback Delay

CO Pulse Delay
0-60s
0-5s
3 4 5

1 execution request

C0206ENa

FIGURE 179: ABNORMAL TERMINATION ON DIRECT EXECUTE

C264/EN AP/B30 Application

Page 176/396 MiCOM C264/C264C

SBO once time sequencing

The configuration below are given as examples.
Device Configuration A:
the optional selection control and Selection position information are configured
The following chronogram shows a normal termination of the control sequence

Selection of the
device

Selection position
input

Device output control

Device status

Selection Open/Close Selection

Feedback Feedback Feedback
Delay Selection time-out Delay Delay

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

1 2 5
3 4
Selection phase Execution phase

C0207ENa

FIGURE 180: NORMAL TERMINATION ON SBO ONCE ( E. G. 1)

Stage 1: Device selection (closing the associated output control)
Stage 2: The selection is confirmed by the associated input information in the feedback
delay (0 – 1-sec user selectable)
Stage 3: Close the device before the end of the selection timeout delay (0 – 10 MN user
selectable)
Stage 4: The device has taken the expected position (close) in the feedback delay (0–60
sec user selectable). The MiCOM C264 Computer deselect the device (open
selection output control)
Stage 5: Confirmation of the deselecting of the device in the same given delay than
stage 2.
The following chronogram shows controls sequence which are aborted after time-out of the
selection delay.
Application C264/EN AP/B30

MiCOM C264/C264C Page 177/396

Selection of the
device

Selection position
input

Device output
control

Device status
Input information

Selection Selection
Feedback Feedback Delay
Delay Selection time-out

0-1 s 1-10mn 0-1 s

1 2
3
4
Selection phase

C0208ENa

FIGURE 181: ABNORMAL TERMINATION ON SBO ONCE ( E. G. 1)

Stage 1: Device selection (closing the associated output control)
Stage 2: The selection is confirmed by the associated input information in the feedback
delay
Stage 3: Timeout of the delay - the device is deselected
Stage 4: Confirmation of the deselecting of the device
Device Configuration B:
The optional selection control is configured and Selection position information is not
configured
The following chronogram shows a normal termination of the control sequence

Selection of the
device

Output Control Of
The Device

Device status

Open/Close
Feedback
Selection time-out Delay

0-60s
1-10mn
1
2 3
Execution phase
Selection phase

C0209ENa

FIGURE 182: NORMAL TERMINATION ON SBO ONCE ( E. G. 2)

Stage 1: Device selection (closing the associated output control)
Stage 2: Close the device before the end of the selection timeout delay (0 – 10 MN user
selectable)
Stage 3: The device has taken the expected position (close) in the feedback delay (0–1-
sec user selectable). The MiCOM C264 Computer deselect the device (open
selection output control)
C264/EN AP/B30 Application

Page 178/396 MiCOM C264/C264C

SBO many time sequencing

SBO many mode is exclusively used for control of transformers. For details see chapter 6.4
Defining Tap changer built-in function.
5.1.10 Defining SPC datapoint
To create SPC datapoint:

• Add a SPC from object entry available at the wished system or electrical object level
(1). Depending of the object level, different pre-defined kinds of SPC exist. They are
used for specific needs at electrical topology level (for details see relevant sub-chapter
in DEFINING MICOM C264 COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see chapter 4.10 Setting
system information for MiCOM C264 Computer components).

• Update the SPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPC.

• Update its relation ‘has for profile’ to point to a specific existing profile (2). See chapter
5.2 Linking datapoint to profile, for details about profile definition and setting.

(1)

FIGURE 183: ADDING A SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPC)

(2)

FIGURE 184: LINKING SPC DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPC)
Application C264/EN AP/B30

MiCOM C264/C264C Page 179/396

5.1.10.1 Setting ‘General’ attributes of SPC datapoint

When adding a generic SPC datapoint, some general attributes must be updated:
1. Short and long names of the datapoint used for logging, alarms ...
2. Activation mode (Permanent, Transient, Permanent until feedback) :
For details, see chapter 5.1.9.2
3. Order on duration (0 to 15000 ms by 10 ms) :
useful when activation mode is set to transient and corresponds to activation delay .
For details, see chapter 5.1.9.2
4. Time between two orders (0 to 10000 ms by 100 ms) :
Corresponds to inter-control delay defined in chapter 5.1.9.6 Generic selection checks
and use also for execution checks (see chapter 5.1.9.8 Generic execution checks)
5. Command panel assignment (Yes/No): set to ‘yes’ to enable SPC control at MiCOM
C264 Computer local HMI level.

(1)

(2)
(3)
(4)
(5)

FIGURE 185 : SETTING GENERAL ATTRIBUTES TO SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPC)
5.1.10.2 Setting ‘Dependencies’ attributes of SPC datapoint
When adding a generic SPC datapoint, some ‘dependencies’ attributes must be updated,
that correspond to:

• Substation and bay mode controls and bay uniqueness control defined in chapter
5.1.9.6 Generic selection checks and use also for execution checks (see chapter
5.1.9.8 Generic execution checks), if SPC datapoint is located under a bay

• Substation mode control and substation uniqueness control, if SPC level is higher than
bay
Substation/Bay control uniqueness is globally set at substation level (see chapter 6.1.2
Defining Substation). When substation uniqueness is set, bay uniqueness is implicitly set for
all bays.
C264/EN AP/B30 Application

Page 180/396 MiCOM C264/C264C

Dependencies for SPC level less or equal to bay

1. Substation mode dependency (Yes/No)
2. Bay mode dependency (Yes/No)
3. SBMC mode dependency (Yes/No)
4. Bay control uniqueness dependency (Yes/No):
only significant if control uniqueness is set to bay at substation level

(1)
(2)
(3)
(4)

FIGURE 186 : SETTING DEPENDENCIES ATTRIBUTES TO SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPC)
Dependencies for SPC level higher to bay
1. Substation mode dependency (Yes/No)
2. Substation control uniqueness dependency (Yes/No):
only significant if control uniqueness is set to substation at substation level

(1)
(2)

FIGURE 187 : SETTING DEPENDENCIES ATTRIBUTES TO SPC DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC SPC)
5.1.10.3 Defining SPC feedback
For correct execution behaviour and control acknowledgement, a SPC datapoint can be
linked to a SPS or DPS datapoint that corresponds to a feedback. For instance a circuit-
breaker control SPC is linked to the circuit-breaker status DPS.
To define SPC feedback:

− Add the relation ‘has for feedback’ at SPC level: choose exclusively one of the two
relations ‘has for feedback: SPS datapoint’ (1) or ‘has for feedback: DPS datapoint’ (2)
depending of the kind of feedback datapoint

− Fill the relation with the relevant SPS or DPS datapoint.

− If necessary update the relation attributes:

3. execution time-out (from 0 to 6000000 ms by 100 ms):
In this given delay, feedback must change relatively to the control. If not,
a negative acknowledgement is sent for the control (for details see
chapter 5.1.9 Overview of control sequence processing)
4. ‘status check for command’:
flag (Yes/No) corresponding to the ‘current status check for the device’
described in chapter 5.1.9.6 Generic selection checks and use also for
execution checks (see chapter 5.1.9.8 Generic execution checks)
Application C264/EN AP/B30

MiCOM C264/C264C Page 181/396

(2)

(1)

FIGURE 188: DEFINING SPC FEEDBACK

(3)
(4)

FIGURE 189 : SETTING ATTRIBUTES TO SPC FEEDBACK RELATION

Configuration rules and checks

• For each "SPC", 2 relations "has for feedback" are available, but they are mutually
exclusive

• A Datapoint and its feedback Datapoint must comply with the following rules :
- both must have the same Server device
- if one of them is a "Wired" Datapoint, the other one must be "Wired" too (Here, the
term "Wired" means that the datapoint is linked to a digital or analog channel of a
MiCOM C264 Computer, or linked to an IED address, else it's "System")
- if one of them is a "System" Datapoint, the other one must be "System" too.
- if one of them is linked to an "UCA2/IEC gen IED" through the relation "has for
UCA2/IEC address", this relation must also be defined for the other one

• For a "SPC" Datapoint, if its attribute "activation mode" is set to the "Transient" value,
then the following rule must be respected :
"execution timeout" > "order on duration"
C264/EN AP/B30 Application

Page 182/396 MiCOM C264/C264C

5.1.11 Defining DPC datapoint

To create DPC datapoint:

• Add a DPC from object entry available at the wished system or electrical object level
(1). Depending of the object level, different pre-defined kinds of DPC exist. They are
used for specific needs at electrical topology level (for details see relevant sub-chapter
in DEFINING MICOM C264 COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see chapter 4.10 Setting
system information for MiCOM C264 Computer components).

• Update the DPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPC.

• Update its relation ‘has for profile’ to point to a specific existing profile (2). See chapter
5.2.7 Defining a DPC profile, for details about profile definition and setting.

(1)

FIGURE 190: ADDING A DPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPC)

(2)

FIGURE 191: LINKING DPC DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPC)
Application C264/EN AP/B30

MiCOM C264/C264C Page 183/396

5.1.11.1 Setting ‘General’ attributes of DPC datapoint

When adding a generic DPC datapoint, some general attributes must be updated:
1. Short and long names of the datapoint used for logging, alarms ...
2. Activation mode (Permanent, Transient, Permanent until feedback) :
For details, see chapter 5.1.9.2
3. Close duration (0 to 15000 ms by 10 ms) :
useful when activation mode is set to transient and corresponds to activation delay .
For details, see chapter 5.1.9.2
4. Open duration (0 to 15000 ms by 10 ms) :
useful when activation mode is set to transient and corresponds to activation delay .
For details, see chapter 5.1.9.2
5. Time between two orders (0 to 10000 ms by 100 ms) :
Corresponds to inter-control delay defined in chapter 5.1.9.6 Generic selection checks
and use also for execution checks (see chapter 5.1.9.8 Generic execution checks)
6. Command panel assignment (Yes/No): set to ‘yes’ to enable DPC control at MiCOM
C264 Computer local HMI level.

(1)

(2)
(3)
(4)
(5)

(6)

FIGURE 192 : SETTING GENERAL ATTRIBUTES TO DPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPC)
C264/EN AP/B30 Application

Page 184/396 MiCOM C264/C264C

5.1.11.2 Setting ‘Dependencies’ attributes of DPC datapoint

When adding a generic DPC datapoint, some ‘dependencies’ attributes must be updated,
that correspond to:

• Substation and bay mode controls and bay uniqueness control defined in chapter
5.1.9.6 Generic selection checks and use also for execution checks (see chapter
5.1.9.8 Generic execution checks), if SPC datapoint is located under a bay

• Substation mode control and substation uniqueness control, if DPC level is higher
than bay
Substation/Bay control uniqueness is globally set at substation level (see chapter 6.1.2
Defining Substation). When substation uniqueness is set, bay uniqueness is implicitly set for
all bays.
Dependencies for DPC level less or equal to bay
1. Substation mode dependency (Yes/No)
2. Bay mode dependency (Yes/No)
3. SBMC mode dependency (Yes/No)
4. Bay control uniqueness dependency (Yes/No):
only significant if control uniqueness is set to bay at substation level

(1)
(2)
(3)
(4)

FIGURE 193 : SETTING DEPENDENCIES ATTRIBUTES TO DPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPC)
Dependencies for DPC level higher to bay
1. Substation mode dependency (Yes/No)
2. Substation control uniqueness dependency (Yes/No):
only significant if control uniqueness is set to substation at substation level

(1)

(2)

FIGURE 194 : SETTING DEPENDENCIES ATTRIBUTES TO DPC DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC DPC)
Application C264/EN AP/B30

MiCOM C264/C264C Page 185/396

5.1.11.3 Defining DPC feedback

For correct execution behaviour and control acknowledgement, a DPC datapoint can be
linked to a SPS or DPS datapoint that corresponds to a feedback. For instance a circuit-
breaker control DPC is linked to the circuit-breaker status DPS.
To define DPC feedback:

• Add the relation ‘has for feedback’ at DPC level: choose exclusively one of the two
relations ‘has for feedback: SPS datapoint’ (1) or ‘has for feedback: DPS datapoint’ (2)
depending of the kind of feedback datapoint

• Fill the relation with the relevant SPS or DPS datapoint.

• If necessary update the relation attributes:

3. execution time-out (from 0 to 6000000 ms by 100 ms):
In this given delay, feedback must change relatively to the control. If not, a
negative acknowledgement is sent for the control (for details see chapter 5.1.9
Overview of control sequence processing)
4. ‘status check for command’:
flag (Yes/No) corresponding to the ‘current status check for the device’
described in chapter 5.1.9.6 Generic selection checks and use also for
execution checks (see chapter 5.1.9.8 Generic execution checks)

(2)

(1)

FIGURE 195: DEFINING DPC FEEDBACK

(3)
(4)

FIGURE 196 : SETTING ATTRIBUTES TO DPC FEEDBACK RELATION

C264/EN AP/B30 Application

Page 186/396 MiCOM C264/C264C

Configuration rules and checks

• For each "DPC", 2 relations "has for feedback" are available, but they are mutually
exclusive

• A Datapoint and its feedback Datapoint must comply with the following rules :
- both must have the same Server device
- if one of them is a "Wired" Datapoint, the other one must be "Wired" too (Here, the
term "Wired" means that the datapoint is linked to a digital or analog channel of a
MiCOM C264 Computer, or linked to an IED address, else it's "System")
- if one of them is a "System" Datapoint, the other one must be "System" too.
- if one of them is linked to an "UCA2/IEC gen IED" through the relation "has for
UCA2/IEC address", this relation must also be defined for the other one

• For a "DPC" Datapoint, if its attribute "activation mode" is set to the "Transient" value,
then the following rule must be respected :
"execution timeout" > max [ "open duration" , "close duration" ]
5.1.12 Defining SetPoint datapoint
5.1.12.1 Overview of SetPoint processing
SetPoints are used to send instruction values to the process or to ancillary devices. MiCOM
MiCOM C264 Computers manage three types of SetPoints:

• Digital SetPoints

• SetPoints to IEDs

• System SetPoints
Digital SetPoints
Digital SetPoints are executed via DO channels of Digital Output boards. This type of
controls is managed in “Direct Execute mode” only.
The checks performed during execution phase for SetPoints are:

• Substation and bay modes : check user selectable (cf. 5.1.9.6 Generic selection
checks)

• Uniqueness : check user selectable (cf. 5.1.9.6 Generic selection checks)

• Device Locked : check user selectable (cf. 5.1.9.6 Generic selection checks)

• Automatism running control: check user selectable (cf. 5.1.9.6 Generic selection
checks)
Digital SetPoints may be configured with digital “refresh DO” (see following topic)
The configuration allows also to define two methods of activation of the SetPoint relays:

• Raw activation :
All activated relays which must be open are deactivated, all relays which must be
closed are activated.
if a “read inhibit DO” is configured this one must be deactivate during the relay
positioning (see following topic).

• Incremental activation:
The restitution of the SetPoint and relays can be done by successive increments from
the initial value to the final one. The value of increments and the duration of the
activation are user selectable.
if a “read inhibit DO” is configured this one must be deactivate during every
incremental activation (see following topic).
Application C264/EN AP/B30

MiCOM C264/C264C Page 187/396

Digital SetPoint encoding

The following code are allowed for :

Code Number of bits Range of value

BCD 4 (1 BCD decade) 0 to 9
8 (2 BCD decades) 0 to 99
12 (3 BCD decades) 0 to 999
16 (4 BCD decades) 0 to 9999
Binary 4 0 to 15
7 0 to 127
8 0 to 255
12 0 to 4095
16 0 to 65535
Gray 8 0 to 255
16 0 to 65535
Decimal 16 (1 bit among 6 for the tens, 1 0 to 69
among 10 for the unit)
1 among N 2 0 to 2
to 48 to 0 to 48

Moreover a supplementary bit can be used for the sign (0 indicates a positive value, 1
indicates a negative value).
For details about Gray encoding see chapter 5.1.5.2 Features of digital measurement
acquisition .
Read inhibit signal for digital SetPoint
A dedicated binary output can be used to allow or forbid the reading of the value by the
external device.
There is one (or none) read inhibit (RI) output per value.
If the RI output is a logical one (external polarity applied), the reading is permitted.
The procedure used to output a value with a RI output is :

• Reset the RI output to a logical 0 : read forbidden.

• Wait for N ms

• Output the value

• Wait for N ms

• Set the RI output to a logical 1 : read permitted.

The 0 to 1 transition on the RI output can be used by the external device as a trigger,
indicating that a new value is available.
C264/EN AP/B30 Application

Page 188/396 MiCOM C264/C264C

Value

RI

C0210ENa

FIGURE 197 : READ INHIBIT SIGNAL FOR DIGITAL SETPOINT

Refresh DO for digital SetPoint
SetPoints can be configured with a refresh period, this means that the SetPoint request must
be sent periodically by the transmitter.
If a request on the SetPoint is not received before the end of the refresh period, the SetPoint
is set to non-refreshed and an alarm is raised but and the last received SetPoint is
maintained.
Once a new SetPoint request is received, the SetPoint is set to refreshed, DO are activated
and the alarm is reset.
SetPoints to IEDs
SetPoints controls towards IEDs are managed in “Direct execute mode”. Execution phase is
identical to the digital SetPoints. The execution is performed via the communication protocol
of the concerned IED.
System SetPoint
SetPoints can be locally managed by MiCOM C264 Computer as a system control for
automation for instance. Execution phase is identical to the digital SetPoints.
5.1.12.2 Adding a SetPoint datapoint
To create SetPoint datapoint:
• Add a SetPoint from object entry available at the wished system or electrical object
level (1). Depending of the object level, different pre-defined kinds of SetPoint exist.
They are used for specific needs at electrical topology level (for details see relevant
sub-chapter in DEFINING MICOM C264 COMPUTER CONFIGURATION IN
ELECTRICAL ARCHITECTURE) or system topology level (for details see chapter
4.10 Setting system information for MiCOM C264 Computer components).

• Update the SetPoint attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SetPoint.

• Update its relation ‘has for profile’ to point to a specific existing profile (2). See chapter
5.2.8 Defining a SetPoint profile, for details about profile definition and setting.

(1)

FIGURE 198: ADDING A SETPOINT DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SETPOINT)
Application C264/EN AP/B30

MiCOM C264/C264C Page 189/396

(2)

FIGURE 199: LINKING SETPOINT DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SETPOINT)
5.1.12.3 Setting ‘General’ attributes of SetPoint datapoint
When adding a generic SetPoint datapoint, some general attributes must be updated:
1. Short and long names of the datapoint used for logging, alarms ...
2. SetPoint type and encoding :
for details refer to 5.1.12.1 Overview of SetPoint processing

− Analogue : SetPoint is managed by IED or is a system output

− Digital coded BCD

− Digital coded ‘Pure binary’

− Digital coded ‘Gray’

− Digital coded ‘1 among N’

− Digital coded ‘decimal’

3. Progressive step usage:
only used for digital SetPoint.
No corresponds to Raw activation, Yes to Incremental Activation, described in
5.1.12.1 Overview of SetPoint processing
4. Increment value, significant and visible if Progressive step usage is set to Yes.
For details see 5.1.12.1 Overview of SetPoint processing
5. Increment duration, significant and visible if Progressive step usage is set to Yes.

For details see 5.1.12.1 Overview of SetPoint processing

6. Minimum value:
used for value control and scaling
7. Maximum value:
used for value control and scaling
8. Command panel assignment:
set to ‘yes’ to enable SetPoint control at MiCOM C264 Computer local HMI level.
C264/EN AP/B30 Application

Page 190/396 MiCOM C264/C264C

(1)

(2)

(3)
(4)
(6)
(5)
(7)
(8)

FIGURE 200 : SETTING GENERAL ATTRIBUTES TO SETPOINT DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SETPOINT)
Configuration rules and checks

• Setpoint Datapoint which is wired on DO channels of MiCOM C264 Computer, must

be digital and have its profile attribute “SBO mode” set to "Direct Execute" or “Direct
Execute with SBO popup”
5.1.12.4 Setting ‘Dependencies’ attributes of SetPoint datapoint
When adding a generic SetPoint datapoint, some ‘dependencies’ attributes must be updated,
that correspond to:

• substation and bay mode controls and bay uniqueness control defined in chapter
5.1.9.6 Generic selection checks and use also for execution checks (see chapter
5.1.9.8 Generic execution checks), if SPC datapoint is located under a bay

• substation mode control and substation uniqueness control, if SetPoint level is higher
than bay
Substation/Bay control uniqueness is globally set at substation level (see chapter 6.1.2
Defining Substation). When substation uniqueness is set, bay uniqueness is implicitly set for
all bays.
Dependencies for SetPoint level less or equal to bay
1. Substation mode dependency (Yes/No)
2. Bay mode dependency (Yes/No)
3. SBMC mode dependency (Yes/No)
4. Bay control uniqueness dependency (Yes/No):
only significant if control uniqueness is set to bay at substation level
Application C264/EN AP/B30

MiCOM C264/C264C Page 191/396

(1)
(2)
(3)
(4)

FIGURE 201 : SETTING DEPENDENCIES ATTRIBUTES TO SETPOINT DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SETPOINT)
Dependencies for SetPoint level higher to bay
1. Substation mode dependency (Yes/No)
2. Substation control uniqueness dependency (Yes/No):
only significant if control uniqueness is set to substation at substation level

(1)

(2)

FIGURE 202 : SETTING DEPENDENCIES ATTRIBUTES TO SETPOINT DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC SETPOINT)
5.1.12.5 Defining SetPoint feedback
For correct execution behaviour and control acknowledgement, a SetPoint datapoint can be
linked to a MV datapoint that corresponds to a feedback.
To define SetPoint feedback:

• Add the relation ‘has for feedback’ (1) at SetPoint level

• Fill the relation with the relevant MV datapoint.

• If necessary update the relation attributes:

3. execution time-out (from 0 to 999 s by 1 s):
In this given delay, feedback must change relatively to the control. If not, a
negative acknowledgement is sent for the control (for details see chapter 5.1.9
Overview of control sequence processing)
C264/EN AP/B30 Application

Page 192/396 MiCOM C264/C264C

(1)

FIGURE 203: DEFINING SETPOINT FEEDBACK

(2)

FIGURE 204 : SETTING ATTRIBUTES TO SETPOINT FEEDBACK RELATION

Configuration rules and checks

• A Datapoint and its feedback Datapoint must comply with the following rules :
- both must have the same Server device
- if one of them is a "Wired" Datapoint, the other one must be "Wired" too (Here, the
term "Wired" means that the datapoint is linked to a digital or analog channel of a
MiCOM C264 Computer, or linked to an IED address, else it's "System")
- if one of them is a "System" Datapoint, the other one must be "System" too.
- if one of them is linked to an "UCA2/IEC gen IED" through the relation "has for
UCA2/IEC address", this relation must also be defined for the other one
Application C264/EN AP/B30

MiCOM C264/C264C Page 193/396

5.2 Linking datapoint to profile

Many common characteristics are often shared by a set of datapoints. For instance, all
feeder breaker positions have got the same state labels, alarm and logging behaviour. To
group these common characteristics, profile concept has been embedded in data modelling.
For each kind of datapoints (SPS, DPS,…) exists a relevant profile (SPSProfile,
DPSProfile, …). Several datapoints of the same kind are link-able to the same profile.
Be careful:
The profile attributes can be seen as the datapoint attributes as soon as this datapoint is
linked to the profile. For ease of explanation, this short-cut will be done in this document.
For input datapoints, the following characteristics are set at profile level:

• state labels and eventual unit label for MV and counter,

• definition of the archived and logged states,

• definition of the alarmed states (gravity, delay, audibility),

• definition of state interlocking values,

• definition of forcing/substitution/suppression (FSS) and SBMC facilities,

• links to printers defined in the system topology for alarm and event logging purpose.
For output datapoints, the following characteristics are set at profile level:

• order labels and eventual unit label for setpoints,

• definition of the significant orders for SPC and DPC,

• definition of the alarmed order failure (gravity, delay, audibility),

• definition of the archived and logged transitions,

• SBO mode facility,

• links to printers defined in the system topology for alarm and event logging purpose.
‘Profile’ objects can be put at any level of the system topology but never in the electrical
topology : they concerns only system characteristics. For details about the system topology,
see chapter 4 DEFINING MICOM C264 COMPUTER CONFIGURATION IN SYSTEM
ARCHITECTURE.
A profile object can be added at the following levels of the system topology:

• Scs,

• Ethernet network,

• Any instance of MiCOM C264 Computer,

• Any instance of MiCOM C264 Computer board,

• Any MiCOM C264 Computer printer,

• Any SCADA network managed by a MiCOM C264 Computer,

• Any IED managed by a MiCOM C264 Computer.

When configuring a MiCOM C264 Computer, the best practice is to group all profiles relevant
to its system datapoints at MiCOM C264 Computer level or eventually its sub-components.
Upper levels (Ethernet network or Scs) can be used to define profiles if sharing datapoint
profile between several MiCOM C264 Computers is wished.
C264/EN AP/B30 Application

Page 194/396 MiCOM C264/C264C

For electrical datapoints, different approaches can be done:

• grouping datapoint profiles at MiCOM C264 Computer level per bay basis it manages,

• grouping datapoint profiles at Scs level by kind of bays/modules managed by the

system,

• mixing the 2 previous approaches, particularly for profiles relevant to datapoints

whose level is upper than bay or belonging to same kind of bays fed by several bay
MiCOM C264 Computers.
Be careful:
(Refer to chapter 4.5.1 Connecting MiCOM C264 Computer to others station-bus sub-
systems, for Client / Server definition)
In the set of all the MiCOM C264 Computers of a Scs:

• the following profile functional characteristics:

logging, alarm, archiving and FSS,
are only useful and given to the MiCOM C264 Computer that serves the linked
datapoints because these functions are always done at MiCOM C264 Computer
server level. So, a MiCOM C264 Computer A using a datapoint acquired on a MiCOM
C264 Computer B will never log, alarm or archive events relevant to this datapoint.

• the following profile functional characteristics:

‘state interlocking values’
are given to server and client MiCOM C264 Computers using a datapoint, because
interlock evaluation is a distributed function done on every MiCOM C264 Computer
that needs it before controlling its own electrical modules.

• the following profile functional characteristics:

‘SBMC facilities’
are given to server or client MiCOM C264 Computers using a datapoint exchanged on
a SCADA network they manage, because SBMC filtering is a distributed function done
on MiCOM C264 Computers managing SCADA networks.

• the following profile characteristics:

‘state/order labels’
are given to server or client MiCOM C264 Computers using a datapoint but are only
used by the server: MiCOM C264 Computer bay mimics, logging, alarm definitions are
reduced to datapoints that the MiCOM C264 Computer is server of.
Application C264/EN AP/B30

MiCOM C264/C264C Page 195/396

5.2.1 Defining a SPS profile

5.2.1.1 Adding a SPS Profile
To create a SPS profile:

• Add a SPS profile from object entry available at the wished system object level (1),

• Update the profile attributes (see following sub-chapters)

• Defines if necessary on which printers event logging of linked SPS datapoint is done,
via adding and filling the relation ‘has events logged on’ at profile level (2).

• Defines if necessary on which printers alarm event logging of linked SPS datapoint is
done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).

(1)

FIGURE 205: ADDING A SPS PROFILE (SAMPLE GIVEN AT MICOM C264 COMPUTER LEVEL)

(2)

FIGURE 206: DEFINING EVENT LOGGING PRINTER FOR SPS PROFILE

C264/EN AP/B30 Application

Page 196/396 MiCOM C264/C264C

(3)

FIGURE 207: DEFINING ALARM LOGGING PRINTER FOR SPS PROFILE

5.2.1.2 Setting ‘General’ attributes of SPS Profile
When adding a SPS profile, some general attributes must be updated:
1. Short and long names of the profile only used for profile identification in SCE
And for linked SPS datapoints:
2. Enable or not Forcing/Substitution/Suppression (Yes/No)
3. SBMC dependant (Yes/No):
for details, see 6.1.4.3 Defining SBMC for bay
4. SBMC state substitution value (Suppressed/Set/Reset), significant and visible if SBMC
dependant is set to Yes:
for details, see 6.1.4.3 Defining SBMC for bay
5. Toggling filtering (Yes/No): useful for datapoint acquired on DI board to filter toggling.
6. Initial status (Reset/Set), used for MiCOM C264 Computer software initialisation
especially for system datapoints.

(1)

(2)

(3)
(4)
(5)
(6)

FIGURE 208 : SETTING GENERAL ATTRIBUTES TO SPS PROFILE

Configuration rules and checks

• The profile of a Datapoint of the System topology must have its "enable
Force/Subst/Sup" set the "No" value.
Application C264/EN AP/B30

MiCOM C264/C264C Page 197/396

5.2.1.3 Setting ‘State labels’ attributes of SPS Profile

When adding a SPS profile, some ‘State labels’ attributes must be updated (1). They are
used for events and alarm management at MiCOM C264 Computer level (logging, display).

(1)

FIGURE 209 : SETTING ‘STATE LABELS’ ATTRIBUTES TO SPS PROFILE

5.2.1.4 Setting ‘State treatment’ attributes of SPS Profile
When adding a SPS profile, some ‘State treatment’ attributes must be updated, for each
available state of the linked datapoints (1).
Available flag values are:

• No archive, No logging

• Archive and logging

• Archive only
For MiCOM C264 Computer configuration, a more synthetic vision of logging and archiving is
deduced from these flags: for details refer chapters Defining MiCOM C264 Computer local
archiving of datapoint events and Defining MiCOM C264 Computer local logging of datapoint
events and alarms.

(1)

FIGURE 210 : SETTING ‘STATE TREATMENTS’ ATTRIBUTES TO SPS PROFILE

C264/EN AP/B30 Application

Page 198/396 MiCOM C264/C264C

5.2.1.5 Setting ‘Alarms’ attributes of SPS Profile

When adding a SPS profile, some ‘Alarms’ attributes must be updated, for each available
state of the linked datapoints.
Globally to all SPS states, the attribute ‘generate condition’ (1) defines when alarm are
generated for the datapoint: ‘appearance of the event’ or ‘appearance and disappearance of
the event’.
For each state, following alarm information are settable:
1. Defined alarm (Yes/No)
2. Alarm masked if associated event follows a control (Yes/No): this flag must be set to
‘Yes’ to manage correctly discrepancy (alarm only appears in case of spontaneous
change of state without previous control)
3. Alarm delay (0 to 120 s), to avoid alarm generation if alarm condition disappears
within this delay
4. Alarm gravity level (1 to 5)
5. Alarm audibility (Yes/No), to activate a klaxon
6. Alarm clearing mode, to precise the way alarm clearing is done when alarm condition
disappears:

− Manual : users must explicitly clears the alarm ,

− Automatic : no user intervention is needed to clear the alarm,

− gravity basis : the clearing mode is deduced from the one given at Scs object level
for the relevant gravity
For ‘Set’ and ‘Reset’ state, extra alarm information ‘spurious’ is settable ((8) and (9)). This
information is only significant when the user wants to alarm a spurious SPS datapoint on a
particular event Set or Reset. In fact, the datapoint has got no state, but generates an event.
It is useful to alarm trip information of relays for instance. When setting a spurious alarm,
only the relative state must be defined as alarmed; the other states must be set to ‘not
defined alarm’.
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.
Application C264/EN AP/B30

MiCOM C264/C264C Page 199/396

(1)

(2)

(8)

(3)
(4)
(5)
(6)
(7)

(9)

FIGURE 211 : SETTING ‘ALARMS’ ATTRIBUTES TO SPS PROFILE

5.2.1.6 Setting ‘Interlocking’ attributes of SPS Profile
When adding a SPS profile, some ‘Interlocking’ attributes can be updated for boolean
evaluation of interlocking equation, if SPS belongs to an interlock equation:
1. Interlock value for ‘Reset’ state (False by default, True, or Invalid)
2. Interlock value for ‘Set’ state (True by default, False, or Invalid)
In interlocking equation, all other states are translated as ‘Invalid’

(1)

(2)

FIGURE 212 : SETTING ‘INTERLOCKING’ ATTRIBUTES TO SPS PROFILE

5.2.2 Defining a DPS profile
5.2.2.1 Adding a DPS Profile
To create a DPS profile:
C264/EN AP/B30 Application

Page 200/396 MiCOM C264/C264C

• Add a DPS profile from object entry available at the wished system object level (1),

• Update the profile attributes (see following sub-chapters)

• Defines if necessary on which printers event logging of linked DPS datapoint is done,
via adding and filling the relation ‘has events logged on’ at profile level (2).

• Defines if necessary on which printers alarm event logging of linked DPS datapoint is
done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).

(1)

FIGURE 213: ADDING A DPS PROFILE (SAMPLE GIVEN AT MiCOM C264 COMPUTER LEVEL)

(2)

FIGURE 214: DEFINING EVENT LOGGING PRINTER FOR DPS PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 201/396

(3)

FIGURE 215: DEFINING ALARM LOGGING PRINTER FOR DPS PROFILE

5.2.2.2 Setting ‘General’ attributes of DPS Profile
When adding a DPS profile, some general attributes must be updated:
1. Short and long names of the profile only used for profile identification in SCE
And for linked DPS datapoints:
2. Enable or not Forcing/Substitution/Suppression (Yes/No)
3. SBMC dependant (Yes/No):
for details, see 6.1.4.3 Defining SBMC for bay
4. SBMC state substitution value (Suppressed/Open/Closed/Jammed), significant and
visible if SBMC dependant is set to Yes:
for details, see 6.1.4.3 Defining SBMC for bay
5. Toggling filtering (Yes/No): useful for datapoint acquired on DI board to filter toggling.
6. Initial status (Motion/Open/Closed/Undefined), used for MiCOM C264 Computer
software initialisation especially for system datapoints.

(1)

(2)

(3)
(4)
(5)
(6)

FIGURE 216 : SETTING GENERAL ATTRIBUTES TO DPS PROFILE

Configuration rules and checks

• The profile of a Datapoint of the System topology must have its "enable
Force/Subst/Sup" set the "No" value.
C264/EN AP/B30 Application

Page 202/396 MiCOM C264/C264C

5.2.2.3 Setting ‘State labels’ attributes of DPS Profile

When adding a DPS profile, some ‘State labels’ attributes must be updated (1). They are
used for events and alarm management at MiCOM C264 Computer level (logging, display).

(1)

FIGURE 217 : SETTING ‘STATE LABELS’ ATTRIBUTES TO DPS PROFILE

5.2.2.4 Setting ‘State treatment’ attributes of DPS Profile
When adding a DPS profile, some ‘State treatment’ attributes must be updated, for each
available state of the linked datapoints (1).
Available flag values are:

• No archive, No logging

• Archive and logging

• Archive only
For MiCOM C264 Computer configuration, a more synthetic vision of logging and archiving is
deduced from these flags: for details refer chapters 5.3 Defining MiCOM C264 Computer
local archiving of datapoint events and 5.5 Defining MiCOM C264 Computer local logging of
datapoint events and alarms.

(1)

FIGURE 218 : SETTING ‘STATE TREATMENTS’ ATTRIBUTES TO DPS PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 203/396

5.2.2.5 Setting ‘Alarms’ attributes of DPS Profile

When adding a DPS profile, some ‘Alarms’ attributes must be updated, for each available
state of the linked datapoints.
Globally to all DPS states, the attribute ‘generate condition’ (1) defines when alarm are
generated for the datapoint: ‘appearance of the event’ or ‘appearance and disappearance of
the event’.
For each state, following alarm information are settable:
1. Defined alarm (Yes/No)
2. Alarm masked if associated event follows a control (Yes/No): this flag must be set to
‘Yes’ to manage correctly discrepancy (alarm only appears in case of spontaneous
change of state without previous control)
3. Alarm delay (0 to 120 s), to avoid alarm generation if alarm condition disappears
within this delay
4. Alarm gravity level (1 to 5)
5. Alarm audibility (Yes/No), to activate a klaxon
6. Alarm clearing mode, to precise the way alarm clearing is done when alarm condition
disappears:

− Manual : users must explicitly clears the alarm ,

− Automatic : no user intervention is needed to clear the alarm,

− Gravity basis : the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For ‘Open’ and ‘Closed’ state, extra alarm information ‘spurious’ is settable ((8) and (9)). This
information is only significant when the user wants to alarm a spurious DPS datapoint on a
particular event Open or Closed. In fact, the datapoint has got no state, but generates an
event. It is useful to alarm trip information of relays for instance. When setting a spurious
alarm, only the relative state must be defined as alarmed; the other states must be set to ‘not
defined alarm’.
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.
C264/EN AP/B30 Application

Page 204/396 MiCOM C264/C264C

(1)

(2)

(3)
(4)
(5)
(6)
(7)

(8)

(9)

FIGURE 219 : SETTING ‘ALARMS’ ATTRIBUTES TO DPS PROFILE

5.2.2.6 Setting ‘Interlocking’ attributes of DPS Profile
When adding a DPS profile, some ‘Interlocking’ attributes can be updated for boolean
evaluation of interlocking equation, if DPS belongs to an interlock equation:
1. Interlock value for ‘Jammed’ state (False by default, True, or Invalid)
2. Interlock value for ‘Open’ state (False by default, True, or Invalid)
3. Interlock value for ‘Closed’ state (True by default, False, or Invalid)
In interlocking equation, all other states are translated as ‘Invalid’

(1)

(2)

(3)

FIGURE 220 : SETTING ‘INTERLOCKING’ ATTRIBUTES TO DPS PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 205/396

5.2.3 Defining a MPS profile

5.2.3.1 Adding a MPS Profile
To create a MPS profile:

• Add a MPS profile from object entry available at the wished system object level (1),

• Update the profile attributes (see following sub-chapters)

• Defines if necessary on which printers event logging of linked MPS datapoint is done,
via adding and filling the relation ‘has events logged on’ at profile level (2).

• Defines if necessary on which printers alarm event logging of linked MPS datapoint is
done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).

(1)

FIGURE 221: ADDING A MPS PROFILE (SAMPLE GIVEN AT MiCOM C264 COMPUTER LEVEL)

(2)

FIGURE 222: DEFINING EVENT LOGGING PRINTER FOR MPS PROFILE

C264/EN AP/B30 Application

Page 206/396 MiCOM C264/C264C

(3)

FIGURE 223: DEFINING ALARM LOGGING PRINTER FOR MPS PROFILE

5.2.3.2 Setting ‘General’ attributes of MPS Profile
When adding a MPS profile, some general attributes must be updated:
1. Short and long names of the profile only used for profile identification in SCE
And for linked MPS datapoints:
2. Enable or not Forcing/Substitution/Suppression (Yes/No)
3. SBMC dependant (Yes/No):
for details, see 6.1.4.3 Defining SBMC for bay
4. SBMC state substitution value (Suppressed/Open/Closed/Jammed), significant and
visible if SBMC dependant is set to Yes:
for details, see 6.1.4.3 Defining SBMC for bay

(1)

(2)

(3)
(4)

FIGURE 224 : SETTING GENERAL ATTRIBUTES TO MPS PROFILE

Configuration rules and checks

• The profile of a Datapoint of the System topology must have its "enable
Force/Subst/Sup" set the "No" value.
Application C264/EN AP/B30

MiCOM C264/C264C Page 207/396

5.2.3.3 Setting ‘State labels’ attributes of MPS Profile

When adding a MPS profile, some ‘State labels’ attributes must be updated (1). They are
used for events and alarm management at MiCOM C264 Computer level (logging, display).

(1)

FIGURE 225 : SETTING ‘STATE LABELS’ ATTRIBUTES TO MPS PROFILE

C264/EN AP/B30 Application

Page 208/396 MiCOM C264/C264C

5.2.3.4 Setting ‘State treatment’ attributes of MPS Profile

When adding a MPS profile, some ‘State treatment’ attributes must be updated, for each
available state of the linked datapoints (1).
Available flag values are:

• No archive, No logging

• Archive and logging

• Archive only
For MiCOM C264 Computer configuration, a more synthetic vision of logging and archiving is
deduced from these flags: for details refer chapters 5.3 Defining MiCOM C264 Computer
local archiving of datapoint events and 5.5 Defining MiCOM C264 Computer local logging of
datapoint events and alarms.

(1)

FIGURE 226 : SETTING ‘STATE TREATMENTS’ ATTRIBUTES TO MPS PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 209/396

5.2.3.5 Setting ‘Alarms’ attributes of MPS Profile

When adding a MPS profile, some ‘Alarms’ attributes must be updated, for each available
state of the linked datapoints.
Globally to all MPS states, the attribute ‘generation condition’ (1) defines when alarm are
generated for the datapoint: ‘appearance of the event’ or ‘appearance and disappearance of
the event’.
For each state, following alarm information are settable:
1. Defined alarm (Yes/No)
2. Alarm masked if associated event follows a control (Yes/No): this flag must be set to
‘Yes’ to manage correctly discrepancy (alarm only appears in case of spontaneous
change of state without previous control)
3. Alarm delay (0 to 120 s), to avoid alarm generation if alarm condition disappears
within this delay
4. Alarm gravity level (1 to 5)
5. Alarm audibility (Yes/No), to activate a klaxon
6. Alarm clearing mode, to precise the way alarm clearing is done when alarm condition
disappears:

− Manual : users must explicitly clears the alarm ,

− Automatic : no user intervention is needed to clear the alarm,

− Gravity basis : the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.

(1)

(2)

(3)
(4)
(5)
(6)
(7)

FIGURE 227 : SETTING ‘ALARMS’ ATTRIBUTES TO MPS PROFILE

C264/EN AP/B30 Application

Page 210/396 MiCOM C264/C264C

5.2.3.6 Setting ‘Interlocking’ attributes of MPS Profile

When adding a MPS profile, some ‘Interlocking’ attributes can be updated for boolean
evaluation of interlocking equation, if MPS belongs to an interlock equation:
1. Interlock value for state ‘<i>’ (True by default, False, or Invalid)
In interlocking equation, all other states are translated as ‘Invalid’

(1)

FIGURE 228 : SETTING ‘INTERLOCKING’ ATTRIBUTES TO MPS PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 211/396

5.2.4 Defining a MV profile

5.2.4.1 Adding a MV Profile
To create a MV profile:

• Add a MV profile from object entry available at the wished system object level (1),

• Update the profile attributes (see following sub-chapters)

• Defines if necessary on which printers event logging of linked MV datapoint is done,

via adding and filling the relation ‘has events logged on’ at profile level (2).

• Defines if necessary on which printers alarm event logging of linked MV datapoint is

done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).

(1)

FIGURE 229: ADDING A MV PROFILE (SAMPLE GIVEN AT MiCOM C264 COMPUTER LEVEL)

(2)

FIGURE 230: DEFINING EVENT LOGGING PRINTER FOR MV PROFILE

C264/EN AP/B30 Application

Page 212/396 MiCOM C264/C264C

(3)

FIGURE 231: DEFINING ALARM LOGGING PRINTER FOR MV PROFILE

5.2.4.2 Setting ‘General’ attributes of MV Profile
When adding a MV profile, some general attributes must be updated:
1. Short and long names of the profile only used for profile identification in SCE
And for linked MV datapoints:
2. Enable or not Forcing/Substitution/Suppression (Yes/No)
3. SBMC dependant (Yes to suppressed /No):
for details, see 6.1.4.3 Defining SBMC for bay
4. MV unit used for display, logging and alarm at MiCOM C264 Computer level
5. Reserved for Substation control point usage

(1)

(2)
(3)
(4)

(5)

FIGURE 232 : SETTING GENERAL ATTRIBUTES TO MV PROFILE

Configuration rules and checks

• The profile of a Datapoint of the System topology must have its "enable
Force/Subst/Sup" set the "No" value.
Application C264/EN AP/B30

MiCOM C264/C264C Page 213/396

5.2.4.3 Setting ‘State labels’ attributes of MV Profile

When adding a MV profile, some ‘State labels’ attributes must be updated (1). They are used
for events and alarm management at MiCOM C264 Computer level (logging, display).

(1)

FIGURE 233 : SETTING ‘STATE LABELS’ ATTRIBUTES TO MV PROFILE

5.2.4.4 Setting ‘State treatment’ attributes of MV Profile
When adding a MV profile, some ‘State treatment’ attributes must be updated, for each
available state of the linked datapoints (1).
Available flag values are:

• No archive, No logging

• Archive and logging

• Archive only
For MiCOM C264 Computer configuration, a more synthetic vision of logging and archiving is
deduced from these flags: for details refer chapters Defining MiCOM C264 Computer local
archiving of datapoint events and Defining MiCOM C264 Computer local logging of datapoint
events and alarms.
C264/EN AP/B30 Application

Page 214/396 MiCOM C264/C264C

(1)

FIGURE 234 : SETTING ‘STATE TREATMENTS’ ATTRIBUTES TO MV PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 215/396

5.2.4.5 Setting ‘Alarms’ attributes of MV Profile

When adding a MV profile, some ‘Alarms’ attributes must be updated, for each available
state of the linked datapoints.
Globally to all MV states, the attribute ‘generate condition’ (1) defines when alarm are
generated for the datapoint: ‘appearance of the event’ or ‘appearance and disappearance of
the event’.
For each state, following alarm information are settable:
1. Defined alarm (Yes/No)
2. Alarm delay (0 to 120 s), to avoid alarm generation if alarm condition disappears
within this delay
3. Alarm gravity level (1 to 5)
4. Alarm audibility (Yes/No), to activate a klaxon
5. Alarm clearing mode, to precise the way alarm clearing is done when alarm condition
disappears:

− Manual : users must explicitly clears the alarm ,

− Automatic : no user intervention is needed to clear the alarm,

− Gravity basis : the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.

(1)

(2)

(3)
(4)
(5)
(6)

FIGURE 235 : SETTING ‘ALARMS’ ATTRIBUTES TO MV PROFILE

C264/EN AP/B30 Application

Page 216/396 MiCOM C264/C264C

5.2.4.6 Setting ‘Interlocking’ attributes of MV Profile

When adding a MV profile, some ‘Interlocking’ attributes can be updated for boolean
evaluation of interlocking equation, if MV belongs to an interlock equation:
1. Interlock value for each MV state

(1)

FIGURE 236 : SETTING ‘INTERLOCKING’ ATTRIBUTES TO MV PROFILE

5.2.4.7 Setting ‘Mean value’ attributes of MV Profile
When adding a MV profile, some ‘Mean value’ attributes must be updated (1). They are
reserved for substation control point usage.

(1)

FIGURE 237 : SETTING ‘MEAN VALUE’ ATTRIBUTES TO MV PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 217/396

5.2.5 Defining a Counter profile

5.2.5.1 Adding a Counter Profile
To create a Counter profile:

• Add a Counter profile from object entry available at the wished system object level (1),

• Update the profile attributes (see following sub-chapters)

• Defines if necessary on which printers event logging of linked Counter datapoint is

done, via adding and filling the relation ‘has events logged on’ at profile level (2).

• Defines if necessary on which printers alarm event logging of linked Counter datapoint
is done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).

(1)

FIGURE 238: ADDING A COUNTER PROFILE (SAMPLE GIVEN AT MiCOM C264 COMPUTER LEVEL)

(2)

FIGURE 239: DEFINING EVENT LOGGING PRINTER FOR COUNTER PROFILE

(3)

FIGURE 240: DEFINING ALARM LOGGING PRINTER FOR COUNTER PROFILE

C264/EN AP/B30 Application

Page 218/396 MiCOM C264/C264C

5.2.5.2 Setting ‘General’ attributes of Counter Profile

When adding a Counter profile, some general attributes must be updated:
1. Short and long names of the profile only used for profile identification in SCE
And for linked Counter datapoints:
2. Enable or not Forcing/Substitution/Suppression (Yes/No)
3. SBMC dependant (Yes to suppressed /No):
for details, see 6.1.4.3 Defining SBMC for bay
4. EPI value for counter scaling
5. Reserved for Substation control point usage
6. Counter unit used for display, logging and alarm at MiCOM C264 Computer level
7. Reserved for Substation control point usage

(1)

(2)

(3)
(4)
(5)
(6)
(7)

FIGURE 241 : SETTING GENERAL ATTRIBUTES TO COUNTER PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 219/396

5.2.5.3 Setting ‘State labels’ attributes of Counter Profile

When adding a Counter profile, some ‘State labels’ attributes must be updated (1). They are
used for events and alarm management at MiCOM C264 Computer level (logging, display).

(1)

FIGURE 242 : SETTING ‘STATE LABELS’ ATTRIBUTES TO COUNTER PROFILE

5.2.5.4 Setting ‘State treatment’ attributes of Counter Profile
When adding a Counter profile, some ‘State treatment’ attributes must be updated, for each
available state of the linked datapoints (1).
Available flag values are:

• No archive, No logging

• Archive and logging

• Archive only
For MiCOM C264 Computer configuration, a more synthetic vision of logging and archiving is
deduced from these flags: for details refer chapters 5.3 Defining MiCOM C264 Computer
local archiving of datapoint events and 5.5 Defining MiCOM C264 Computer local logging of
datapoint events and alarms.

(1)

FIGURE 243 : SETTING ‘STATE TREATMENTS’ ATTRIBUTES TO COUNTER PROFILE

C264/EN AP/B30 Application

Page 220/396 MiCOM C264/C264C

5.2.5.5 Setting ‘Alarms’ attributes of Counter Profile

When adding a Counter profile, some ‘Alarms’ attributes must be updated, for each available
state of the linked datapoints.
Globally to all Counter states, the attribute ‘generate condition’ (1) defines when alarm are
generated for the datapoint: ‘appearance of the event’ or ‘appearance and disappearance of
the event’.
For each state, following alarm information are settable:
1. Defined alarm (Yes/No)
2. Alarm delay (0 to 120 s), to avoid alarm generation if alarm condition disappears
within this delay
3. Alarm gravity level (1 to 5)
4. Alarm audibility (Yes/No), to activate a klaxon
5. Alarm clearing mode, to precise the way alarm clearing is done when alarm condition
disappears:

− Manual : users must explicitly clears the alarm ,

− Automatic : no user intervention is needed to clear the alarm,

− Gravity basis : the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.

(1)

(2)

(3)
(4)
(5)
(6)

FIGURE 244 : SETTING ‘ALARMS’ ATTRIBUTES TO COUNTER PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 221/396

5.2.5.6 Setting ‘Mean value’ attributes of Counter Profile

When adding a Counter profile, some ‘Mean value’ attributes must be updated (1). They are
reserved for substation control point usage.

(1)

FIGURE 245 : SETTING ‘MEAN VALUE’ ATTRIBUTES TO COUNTER PROFILE

5.2.6 Defining a SPC profile
5.2.6.1 Adding a SPC Profile
To create a SPC profile:

• Add a SPC profile from object entry available at the wished system object level (1),

• Update the profile attributes (see following sub-chapters)

• Defines if necessary on which printers event logging of linked SPC datapoint is done,
via adding and filling the relation ‘has events logged on’ at profile level (2).

• Defines if necessary on which printers alarm event logging of linked SPC datapoint is
done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).

(1)

FIGURE 246: ADDING A SPC PROFILE (SAMPLE GIVEN AT MiCOM C264 COMPUTER LEVEL)

(2)

FIGURE 247: DEFINING EVENT LOGGING PRINTER FOR SPC PROFILE

C264/EN AP/B30 Application

Page 222/396 MiCOM C264/C264C

(3)

FIGURE 248: DEFINING ALARM LOGGING PRINTER FOR SPC PROFILE

5.2.6.2 Setting ‘General’ attributes of SPC Profile
When adding a SPC profile, some general attributes must be updated:
1. Short and long names of the profile only used for profile identification in SCE
And for linked SPC datapoints:
2. SBO mode (for details see chapter 5.1.9.1 Device control mode and device type)
Available values are:

− Direct execute

− SBO operate once

− SBO operate many

− Direct execute with SBO control box (reserved to substation control point usage),
similar to ‘Direct execute’ for MiCOM C264 Computer
3. SBO time-out (from 0 to 600 s step 1s), significant if SBO mode is set to ‘SBO operate
once’ or ‘SBO operate many’. For details see chapter 5.1.9.7 Selection behaviour)

(1)

(2)

(3)

FIGURE 249 : SETTING GENERAL ATTRIBUTES TO SPC PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 223/396

5.2.6.3 Setting ‘Order labels’ attributes of SPC Profile

When adding a SPC profile, some ‘Order labels’ attributes must be updated. They are used
for events and alarm management at MiCOM C264 Computer level (logging, display) and for
correct SPC order management:
1. ‘Order off’ usage (Yes/No)
2. ‘Order on’ usage (Yes/No)
3. ‘Order off’ label
4. ‘Order on’ label

(1)

(2)

(3)

(4)

FIGURE 250 : SETTING ‘ORDER LABELS’ ATTRIBUTES TO SPC PROFILE

5.2.6.4 Setting ‘State treatment’ attribute of SPC Profile
When adding a SPC profile, A ‘State treatment’ attribute must be updated globally for all
available control and acknowledgement steps of the linked datapoints (1).
Available flag values are:

• No archive, No logging

• Archive and logging

• Archive only
For MiCOM C264 Computer configuration, a more synthetic vision of logging and archiving is
deduced from this flag: for details refer chapters 5.3 Defining MiCOM C264 Computer local
archiving of datapoint events and 5.5 Defining MiCOM C264 Computer local logging of
datapoint events and alarms.

(1)

FIGURE 251 : SETTING ‘STATE TREATMENT’ ATTRIBUTE TO SPC PROFILE

C264/EN AP/B30 Application

Page 224/396 MiCOM C264/C264C

5.2.6.5 Setting ‘Alarms’ attributes of SPC Profile

When adding a SPC profile, some ‘Alarms’ attributes must be updated, for the correct alarm
management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm information are settable:
1. Defined alarm (Yes/No)
2. Alarm delay (0 to 120 s), to avoid alarm generation if alarm condition disappears
within this delay
3. Alarm gravity level (1 to 5)
4. Alarm audibility (Yes/No), to activate a klaxon
5. Alarm clearing mode, to precise the way alarm clearing is done when alarm condition
disappears:

− Manual : users must explicitly clears the alarm ,

− Automatic : no user intervention is needed to clear the alarm,

− Gravity basis : the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.

(1)
(2)

(3)
(4)
(5)

FIGURE 252 : SETTING ‘ALARMS’ ATTRIBUTES TO SPC PROFILE

5.2.6.6 Setting ‘Interlocking and FBD’ attributes of SPC Profile
When adding a SPC profile, some ‘Interlocking and FBD’ attributes can be updated for
boolean evaluation of interlocking equation, if the SPC belongs to an interlock equation or if
the SPC is an input of FBD automation (see chapter 6.6.1 Defining a FBD fast automation
and 6.6.6 Defining interlocking):
The following alarm information are settable:
1. boolean value for ‘On order’ (True by default, False, or Invalid)
2. boolean value for ‘Off order’ (False by default, True, or Invalid)
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.

(1)
(2)

FIGURE 253 : SETTING ‘INTERLOCKING AND FBD’ ATTRIBUTES TO SPC PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 225/396

5.2.7 Defining a DPC profile

5.2.7.1 Adding a DPC Profile
To create a DPC profile:

• Add a DPC profile from object entry available at the wished system object level (1),

• Update the profile attributes (see following sub-chapters)

• Defines if necessary on which printers event logging of linked DPC datapoint is done,
via adding and filling the relation ‘has events logged on’ at profile level (2).

• Defines if necessary on which printers alarm event logging of linked DPC datapoint is
done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).

(1)

FIGURE 254: ADDING A DPC PROFILE (SAMPLE GIVEN AT MiCOM C264 COMPUTER LEVEL)

(2)

FIGURE 255: DEFINING EVENT LOGGING PRINTER FOR DPC PROFILE

C264/EN AP/B30 Application

Page 226/396 MiCOM C264/C264C

(3)

FIGURE 256: DEFINING ALARM LOGGING PRINTER FOR DPC PROFILE

5.2.7.2 Setting ‘General’ attributes of DPC Profile
When adding a SPC profile, some general attributes must be updated:
1. Short and long names of the profile only used for profile identification in SCE
And for linked DPC datapoints:
2. SBO mode (for details see chapter 5.1.9.1 Device control mode and device type)
Available values are:

− Direct execute

− SBO operate once

− SBO operate many

− Direct execute with SBO control box (reserved to substation control point usage),
similar to ‘Direct execute’ for MiCOM C264 Computer
3. SBO time-out (from 0 to 600 s step 1s), significant if SBO mode is set to ‘SBO operate
once’ or ‘SBO operate many’. For details see chapter 5.1.9.7 Selection behaviour)

(1)

(2)
(3)

FIGURE 257 : SETTING GENERAL ATTRIBUTES TO DPC PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 227/396

5.2.7.3 Setting ‘Order labels’ attributes of DPC Profile

When adding a SPC profile, some ‘Order labels’ attributes must be updated. They are used
for events and alarm management at MiCOM C264 Computer level (logging, display) and for
correct SPC order management:
1. ‘Order open’ usage (Yes/No)
2. ‘Order close’ usage (Yes/No)
3. ‘Order open’ label
4. ‘Order close’ label

(1)

(2)

(3)

(4)

FIGURE 258 : SETTING ‘ORDER LABELS’ ATTRIBUTES TO DPC PROFILE

5.2.7.4 Setting ‘State treatment’ attribute of DPC Profile
When adding a DPC profile, A ‘State treatment’ attribute must be updated globally for all
available control and acknowledgement steps of the linked datapoints (1).
Available flag values are:

• No archive, No logging

• Archive and logging

• Archive only
For MiCOM C264 Computer configuration, a more synthetic vision of logging and archiving is
deduced from this flag: for details refer chapters 5.3 Defining MiCOM C264 Computer local
archiving of datapoint events and 5.5 Defining MiCOM C264 Computer local logging of
datapoint events and alarms.

(1)

FIGURE 259 : SETTING ‘STATE TREATMENT’ ATTRIBUTE TO DPC PROFILE

C264/EN AP/B30 Application

Page 228/396 MiCOM C264/C264C

5.2.7.5 Setting ‘Alarms’ attributes of DPC Profile

When adding a DPC profile, some ‘Alarms’ attributes must be updated, for the correct alarm
management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm information are settable:
1. Defined alarm (Yes/No)
2. Alarm delay (0 to 120 s), to avoid alarm generation if alarm condition disappears
within this delay
3. Alarm gravity level (1 to 5)
4. Alarm audibility (Yes/No), to activate a klaxon
5. Alarm clearing mode, to precise the way alarm clearing is done when alarm condition
disappears:

− Manual : users must explicitly clears the alarm ,

− Automatic : no user intervention is needed to clear the alarm,

− Gravity basis : the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.

(1)
(2)

(3)
(4)
(5)

FIGURE 260 : SETTING ‘ALARMS’ ATTRIBUTES TO DPC PROFILE

5.2.7.6 Setting ‘Interlocking and FBD’ attributes of DPC Profile
When adding a DPC profile, some ‘Interlocking and FBD’ attributes can be updated for
boolean evaluation of interlocking equation, if the SPC belongs to an interlock equation or if
the DPC is an input of FBD automation (see chapters 6.6.1 Defining a FBD fast automation
and 6.6.6 Defining interlocking):
The following alarm information are settable:
1. boolean value for ‘Open order’ (False by default, True, or Invalid)
2. boolean value for ‘Close order’ (True by default, False, or Invalid)
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.

(1)
(2)

FIGURE 261 : SETTING ‘INTERLOCKING AND FBD’ ATTRIBUTES TO DPC PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 229/396

5.2.8 Defining a SetPoint profile

5.2.8.1 Adding a SetPoint Profile
To create a SetPoint profile:

• Add a SetPoint profile from object entry available at the wished system object level
(1),

• Update the profile attributes (see following sub-chapters)

• Defines if necessary on which printers event logging of linked SetPoint datapoint is

done, via adding and filling the relation ‘has events logged on’ at profile level (2).

• Defines if necessary on which printers alarm event logging of linked SetPoint

datapoint is done, via adding and filling the relation ‘has alarm events logged on’ at
profile level (3).

(1)

FIGURE 262: ADDING A SETPOINT PROFILE (SAMPLE GIVEN AT MiCOM C264 COMPUTER LEVEL)

(2)

FIGURE 263: DEFINING EVENT LOGGING PRINTER FOR SETPOINT PROFILE

C264/EN AP/B30 Application

Page 230/396 MiCOM C264/C264C

(3)

FIGURE 264: DEFINING ALARM LOGGING PRINTER FOR SETPOINT PROFILE

5.2.8.2 Setting ‘General’ attributes of SetPoint Profile
When adding a SetPoint profile, some general attributes must be updated:
1. Short and long names of the profile only used for profile identification in SCE
And for linked SetPoint datapoints:
2. SBO mode
Available values are:

− Direct execute

− SBO operate once, reserved for future use

− SBO operate many, reserved for future use

− Direct execute with SBO control box (reserved to substation control point usage),
similar to ‘Direct execute’ for MiCOM C264 Computer, reserved for future use
3. SBO time-out (from 0 to 600 s step 1s), significant if SBO mode is set to ‘SBO operate
once’ or ‘SBO operate many’.
4. SetPoint unit used for display, logging and alarm at MiCOM C264 Computer level

(1)

(2)

(3)
(4)

FIGURE 265 : SETTING GENERAL ATTRIBUTES TO SETPOINT PROFILE

Application C264/EN AP/B30

MiCOM C264/C264C Page 231/396

5.2.8.3 Setting ‘State treatment’ attribute of SetPoint Profile

When adding a SetPoint profile, A ‘State treatment’ attribute must be updated globally for all
available control and acknowledgement steps of the linked datapoints (1).
Available flag values are:

• No archive, No logging
• Archive and logging
• Archive only
For MiCOM C264 Computer configuration, a more synthetic vision of logging and archiving is
deduced from this flag: for details refer chapters Defining MiCOM C264 Computer local
archiving of datapoint events and Defining MiCOM C264 Computer local logging of datapoint
events and alarms.

(1)

FIGURE 266 : SETTING ‘STATE TREATMENT’ ATTRIBUTE TO SETPOINT PROFILE

5.2.8.4 Setting ‘Alarms’ attributes of SetPoint Profile
When adding a SetPoint profile, some ‘Alarms’ attributes must be updated, for the correct
alarm management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm information are settable:
1. Defined alarm (Yes/No)
2. Alarm delay (0 to 120 s), to avoid alarm generation if alarm condition disappears
within this delay
3. Alarm gravity level (1 to 5)
4. Alarm audibility (Yes/No), to activate a klaxon
5. Alarm clearing mode, to precise the way alarm clearing is done when alarm condition
disappears:
− Manual : users must explicitly clears the alarm ,

− Automatic : no user intervention is needed to clear the alarm,

− Gravity basis : the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For MiCOM C264 Computer configuration, all flags are significant for datapoints it is server
of.

(1)
(2)

(3)
(4)
(5)

FIGURE 267 : SETTING ‘ALARMS’ ATTRIBUTES TO SETPOINT PROFILE

C264/EN AP/B30 Application

Page 232/396 MiCOM C264/C264C

5.3 Defining MiCOM C264 Computer local archiving of datapoint events

A MiCOM C264 Computer manages only archiving of the datapoints it is server of (Refer to
chapter 4.5.1 Connecting MiCOM C264 Computer to others station-bus sub-systems, for
Client / Server definition).
For MiCOM C264 Computer, archiving is available or not for all the events appearing on a
given datapoint. Archiving is activated as soon as one ‘state treatment’ attribute is set to
‘Archive and logging’ or ‘archive only’ at datapoint profile level (see relevant sub-chapter of
5.2 Linking datapoint to profile).
5.4 Defining MiCOM C264 Computer local archiving of datapoint alarms
A MiCOM C264 Computer manages only archiving of the datapoints it is server of (Refer to
chapter 4.5.1 Connecting MiCOM C264 Computer to others station-bus sub-systems, for
Client / Server definition).
Alarm archiving at MiCOM C264 Computer level is defined globally for all the MiCOM C264
Computers at Scs object level (see chapter 4.1 Setting general system configuration relevant
to MiCOM C264 Computers - point (6))
5.5 Defining MiCOM C264 Computer local logging of datapoint events and alarms
A MiCOM C264 Computer manages only logging of the datapoints it is server of (Refer to
chapter 4.5.1 Connecting MiCOM C264 Computer to others station-bus sub-systems, for
Client / Server definition).
For MiCOM C264 Computer, event logging is available or not for all the events appearing on
a given datapoint.
Event logging is activated as soon as the datapoint profile is linked to the local printer of the
MiCOM C264 Computer via the relation ‘has events logged on’. To link a datapoint profile to
a printer, see relevant sub-chapter of 5.2 Linking datapoint to profile.
Alarm logging is activated as soon as the datapoint profile is linked to the local printer of the
MiCOM C264 Computer via the relation ‘has alarm events logged on’. To link a datapoint
profile to a printer, see relevant sub-chapter of 5.2 Linking datapoint to profile.
To create a MiCOM C264 Computer printer, see chapter 4.4.6 Adding a printer.
5.6 Defining acquisition source for input datapoints
Input datapoints have real-time values, fed by several ways exclusive each other:

• Acquisition via input channel(s)

• Acquisition via IED legacy network

• Acquisition via non-PACiS UCA2 communicant IED

• (virtual) acquisition via software production:

− diagnostic and control of system components

− datapoints relevant to built-in function and user’s function

− MV or counter datapoint relevant to CT/VT board computation

5.6.1 Acquiring input datapoint via input channels
At SCE level, linking datapoint to specific channels (DI or AI channels) belonging to PACiS
MiCOM C264 Computer’s DIU200-210, CCU200, AIU201 or AIU210 boards does input
datapoint wiring.
Application C264/EN AP/B30

MiCOM C264/C264C Page 233/396

5.6.1.1 Wiring SPS datapoint, via 1 DI channel

A wired SPS is in the SET or in the RESET state, depending on the state of the associated
Digital Input and of the mode, normal or inverted (defined in configuration), of the SPS.

DI state Mode SPS state

ON Normal SET
OFF Normal RESET
ON Inverted RESET
OFF Inverted SET
Faulty * SELFCHECK FAULTY

To wire a SPS datapoint on DI channel:

• Add the relation ‘wired on’ (1) at SPS datapoint level

• Fill the relation with the relevant DI channel:

When datapoint level is lower or equal to bay, only DI channels from DIU boards
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

• If necessary update the relation attribute ‘inverted value’ (2), whose meaning is given
previously.

(1)

FIGURE 268: WIRING SPS DATAPOINT, VIA 1 DI CHANNEL

(2)

FIGURE 269: UPDATING WIRING OF SPS DATAPOINT

C264/EN AP/B30 Application

Page 234/396 MiCOM C264/C264C

5.6.1.2 Wiring DPS datapoint, via 2 DI channels

To wire a DPS datapoint on 2 DI channels:

• Add the relations ‘closed wired on’ (1) and ‘open wired on’ (2) at DPS datapoint level

• Fill the relations with the relevant DI channels:

When datapoint level is lower or equal to bay, only DI channels from DIU boards
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

(1)

(2)

FIGURE 270: WIRING DPS DATAPOINT, VIA 2 DI CHANNEL

Application C264/EN AP/B30

MiCOM C264/C264C Page 235/396

5.6.1.3 Wiring MPS datapoint, via DI channels

MPS datapoint wiring is done via 3 or more DI channels (up to 16) for each state, and an
optional DI channel for ‘read inhibit’ indication.
To wire a MPS datapoint on n DI channels (n <=16):

• Add the relations ‘state <i> wired on’ (1) at MPS datapoint level, for each available
state of the MPS (i begins from 0)

• Fill the relations with the relevant DI channels:

When datapoint level is lower or equal to bay, only DI channels from DIU boards
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

• If a read inhibit signal exists for the MPS (see chapter 5.1.4.4 Definition of MPS
inhibition filtering), add the relations ‘read inhibit wired on’ (2) at MPS datapoint level.

(2)

(1)

FIGURE 271: WIRING MPS DATAPOINT, VIA N DI CHANNEL

C264/EN AP/B30 Application

Page 236/396 MiCOM C264/C264C

5.6.1.4 Wiring MV and TPI datapoint

MV and TPI datapoint wiring is done via 1 AI channel (analogue measurement) or via up to
64 DI channels (for digital measurements) and two optional DI channels for ‘read inhibit’
indication and sign bit.
To wire a MV or TPI datapoint on AI channel:

• Add the relation ‘wired on’ (1) at MV or TPI datapoint level

• Fill the relation with the relevant AI channel:

When datapoint level is lower or equal to bay, only AI channels from AIU boards
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

• To define sensor range of the AI channel, refer to chapter 4.4.5 Configuring an AI

channel

(1)

FIGURE 272: WIRING MV OR TPI DATAPOINT, VIA 1 AI CHANNEL

To wire a MV or TPI datapoint on n DI channels (n <=64):

• Add the relations ‘bit <i> wired on’ (1) at MV or TPI datapoint level, for each available
bit channel of the MV or TPI (i begins from 0)

• Fill the relations with the relevant DI channels:

When datapoint level is lower or equal to bay, only DI channels from DIU boards
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

• If a read inhibit signal exists for the MV or TPI (see chapter 5.1.5.2 Features of digital
measurement acquisition ), add the relations ‘read inhibit wired on’ (2) at MV or TPI
datapoint level.

• If a sign bit exists for the MV, add the relations ‘sign bit wired on’ (3) at MV datapoint
level.

(1)

(2)

(3)

FIGURE 273: WIRING MV OR TPI DATAPOINT, VIA N DI CHANNEL

Application C264/EN AP/B30

MiCOM C264/C264C Page 237/396

5.6.1.5 Wiring Counter datapoint

Counter datapoint wiring is done via 1 DI channel (simple counter) or 2 DI channels (double
counter).
To wire a Counter datapoint on DI channel:

• Add the relation ‘primary input wired on’ (1) at Counter datapoint level

• If it is a double counter, add the extra relation ‘secondary input wired on’ (2) at
Counter datapoint level

• Fill the relations with the relevant DI channel:

When datapoint level is lower or equal to bay, only DI channels from DIU boards
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

(1)

(2)

FIGURE 274: WIRING COUNTER DATAPOINT, VIA DI CHANNEL

C264/EN AP/B30 Application

Page 238/396 MiCOM C264/C264C

5.6.2 Acquiring input datapoint via IED legacy network

At SCE level, IED wiring is not described. Acquiring input datapoint issued from IED is done
by giving it a communication address in the relay’s legacy network mapping. This addressing
can be seen as a virtual wiring regardless to channel wiring.
Addressing MPS datapoint on IED legacy network is not available.
Depending on legacy network type, addressing information can be different.
See chapter 4 DEFINING MICOM C264 COMPUTER CONFIGURATION IN SYSTEM
ARCHITECTURE for further details about IED legacy network creation and addressing
mapping definition.
To link an input datapoint to an existing IED address in a IED mapping:

• Add the relation ‘has for IED address’ (1) at datapoint level. Generally, only one
relation adding is available for datapoint, except for DPS datapoint where up to 2
relations can be added, corresponding to each elementary bit of the DPS if the legacy
protocol does not support the DPS feature. In that case, the DPS is split in two SPS
regarding to the legacy protocol.

• Fill the relation with the relevant IED address:

When datapoint level is lower or equal to bay, only IED addresses from IEDs
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

(1)

FIGURE 275: ACQUIRING INPUT DATAPOINT VIA IED LEGACY NETWORK

(E.G. SPS DATAPOINT)
Configuration rules and checks

• A "DPS" Datapoint can have 1 or 2 relation(s) "has for IED address":

− In the case of 1 IED address, the attribute "contact type" of the IED address must
be set to the "Unused" value.

− In the case of 2 IED addresses, the attribute "contact type" of one of the IED
addresses must be set to the "open" value, and the attribute "contact type" of the
other IED address must be set to the "close" value.
Application C264/EN AP/B30

MiCOM C264/C264C Page 239/396

5.6.3 Acquiring input datapoint via non-PACiS UCA2 communicant IED

At SCE level, IED wiring is not described. Acquiring input datapoint issued from UCA2 IED is
done by giving it a communication address in the relay’s UCA2 mapping. This addressing
can be seen as a virtual wiring regardless to channel wiring (implicit association is done at
IED level).
See relevant application guide for further details about UCA2 IED creation and
corresponding UCA2 addressing mapping definition (nevertheless, similar UCA2 addressing
mapping is described in chapter 4.5.2 Defining addressing mapping of station-bus network of
the present guide).
To link an input datapoint to an existing UCA2 IED address in the IED UCA2 mapping:

• Add the relation ‘has for UCA2 address’ (1) at datapoint level

• Fill the relation with the relevant UCA2 address

Do not confuse:

• Give an UCA2 address to a datapoint, still wired on a MiCOM C264 Computer, via
‘has for UCA2 address’ relation adding.

• Give an UCA2 address to a datapoint on an UCA2 IED. In that case the datapoint can
not be wired, because it is seen as produced or managed by the UCA2 IED.

(1)

FIGURE 276: ACQUIRING INPUT DATAPOINT VIA NON-PACiS UCA2 IED

(E.G. SPS DATAPOINT)
5.6.4 Producing input datapoint
An other way to produce input datapoint real-time values is to allow software functions to
generate them.
This is done at several software levels:

• Supervision of UCA2 PACiS system device, where system datapoints are produced to
indicate mode device, synchro device, database status,…

• Supervision of UCA2 PACiS system device board (board status diagnostics)

• Supervision of legacy network and IED managed by PACiS MiCOM C264 Computers
(communication status diagnostics)

• Supervision of redundancy between 2 PACiS MiCOM C264 Computers (redundancy

status diagnostics)

• Supervision of logging printers managed by OI server or PACiS MiCOM C264

Computer (printer status diagnostics)

• Supervision of archiving managed by OI server (archiving status diagnostics)

• Facilities given by built-in electrical and grouping functions or user’s function, in PACiS
MiCOM C264 Computers.
C264/EN AP/B30 Application

Page 240/396 MiCOM C264/C264C

5.6.4.1 Implicit system input datapoint via system decomposition

In data modelling, many components of the system topology own input datapoints. Their
creation are generally implicit when creating the component: they belongs to its hierarchy.
Most of system input datapoints when transmitted on station bus network are addressed in
UCA2 diagnostics bricks.
The list of such system datapoints are given in chapter 4.10 Setting system information for
MiCOM C264 Computer components.
5.6.4.2 Implicit electrical input datapoint via built-in function
Implicit input datapoints can be embedded in built-in function creation. For details refer to the
following chapters:

• 6.2 Defining Synchrocheck function,

• 6.3 Defining Auto-recloser built-in function,

• 6.4 Defining Tap changer built-in function,

• 6.5 Defining AVR built-in function.

Generally, these electrical datapoints are transmitted on station bus network in a specific
UCA2 brick of built-in function.
5.6.4.3 Explicit electrical input datapoint via user function
By setting output plug, fast automation can produce real-time value for electrical input
datapoint (see chapter 6.6.1 Defining a FBD fast automation).
So can slow automation when it manages electrical datapoints or owns management input
datapoints (see chapter 0 Defining an ISaGRAF slow automation).
For group needs, an electrical SPS containing the group result must be created (see
chapter 6.6.3 Defining a group).
For SPS-DPS association, the resulting DPS is the product of the two SPS associations (see
chapter 6.6.5 Producing DPS ).
To define (open or close) interlocking equation on SPC or DPC datapoint, an extra (open or
close) SPS should be produced, whose result is interlocking equation computation (see
chapter 6.6.6 Defining interlocking)
5.6.4.4 Explicit electrical input datapoint via CT/VT computation
An other way to produce a MV electrical datapoint is to link it to a CT/VT MiCOM C264
Computer board. Then, a specific link attribute must be filled to precise which MV
computation is concerned (power, harmonic ...)
Data produced by CT/VT board computation concern:

• RMS Values of phase voltage

• RMS values of busbar voltage

• RMS values of phase current

• RMS values of residual voltage and current

• Fundamental sequence components

• Active Power

• Reactive Power

• Apparent Power

• Frequency

• Harmonics levels
Application C264/EN AP/B30

MiCOM C264/C264C Page 241/396

To link a MV datapoint to a CT/VT computation:

• Add the relation ‘is computed by’ (1) at datapoint level,

• Fill the relation with the relevant CT/VT board
When datapoint level is lower or equal to bay, only the CT/VT board belonging to the
MiCOM C264 Computer that manages the bay, is available. To define the MiCOM
C264 Computer that manages a bay, refer to chapter 6.1.4 Defining Bay.
• Update the relation attribute ‘measure type’ (2), giving the computation type.

(1)

FIGURE 277: DEFINING CT/VT COMPUTATION FOR A MV DATAPOINT

5.7 Defining control source for output datapoints
Output datapoints have real-time control values, managed by several ways exclusive each
other:

• control via output channel(s)

• control via IED legacy network
• control via non-PACiS UCA2 communicant IED
• (virtual) control via software production:
− control of system components

− datapoints relevant to built-in function and user’s function

5.7.1 Controlling output datapoint via output channels
At SCE level, linking datapoint to specific channels (DO channels) belonging to PACiS
MiCOM C264 Computer’s DOU200 or CCU200 boards does output datapoint wiring.
5.7.1.1 Wiring SPC datapoint, via 1 DO channel
To wire a SPC datapoint on DO channel:

• Add the relation ‘wired on’ (1) at SPC datapoint level

• Fill the relation with the relevant DO channel:

When datapoint level is lower or equal to bay, only DO channels from DOU boards
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

(1)

FIGURE 278: WIRING SPC DATAPOINT, VIA 1 DO CHANNEL

C264/EN AP/B30 Application

Page 242/396 MiCOM C264/C264C

5.7.1.2 Wiring DPC datapoint, via 2 or 4 DO channels

To wire a DPC datapoint on 2 or 4 DO channels:

• Add the relations ‘closed wired on’ (1) and ‘open wired on’ (2) at DPC datapoint level
(these relations can be added twice in case of 4 DO channels use)

• Fill the relations with the relevant DO channels:

When datapoint level is lower or equal to bay, only DO channels from DOU boards
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

(1)

(2)

FIGURE 279: WIRING DPC DATAPOINT, VIA 2 DO CHANNEL

5.7.1.3 Wiring SetPoint datapoint
SetPoint datapoints can only be wired on digital channels (up to 48 DO channels) and two
optional DO channel for ‘read inhibit’ indication and sign bit.
To wire a SetPoint datapoint on n DO channels (n <=48):

• Add the relations ‘bit <i> wired on’ (1) at SetPoint datapoint level, for each available bit
channel of the SetPoint (i begins from 0)

• Fill the relations with the relevant DO channels:

When datapoint level is lower or equal to bay, only DO channels from DOU boards
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

• If a read inhibit signal exists for the SetPoint (see chapter 5.1.12.1 Overview of
SetPoint processing), add the relations ‘read inhibit wired on’ (2) at SetPoint datapoint
level.

• If a refresh signal exists for the SetPoint (see chapter 5.1.12.1 Overview of SetPoint
processing), add the relations ‘refresh wired on’ (2) at SetPoint datapoint level.

• If a sign bit exists for the SetPoint, add the relations ‘sign bit wired on’ (4) at SetPoint
datapoint level.
Application C264/EN AP/B30

MiCOM C264/C264C Page 243/396

(1)

(2)

(3)
(4)

FIGURE 280: WIRING SETPOINT DATAPOINT, VIA N DO CHANNEL

Configuration rules and checks

• Setpoint Datapoint which is wired on DO channels of MiCOM C264 Computer, must

be digital and have its profile attribute “SBO mode” set to "Direct Execute" or “Direct
Execute with SBO popup”
C264/EN AP/B30 Application

Page 244/396 MiCOM C264/C264C

5.7.2 Controlling output datapoint via IED legacy network

At SCE level, IED wiring is not described. Controlling output datapoint issued from IED is
done by giving it a communication address in the relay’s legacy network mapping. This
addressing can be seen as a virtual wiring regardless to channel wiring (implicit association
is done at IED level).
Depending on legacy network type, addressing information can be different.
See chapter 4 DEFINING MICOM C264 COMPUTER CONFIGURATION IN SYSTEM
ARCHITECTURE for further details about IED legacy network creation and addressing
mapping definition.
To link an output datapoint to an existing IED address in a IED mapping:

• Add the relation ‘has for IED address’ (1) at datapoint level. Generally, only one
relation adding is available for datapoint, except for DPC datapoint where up to 2
relations can be added, corresponding to each elementary bit of the DPC if the legacy
protocol does not support the DPC feature. In that case, the DPC is split in two SPC
regarding to the legacy protocol.

• Fill the relation with the relevant IED address:

When datapoint level is lower or equal to bay, only IED addresses from IEDs
belonging to the MiCOM C264 Computer that manages the bay, are available. To
define the MiCOM C264 Computer that manages a bay, refer to chapter 6.1.4 Defining
Bay.

(1)

FIGURE 281: ACQUIRING OUTPUT DATAPOINT VIA IED LEGACY NETWORK

(E.G. SPC DATAPOINT)
Configuration rules and checks

• A "DPC" Datapoint can have 1 or 2 relation(s) "has for IED address":

− In the case of 1 IED address, the attribute "contact type" of the IED address must
be set to the "Unused" value.

− In the case of 2 IED addresses, the attribute "contact type" of one of the IED
addresses must be set to the "open" value, and the attribute "contact type" of the
other IED address must be set to the "close" value.
Application C264/EN AP/B30

MiCOM C264/C264C Page 245/396

5.7.3 Controlling output datapoint via non-PACiS UCA2 communicant IED

At SCE level, IED wiring is not described. Controlling output datapoint issued from IED is
done by giving it a communication address in the relay’s UCA2 mapping. This addressing
can be seen as a virtual wiring regardless to channel wiring.
See relevant application guide for further details about UCA2 IED creation and
corresponding UCA2 addressing mapping definition (nevertheless, similar UCA2 addressing
mapping is described in chapter 4.5.2 Defining addressing mapping of station-bus network of
the present guide).
To link an output datapoint to an existing UCA2 IED address in the IED UCA2 mapping:

• Add the relation ‘has for UCA2 address’ (1) at datapoint level

• Fill the relation with the relevant UCA2 address

Do not confuse:

• Give an UCA2 address to a datapoint, still wired on a MiCOM C264 Computer, via
‘has for UCA2 address’ relation adding.

• Give an UCA2 address to a datapoint on an UCA2 IED. In that case the datapoint can
not be wired, because it is seen as produced or managed by the UCA2 IED.

(1)

FIGURE 282: ACQUIRING OUTPUT DATAPOINT VIA NON-PACiS UCA2 IED

(E.G. SPC DATAPOINT)
C264/EN AP/B30 Application

Page 246/396 MiCOM C264/C264C

5.7.4 Producing output datapoint

An other way to produce output datapoint real-time control values is to allow software
functions to generate them.
This is done at several software levels:

• Supervision of UCA2 PACiS system device, where system datapoints are produced to
control mode device, database switch,…
These output system datapoints are only used by System Management Tool.

• Supervision of redundancy between 2 PACiS MiCOM C264 Computers (redundancy

controls)

• Facilities given by built-in electrical and grouping functions or user’s function, in PACiS
MiCOM C264 Computers.
5.7.4.1 Implicit system output datapoint via system decomposition
In data modelling, only PACiS devices of the system topology own output datapoints for
device mode management and database switch. Their creation are implicit when creating the
device: they belong to its hierarchy.
MiCOM C264 Computer redundancy needs specific output typed datapoints that must be
manually added in MiCOM C264 Computer’s hierarchy.
Most of system output datapoints when transmitted on station bus network are addressed in
UCA2 diagnostics bricks.
The list of such system datapoints are given in chapter 4.10 Setting system information for
MiCOM C264 Computer components.
5.7.4.2 Implicit electrical output datapoint via built-in function
Implicit output datapoints can be embedded in built-in function creation. For details refer to
the following chapters:

• 6.2 Defining Synchrocheck function,

• 6.3 Defining Auto-recloser built-in function,

• 6.4 Defining Tap changer built-in function,

• 6.5 Defining AVR built-in function.

Generally, these electrical datapoints are transmitted on station bus network in a specific
UCA2 brick of built-in function.
5.7.4.3 Explicit electrical datapoint via user function
By setting output plug, fast automation can produce real-time order value for electrical output
datapoint (see chapter 6.6.1 Defining a FBD fast automation).
So can slow automation when it manages electrical output datapoints or owns management
output datapoints (see chapter Defining an ISaGRAF slow automation).
For xPS-xPC association, an electrical output SPC or DPC linked to the SPS or DPS must
exist and sometimes be created (see chapter 6.6.4 Controlling xPC ).
Application C264/EN AP/B30

MiCOM C264/C264C Page 247/396

6. DEFINING MiCOM C264 COMPUTER CONFIGURATION IN ELECTRICAL

ARCHITECTURE
6.1 Defining electrical topology
At SCE data modelling level, the entry point of electrical topology is the ‘Site’ object. At the
moment, a ‘Site object’ (1) can be composed of only one ‘Substation’ object.
A substation (2) is constituted of ‘Voltage level’ objects, each of them corresponding to an
electrical partitioning of the substation by voltage level value (in kV).
A voltage level (3) is an aggregation of ‘Bay’ object (4), grouping of electrical devices, called
module (5). Generally , this grouping is electrically self-safety, i.e. can be isolated from
others bays by switchgears for maintenance and managed by only one PACiS MiCOM C264
Computer. There are different kinds of bays: feeder, transformer, busbar, bus coupler, bus
section, capacitor bank and generic bay.
Coupling two voltage levels is commonly done via transformer. To respect SCE data
modelling electrical partitioning, this transformer must belong to a transformer bay (6)
arbitrary put in one of both voltage levels (generally its primary). An extra relation on
transformer refines to which voltage level its secondary (or primary) belongs.
Final electrical components are modules composing bays. There are different kinds of
modules: circuit breaker, switchgear, transformer, motor, generator, battery, capacitor,
inductor, converter and generic module. An extra module exists to describe substation
external connection (external line).
Every level of the electrical topology, except Site level, can owns datapoints whose features
and configuration are described in chapter 5 DEFINING DATAPOINT.

(1): Site

(2): Substation
datapoints
(3): Vo ltage level

(4): bay ‘Feeder’

(5): module ‘circuit

breaker

(6): bay ‘Transformer’

C0211ENa

FIGURE 283: ELECTRICAL TOPOLOGY DEFINITION (E.G.)

C264/EN AP/B30 Application

Page 248/396 MiCOM C264/C264C

Feeder bay

Bus coupling bay

Transformer bay
Busbar bay

Bus section bay

C0212ENa

FIGURE 284: BAY SAMPLES

Switchgear
module
Q1

Circuit-breaker
module
Q0

Switchgear
module Q9

Switchgear Q8
Module (earth)

External line
module

C0213ENa

FIGURE 285: MODULE SAMPLES

Application C264/EN AP/B30

MiCOM C264/C264C Page 249/396

6.1.1 Defining Site

When creating a new configuration using SCE, the electrical topology is automatically
instantiated via ‘Site’ root object, containing a mandatory ‘Substation’ object.
Site object corresponds to customer project identification: its attributes ‘short name’ and ‘long
name’ (1) can be entered at SCE level. At the moment, these attributes are not used.

(1)

FIGURE 286 : SETTING ATTRIBUTES TO SITE

6.1.2 Defining Substation
When creating a new configuration using SCE, the electrical topology is automatically
instantiated via ‘Site’ root object, containing a mandatory ‘Substation’ object.
Substation object corresponds to customer substation identification: its attributes ‘short
name’ and ‘long name’ (1) must be entered at SCE level, for proper logging formatting and
datapoint identification, at MiCOM C264 Computer and operator interface levels.
At substation level, the attribute ‘default uniqueness’ (2) defines the way control uniqueness
is managed for the whole substation. Available values are:

• None :
no control uniqueness is provided by PACiS system for the substation,

• Substation level :
control uniqueness is provided by PACiS system for the whole substation, i.e. 2
simultaneous controls are refused within the substation, except for control datapoints
configured as substation uniqueness independent (see chapters 5.1.10.2 Setting
‘Dependencies’ attributes of SPC datapoint, 5.1.11.2 Setting ‘Dependencies’ attributes
of DPC datapoint, 5.1.12.4 Setting ‘Dependencies’ attributes of SetPoint datapoint),

• Bay level:
control uniqueness is provided by PACiS system for an entire bay, i.e. 2 simultaneous
controls are refused within the same bay, except for control datapoints configured as
bay uniqueness independent (see chapters 5.1.10.2 Setting ‘Dependencies’ attributes
of SPC datapoint, 5.1.11.2 Setting ‘Dependencies’ attributes of DPC datapoint,
5.1.12.4 Setting ‘Dependencies’ attributes of SetPoint datapoint).

(1)

(2)

FIGURE 287 : SETTING ATTRIBUTES TO SUBSTATION

Bay and substation uniqueness are managed by MiCOM C264 Computer by synthesis of
mandatory SPS datapoints ‘Order running’, automatically added under a bay at its creation
(see chapter 6.1.4 Defining Bay).
C264/EN AP/B30 Application

Page 250/396 MiCOM C264/C264C

Configuration rules and checks

• when control uniqueness is set to substation, all MiCOM C264 Computers of

substation must be UCA2 client of all ‘order running’ SPS datapoints defined for all the
bays. So, proper UCA2 configuration must be done for all MiCOM C264 Computers to
insure that feature. For details about UCA2 configuration, refer to chapter 4.5
Networking MiCOM C264 Computer on the station-bus network.
6.1.2.1 Adding substation generic datapoint
An addition of a substation typed datapoint is done under SCE via the “Object entry” area at
substation level by clicking on mouse’s right button. Here are listed generic datapoint
(standard usage) out of scope of the specific substation functions:

• Local/remote for substation (see chapter 6.1.2.2 Defining Local/Remote for substation)

• Taking Control for substation and SCDA links (see chapter 6.1.2.3 Defining Taking
Control for substation and SCADA links)
For more details about datapoints and their configuration, refer to chapter 5 DEFINING
DATAPOINT.

FIGURE 288: ADDING SUBSTATION GENERIC DATAPOINT

Application C264/EN AP/B30

MiCOM C264/C264C Page 251/396

6.1.2.2 Defining Local/Remote for substation

A substation can be in remote or local control mode.
The Remote mode indicates that the substation is controlled from Remote Control Point
(RCP), via gateway. No controls can be sent from Substation Control Point level (except if
the concerned bay is in SBMC mode, see chapter 6.1.4.3 Defining SBMC for bay).
The Local mode indicates that the substation is controlled from PACiS Operator Interface
(Substation Control Point). The controls issued from RCP are not taken into account by the
system, they are refused.
Some controls, defined during the configuration phase, can be independent of the substation
control mode : it means they can be issued from SCP or RCP whatever the current control
mode is. Controls from configurable automation (see chapter 6.6 Defining electrical
regulation by user function) are accepted whatever was the mode. For details about the
configuration of this dependency attribute, refer to chapters:

• SPC : 5.1.10.2 Setting ‘Dependencies’ attributes of SPC datapoint,

• DPC: 5.1.10.2 Setting ‘Dependencies’ attributes of SPC datapoint,

• SetPoint: 5.1.12.4 Setting ‘Dependencies’ attributes of SetPoint datapoint.

In Local or Remote mode the information acquired by MiCOM C264 Computers and IEDs
are always sent to RCP and PACiS Operator Interface.
The automatic “Forcing of Invalid BI” function (refer to chapter 5.1.1.4 Forcing of invalid BI's)
is used to avoid processing of invalid states of the substation mode (the local or remote
replacement state is defined in configuration). The “Forced Local” state is processed as the
“Local” state. The “Forced Remote” state is processed as the “Remote” state.
Moreover, all UCA2 clients (i.e. Operator Interface, gateway, MiCOM C264 Computers) will
automatically forced the substation mode to “Forced Local” or “Forced Remote” if it takes the
UNKNOWN state (due for example to the loss of communication between the MiCOM C264
Computer which manages the substation mode and the UCA2 clients).
To activate Local/remote substation facilities:

• add the optional datapoints ‘Local/remote DPS’ (1) and/or ‘Loc/rem ctrl DPC’ (2), via
the “Object entry” area at substation level by clicking on mouse’s right button

• configure them (see chapter 5 DEFINING DATAPOINT),

• if necessary, do not forget to link via ‘has for feedback’ relation, the control of the
Local/remote with the Local/remote status datapoint.

(2)

(1)

FIGURE 289: DEFINING LOCAL/REMOTE FOR SUBSTATION

C264/EN AP/B30 Application

Page 252/396 MiCOM C264/C264C

Configuration rules and checks

Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
MiCOM C264 Computer

• if "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback)

• if "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is mandatory

• if "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.

• If, under a Substation, a "DPC" or "SPC" Datapoint has its attribute "Substation mode
dependency" set to "Yes", then the Substation "Local/remote DPS" Datapoint must be
present.

• If the two Datapoints "Local/remote DPS" and "Loc/rem ctrl DPC" are present, they
must have the same Server device

• "Loc/rem ctrl DPC" Datapoint must have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”
6.1.2.3 Defining Taking Control for substation and SCADA links
This facility allows a Remote Control Point (RCP) to force the mode of the substation from
LOCAL to REMOTE and to define on which link the SCADA controls must be accepted.
To activate Taking control facilities for a given SCADA network:

• add the optional datapoints ‘Taking Control’ (2) and ‘Taking status’ (1), via the “Object
entry” area at substation level by clicking on mouse’s right button

• configure them (see chapter 5 DEFINING DATAPOINT),

• add the relation ‘is taken control of’ at ‘Taking status’ datapoint level (3), and fill it with
the relevant given SCADA network.

• do not forget to link via ‘has for feedback’ relation, the control with the status
datapoint.

(2)

(1)

(1)

FIGURE 290: DEFINING TAKING CONTROL FOR A SCADA LINK

Application C264/EN AP/B30

MiCOM C264/C264C Page 253/396

Configuration rules and checks

• If, at least, one SCADA network is linked to a Taking Control function, all the SCADA
Networks of the system must be linked to a Taking Control function.

• If a "Taking Status" datapoint is linked to a SCADA Network, it must also be linked to a

"Taking Control" datapoint through the relation "has for feedback".

• A "Taking Control" datapoint must be linked to a "Taking Status" datapoint through the
relation "has for feedback".

• The "Taking Control" datapoint must have its "activation mode" attribute set to a
"Permanent…" value.
The "Taking Status" datapoint must have its "detection mode" attribute set to the
"Permanent" value.

• Both "Taking Control" and "Taking Status" datapoints must be linked to a SCADA
address in the mapping of their SCADA network.

• If a Taking-Control function is defined then, the "Loc/rem ctrl DPC" for substation must
be present and not wired.

• The Server of the Local/Remote Datapoints is the Server of each Datapoints couple
"Taking Status" / "Taking Control".

• All the devices having a SCADA network linked to a Taking-Control function are :
- Clients of each Datapoints couple "Taking Status" / "Taking Control".
- Clients of the Datapoints couple "Local/remote DPS" / "Loc/rem ctrl DPC".
6.1.2.4 Adding user function to substation
An addition of a substation user function is done under SCE via the “Object entry” area at
substation level by clicking on mouse’s right button.
For more details about user function usage and their configuration, refer to chapter 6.6
Defining electrical regulation by user function.

FBD user function

ISA GRAF user function

FIGURE 291: ADDING USER FUNCTION TO SUBSTATION

C264/EN AP/B30 Application

Page 254/396 MiCOM C264/C264C

6.1.3 Defining Voltage level

At substation level, several ‘voltage level’ objects can be added. A voltage level corresponds
to a substation area whose electrical bays and sub-modules refers to the same nominal
voltage. There is an exception for transformer bay, coupling 2 different voltage levels, that
must be arbitrary located on one of the both.
To create a voltage level, add it from object entry available at substation level, as following:

FIGURE 292: ADDING A VOLTAGE LEVEL

When adding a voltage level, some general attributes must be updated:
1. Short and long names of the voltage level used for logging, alarms ...
2. Nominal value in kV
3. ATCC regulation existence on the voltage level (Yes/No):
when set to ‘yes’, an extra tab-pane appears for the voltage level, to enter specific
ATCC regulation feature for the voltage level. For details about ATCC configuration
and this attribute, refer to chapter 6.5 Defining AVR built-in function

(1)
(2)

FIGURE 293 : SETTING GENERAL ATTRIBUTES TO MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
Application C264/EN AP/B30

MiCOM C264/C264C Page 255/396

6.1.3.1 Adding voltage level generic datapoint

An addition of a voltage level typed datapoint is done under SCE via the “Object entry” area
at voltage level by clicking on mouse’s right button. Here are listed generic datapoint
(standard usage).
For more details about datapoints and their configuration, refer to chapter 5 DEFINING
DATAPOINT.

FIGURE 294: ADDING VOLTAGE LEVEL GENERIC DATAPOINT

6.1.3.2 Adding user function to voltage level
An addition of a voltage level user function is done under SCE via the “Object entry” area at
voltage level by clicking on mouse’s right button.
For more details about user function usage and their configuration, refer to chapter 6.6
Defining electrical regulation by user function.

FBD user function

ISA GRAF user function

C0214ENa

FIGURE 295: ADDING USER FUNCTION TO VOLTAGE LEVEL

C264/EN AP/B30 Application

Page 256/396 MiCOM C264/C264C

6.1.4 Defining Bay

At ‘voltage level’ level, several ‘bay’ objects can be added. A voltage level corresponds to a
substation area whose electrical bays and sub-modules refers to the same nominal voltage.
There is an exception for transformer bay, coupling 2 different voltage levels, that must be
arbitrary located on one of the both.
To create a bay:

• Add a typed one from object entry available at voltage level (1)

• Update the bay attributes

• Update its ‘is managed by’ relation, to define which MiCOM C264 Computer manages
the bay (2).

(1)

FIGURE 296: ADDING A TYPED BAY

(2)

FIGURE 297: DEFINING MiCOM C264 COMPUTER MANAGING A BAY

When adding a bay, some general attributes must be updated:
1. Short and long names of the bay used for logging, alarms ...
2. Control uniqueness used for output datapoints under the bay.
Available values are:

− None:
No control uniqueness is provided by PACiS system for output datapoints under
the bay.

− See substation definition :

control uniqueness is inherited from attribute ‘default uniqueness’ at substation
level (see chapter 6.1.2 Defining Substation),
Application C264/EN AP/B30

MiCOM C264/C264C Page 257/396

(1)

(2)

FIGURE 298 : SETTING GENERAL ATTRIBUTES TO BAY

(SAMPLE GIVEN FOR BAY TYPE ‘FEEDER’)
When adding a bay, a mandatory SPS datapoint ‘order running’ is automatically created at
bay level. This datapoint allows PACiS system to manage control uniqueness at substation
and bay level: it is set when a control is in progress on a bay.
Configuration rules and checks

• when control uniqueness is set to substation, all MiCOM C264 Computers of

substation must be UCA2 client of all ‘order running’ SPS datapoints defined for all the
bays. So, proper UCA2 configuration must be done for all MiCOM C264 Computers to
insure that feature. For details about UCA2 configuration, refer to chapter 4.5
Networking MiCOM C264 Computer on the station-bus network.
Typed bay features
Using typed bay allows implicit sub-component creation. Hereafter are listed all typed bays
with their sub-component features:

• Feeder :
A circuit-breaker and external line modules are mandatory and implicitly created,

• Transformer:
A transformer module is mandatory and implicitly created,

• Bus coupler:
A circuit-breaker module is mandatory and implicitly created,

• Bus section:
A circuit-breaker module is mandatory and implicitly created,

• Capacitor bank:
A capacitor module is mandatory and implicitly created,

• Shunt:
A circuit-breaker module is mandatory and implicitly created,

• Busbar:
No module is available. This typed bay must be seen as a single electrical node. A
specific attribute ‘node reference’ used for electrical topology definition for ATCC
function can be entered for a busbar. For details about ATCC configuration and this
attribute, refer to chapter 6.5 Defining AVR built-in function

• Generic bay:
No sub-component constraint.
Used for general usage outside the scope of other previous typed bays.
C264/EN AP/B30 Application

Page 258/396 MiCOM C264/C264C

6.1.4.1 Adding bay generic datapoint

An addition of a bay typed datapoint is done under SCE via the “Object entry” area at bay
level by clicking on mouse’s right button. Here are listed generic datapoint (standard usage)
out of scope of the specific bay functions:

• Local/remote for bay (see chapter 6.1.4.2 Defining Local/Remote for bay)

• SBMC for bay (see chapter 6.1.4.3 Defining SBMC for bay)

• Group computation (see chapter 6.6.3 Defining a group)

For more details about datapoints and their configuration, refer to chapter 5 DEFINING
DATAPOINT.

FIGURE 299: ADDING BAY GENERIC DATAPOINT

Application C264/EN AP/B30

MiCOM C264/C264C Page 259/396

6.1.4.2 Defining Local/Remote for bay

Each bay can be independently in Remote or Local mode.
The Remote mode indicates that the bay is controlled from the upper level, i.e. Remote
Control Point (RCP) or Substation Control Point (SCP) depending on the current substation
control mode (refer to chapter 6.1.4.2 Defining Local/Remote for bay). No controls can be
sent from Bay Control Point (BCP) level, i.e. operator interface at the MiCOM C264
Computer that manages the bay.
The Local mode indicates that the bay is controlled from BCP. The controls issued from
upper level are not taken into account by the bay.
Some controls, defined during the configuration phase, can be independent of the bay
control mode : it means they can be issued from any control points whatever was the current
control mode. Controls from configurable automation (ISaGRAF) are accepted in remote
mode. For details about the configuration of this dependency attribute, refer to chapters:

• SPC : 5.1.10.2 Setting ‘Dependencies’ attributes of SPC datapoint,

• DPC: 5.1.10.2 Setting ‘Dependencies’ attributes of SPC datapoint,

• SetPoint: 5.1.12.4 Setting ‘Dependencies’ attributes of SetPoint datapoint.

In Local or Remote mode, the information issued from the bay is always sent to SCP and
RCP.
The automatic “Forcing of Invalid BI” function (refer to chapter 5.1.1.4 Forcing of invalid BI's)
is used to avoid processing of invalid states of the bay mode (the local or remote
replacement state is defined in configuration). The “Forced Local” state is processed as the
“Local” state. The “Forced Remote” state is processed as the “Remote” state.
To activate Local/remote bay facilities:

• add the optional datapoints ‘Local/remote DPS’ (1) and/or ‘Loc/rem ctrl DPC’ (2), via
the “Object entry” area at bay level by clicking on mouse’s right button

• configure them (see chapter 5 DEFINING DATAPOINT),

• if necessary, do not forget to link via ‘has for feedback’ relation, the control of the
Local/remote with the Local/remote status datapoint.

(2)

(1)

FIGURE 300: DEFINING LOCAL/REMOTE FOR BAY

C264/EN AP/B30 Application

Page 260/396 MiCOM C264/C264C

Configuration rules and checks

Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
MiCOM C264 Computer

• if "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback)

• if "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must not be wired.

• if "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.

• If, under a Bay, a "DPC" or "SPC" Datapoint has its attribute "bay mode dependency"
set to "Yes", then the Bay "Local/remote DPS" Datapoint must be present.

• "Loc/rem ctrl DPC" Datapoint must have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”
If the "GHU200" board of a MiCOM C264 Computer has its attribute "HMI type" set to the
"Simple" value, then the "Local/remote DPS" Datapoints of the bays managed by this
MiCOM C264 Computer must be all be "Wired" or all "System".
6.1.4.3 Defining SBMC for bay
Each bay can be set in SBMC mode (Site Based Maintenance Control mode).
In SBMC mode, a bay does not take into account the commands issued from Remote
Control Point (RCP), even if the substation is in remote control (see chapter 6.1.2.2 Defining
Local/Remote for substation). Some controls, defined during the configuration phase, can be
independent of the SBMC mode. For details about the configuration of this dependency
attribute, refer to chapters:

• SPC : 5.1.10.2 Setting ‘Dependencies’ attributes of SPC datapoint,

• DPC: 5.1.10.2 Setting ‘Dependencies’ attributes of SPC datapoint,

• SetPoint: 5.1.12.4 Setting ‘Dependencies’ attributes of SetPoint datapoint.

This function provides a facility to control selected bays from the Substation Control Point
(SCP) and optionally to suppress or force to a pre-defined state, datapoint for the RCP while
the substation is in Remote mode. If configured as SBMC dependant at its profile level, a
datapoint belonging to a bay in SBMC mode takes the state defined in the profile
configuration for the RCP, but is still processed normally in the SCS (e.g. all processes
inside the system are unaffected by the state modification of an information at the RCP
interface).
The state of datapoints sent to RCP are defined in their profile configuration. For each type
of datapoint, they are :

SPS SUPPRESSED, SET, RESET

DPS SUPPRESSED, OPEN, CLOSE, JAMMED
MPS SUPPRESSED, UNDEFINED
MV, TPI and Counter SUPPRESSED

For details about SBMC configuration at datapoint profile level, refer to chapters:

• 5.2.1.2 Setting ‘General’ attributes of SPS Profile,

• 5.2.2.2 Setting ‘General’ attributes of DPS Profile,

• 5.2.3.2 Setting ‘General’ attributes of MPS Profile,

• 5.2.4.2 Setting ‘General’ attributes of MV Profile,

• 5.2.5.2 Setting ‘General’ attributes of Counter Profile

Application C264/EN AP/B30

MiCOM C264/C264C Page 261/396

To activate SBMC facilities at bay level:

• add the optional datapoints ‘SBMC SPS’ (1) and ‘SBMC control SPC’ (2), via the
“Object entry” area at bay level by clicking on mouse’s right button

• configure them (see chapter 5 DEFINING DATAPOINT),

• do not forget to link via ‘has for feedback’ relation, the control of the SBMC with the
SBMC status datapoint.

(2)

(1)

FIGURE 301: DEFINING SBMC FOR BAY

Configuration rules and checks

• if "SBMC SPS" is present, then "SBMC control SPC" must be present

• if "SBMC control SPC" is present, then "SBMC SPS" must be present

• if "SBMC control SPC" is present, then its attribute "bay mode dependency" must be
set to "No".

• If a "DPC" or "SPC" Datapoint has its attribute "SBMC mode dependency" set to
"Yes", then the "SBMC SPS" Datapoint must be present.

• If a "DPS" or "SPS" Datapoint has the attribute "SBMC dependant" of its profile set to
"Yes", then the "SBMC SPS" Datapoint must be present.
C264/EN AP/B30 Application

Page 262/396 MiCOM C264/C264C

6.1.4.4 Adding user function to bay

An addition of a bay user function is done under SCE via the “Object entry” area at bay level
by clicking on mouse’s right button.
For more details about user function usage and their configuration, refer to chapter 6.6
Defining electrical regulation by user function.

FBD user function

ISA GRAF user function

C0216ENa

FIGURE 302: ADDING USER FUNCTION TO BAY

6.1.5 Defining Module
This chapter deals with general module configuration. Configuring specific typed module is
described in following relevant chapter.
At ‘bay’ level, several ‘module’ objects can be implicitly or explicitly added. A module
corresponds generally to a substation electrical device.
To create explicitly a module:

• Add a typed one from object entry available at bay (1)

For implicit or explicit module:

• Update the module attributes (see following sub-chapters)

(1)

FIGURE 303: ADDING EXPLICITLY A TYPED MODULE

Application C264/EN AP/B30

MiCOM C264/C264C Page 263/396

When adding a module, some general attributes must be updated:

1. Short and long names of the module used for logging, alarms ...
2. ‘node reference’, used for electrical topology definition for ATCC function. For details
about ATCC configuration and this attribute, refer to chapter 6.5 Defining AVR built-in
function

(1)

(2)

FIGURE 304 : SETTING COMMON GENERAL ATTRIBUTES TO MODULE

Typed module features
Using typed module specialises module configuration. Hereafter are listed all typed modules
with their main configuration features:

• Capacitor, Inductor :
− Specific attribute ‘reactive power value’ (in MVA), used for ATCC regulation. For
details about ATCC configuration and this attribute, refer to chapter 6.5 Defining
AVR built-in function.
− Not lockable module

• Convertor, generator, motor:

− Not lockable module

• Transformer:
− Lockable module
− Supports Tap changer built-in function,
− Supports ATCC function needs. For details about ATCC configuration and this
attribute, refer to chapter 6.5 Defining AVR built-in function.

• Circuit-breaker module:
− Lockable module
− Supports synchrocheck and autorecloser built-in functions,
− May support withdrawing if exists

• Switchgear module
− Lockable module
− May support withdrawing if exists

• External line:
− Only support SPS and DPS attribution

• Generic module:
− Lockable module
− Used for general usage outside the scope of other previous typed modules
C264/EN AP/B30 Application

Page 264/396 MiCOM C264/C264C

6.1.5.1 Adding module generic datapoint

An addition of a module typed datapoint is done under SCE via the “Object entry” area at
module level by clicking on mouse’s right button. Here are listed generic datapoint (standard
usage) out of scope of the specific module functions:

• Group computation (see chapter 6.6.3 Defining a group),

• Locking module (see chapter 6.1.5.3 Defining a lockable module),

• Specific features and configuration of typed modules (see following chapters)

For more details about datapoints and their configuration, refer to chapter 5 DEFINING
DATAPOINT.

FIGURE 305: ADDING MODULE GENERIC DATAPOINT

(E.G. FOR GENERATOR MODULE)
6.1.5.2 Adding user function to module
An addition of a module user function is done under SCE via the “Object entry” area at
module level by clicking on mouse’s right button.
For more details about user function usage and their configuration, refer to chapter 6.6
Defining electrical regulation by user function.
Module does not support ISaGRAF function.

FBD user function

C0217ENa

FIGURE 306: ADDING USER FUNCTION TO MODULE

(E.G. FOR GENERATOR MODULE)
Application C264/EN AP/B30

MiCOM C264/C264C Page 265/396

6.1.5.3 Defining a lockable module

According to PACiS system, locking module is a system function running on the MiCOM
C264 Computer that manages the bay containing the module.
When a module is locked, any subsequent control acting on it, is refused. Locking is checked
during control sequence processing at MiCOM C264 Computer level (see chapter 5.1.9
Overview of control sequence processing).
At SCE level, only following types modules are lockable:

• Circuit-breaker,

• Switchgear,

• Transformer,

• Generic module.
To configure such a module as lockable:

• Add the pre-defined SPS datapoint ‘Lock SPS’ at module level (1) and configure it
(see chapter 5 DEFINING DATAPOINT),

• Add the pre-defined SPC datapoint ‘Lock control SPC’ at module level (2) and
configure it (see chapter 5 DEFINING DATAPOINT),

• Define the ‘Lock SPS’ as feedback of the ‘Lock control SPC’ by adding and filling ‘has
for feedback’ relation at the SPC level (see chapter 5.1.10.3 Defining SPC feedback).

(2)

(1)

FIGURE 307: DEFINING A LOCKABLE MODULE

(E.G. FOR GENERIC MODULE)
Lock SPS and Lock control SPC are datapoints fed and controlled directly by the MiCOM
C264 Computer that manages the module. They can not be wired.
Configuration rules and checks

• For “Lock control SPC“, the feedback to “Lock SPS“ is mandatory

6.1.5.4 Defining withdrawable circuit-breaker or switchgear
To define a withdrawable circuit-breaker or switchgear:

• add the pre-defined SPS ‘withdraw’ at module level

• configure it (see chapter 5 DEFINING DATAPOINT)

Withdraw information is useful for bay mimic animation at MiCOM C264 Computer LCD
level. For more details see chapter 7.3 Defining MiCOM C264 Computer bay mimic.
C264/EN AP/B30 Application

Page 266/396 MiCOM C264/C264C

(1)

FIGURE 308: DEFINING A WITHDRAWABLE MODULE

(E.G. FOR CIRCUIT BREAKER)
6.1.5.5 Defining circuit-breaker
This chapter deals with general circuit-breaker features and available associated input and
output datapoints at MiCOM C264 Computer level.
If the circuit-breaker is synchronised by internal or external synchrocheck, extra datapoints
exist. For more details refer to chapter 6.2 Defining Synchrocheck function.
General module features described in chapter 6.1.5 Defining Module are applicable to
circuit-breaker module and not reviewed here.
When adding a circuit-breaker module, the following specific general attribute must be
updated:
1. Circuit-breaker type:
Available values are:

− Single phase circuit-breaker, where the 3 phases can be managed independently

− Triple phase circuit-breaker, where the 3 phases can only be managed together.

− Other circuit-breaker: obsolete

(1)

obsolete

C0218ENa

FIGURE 309 : SETTING CIRCUIT-BREAKER TYPE

Application C264/EN AP/B30

MiCOM C264/C264C Page 267/396

The following tables give inputs and outputs circuit breaker’s features controlled by the
MiCOM C264 Computer for triple phase and single phase circuit-breaker. For each datapoint
its SCE identification is given by a number, referenced in the following figure.
When creating a circuit breaker module implicitly or explicitly (cf. chapter 6.1.4 Defining Bay),
the mandatory pre-defined DPS datapoint ‘computed switch position’ (20) is automatically
created.
To configure correctly a circuit-breaker module:

• Add the relevant datapoints, relatively to the following tables,

• configure them (see chapter 5 DEFINING DATAPOINT),

• do not forget to link via ‘has for feedback’ relation, the control(s) (1), (11) or (10) of the
breaker with the computed switch position (20) datapoint;

Triple phase circuit-breaker

OUTPUTS CB TYPE A OUTPUTS CB TYPE B (iv) INPUTS CB ALL TYPES

DEVICE (1) DPC control for open/close (11) SPC control for open of (8) DPS or (19) SPS physical
CONTROL of device device position of the device (1
phase)
(10) SPC control for close of
device (14) SPS (optional) phase not
together information
(20) system DPS the
feedback of the control (i)

DEVICE (9) SPC (optional) control of (9) SPC (optional) control of (15) SPS (optional) device
SELECTION device selection device selection selection position information
(HARDWARE)

Single phase circuit-breaker

OUTPUTS CB TYPE A OUTPUTS CB TYPE B (iv) INPUTS CB ALL TYPES

DEVICE (1) DPC control for open/close (2) DPC or (11) SPC control for (16) SPS or (5) DPS physical
CONTROL of device open phase A position of phase A
(3) DPC or (12) SPC control for (17) SPS or (6) DPS physical
open phase B (pulse) position of phase B

(4) DPC or (13) SPC control for (18) SPS or (7) DPS physical
open phase C position of phase C

(1) DPC control for close of (14) system SPS phase not
device together information (ii)
(20) system DPS: the
feedback of the control (iii)

DEVICE (9) SPC (optional) control of (9) SPC (optional) control of (15) SPS (optional) device
SELECTION device selection device selection selection position information
(HARDWARE)

(i) The computed double signal is equal to the physical status if the phase not together
status is equal to “false” else the computed signal is equal to “jammed”.
(ii) The computed “phases not together” is equal to “false” if all phases are in the same
position else it is equal to “true”.
(iii) The computed signal is equal to the phase A status if the phase not together status is
equal to “false” else the computed signal is equal to “jammed”.
(iv) Only the “DPC close “ is known by the other UCA2 devices :
- For open the device they send the “DPC close” with “open” request
- For close the device they send the “DPC close” with “close” request
C264/EN AP/B30 Application

Page 268/396 MiCOM C264/C264C

(1)
(2)
(3)
(4)

(5)
(6)
(7)
(8)

(9)
(10)
(11)
(12)
(13)

(14)
(15)
(16)
(17)

(18)
(19)

(21)

(20)

FIGURE 310: AVAILABLE PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER

Configuration rules and checks

• The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive.
None is mandatory

• If physical position of the device is given by an SPS (19), phase not together
information (14) is mandatory
Application C264/EN AP/B30

MiCOM C264/C264C Page 269/396

• Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}

If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then :
- in a set, if one Datapoint is present for a phase, then the two others must be present
as well.
- the Datapoints of the two sets (1) and (2) are mutually exclusive.
- the Datapoints of the two sets (3) and (4) are mutually exclusive.
- if the Datapoint "Switchgear pos." is present, but none of the three Datapoints
"Switch PhA pos", "Switch PhB pos", and "Switch PhC pos" then the SPS Datapoint
"Ph not together" is mandatory.

If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then :
- none of the datapoints referencing a phase (phA, phB or phC) is allowed.

• "Selection SPC" Datapoint must have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”
Control sequence of non-synchronised circuit breakers
Circuit breakers devices are managed in “direct execute mode” and in “SBO once mode”.
Refer to the generic description in chapter 5.1.9 Overview of control sequence processing.
Control sequence of synchronised circuit breakers
Refer to chapter 6.2 Defining Synchrocheck function.
6.1.5.6 Defining switchgear
This chapter deals with general switchgear features and available associated input and
output datapoints at MiCOM C264 Computer level.
General module features described in chapter 6.1.5 Defining Module are applicable to
switchgear module and not reviewed here.
When adding a switchgear module, the following specific general attribute must be updated:
1. Switchgear type:
Available values are:

− Busbar disconnector

− Disconnector

− Bypass disconnector

− Transfer busbar disconnector

− Earth switch

(1)

obsolete

C0219ENa

FIGURE 311 : SETTING SWITCHGEAR TYPE

C264/EN AP/B30 Application

Page 270/396 MiCOM C264/C264C

The following tables give inputs and outputs switchgear’s features controlled by the MiCOM
C264 Computer. For each datapoint its SCE identification is given by a number, referenced
in the following figure.
To configure correctly a switchgear module:

• Add the relevant datapoints, relatively to the following tables,

• configure them (see chapter 5 DEFINING DATAPOINT),

• do not forget to link via ‘has for feedback’ relation, the control (3) of the switchgear (if it
exists) with the switch position (1) or (5) datapoint;

Switchgear
OUTPUTS TYPE A INPUTS CB ALL TYPES

DEVICE (3) DPC control for open/close (1) DPS or (5) SPS physical
CONTROL of device position of the device (1 phase) (v)

DEVICE (2) SPC (optional) control of (4) SPS (optional) device selection
SELECTION device selection position information
(HARDWARE)

(1)

(2)
(3)

(4)
(5)

FIGURE 312: AVAILABLE PRE-DEFINED DATAPOINTS FOR SWITCHGEAR

Control sequence of switchgears
Switchgear devices are managed in “direct execute mode” and in “SBO once mode”. Refer
to the generic description in chapter 5.1.9 Overview of control sequence processing.
Application C264/EN AP/B30

MiCOM C264/C264C Page 271/396

6.1.5.7 Defining transformer

This chapter deals with general transformer features and available associated input and
output datapoints at MiCOM C264 Computer level.
General module features described in chapter 6.1.5 Defining Module are applicable to
transformer module and not reviewed here.
When adding implicitly a transformer module via transformer bay creation (refer to 6.1.4
Defining Bay), the following general attribute must be updated:
1. Transformer type:
Available values are:

− Double wound:
Double wound (or two winding transformer) is a transformer with galvanic isolation
between primary and secondary coil.
Tap Changer (with additional winding) is usually located at HV-neutral side for
economic reasons. Tapping-up (raise order) reduces primary winding and
increase LV tension.

− Auto transformer:
Auto transformer (or Auto-wound or single wound) is a transformer without
galvanic isolation between primary and secondary. Secondary coil follows primary
coil, (winding are serial).
Tap Changer (with tap of additional winding) is serial. Increasing tap position
(raise order) acts simultaneously on primary and secondary, it reduces
transformer ratio then voltage at LV side. So for this type of transformers the raise
order must be inverted (consider as low order)
2. Power value (from 1 to 300 MVA), useful for ATCC regulation (refer to chapter 6.5
Defining AVR built-in function)
3. Impedance, whose unit is a percent of value for S=100 MVA (from 0,01 to 24,99 by
step 0,01) , useful for ATCC regulation (refer to chapter 6.5 Defining AVR built-in
function)

(1)
(2)

(3)

FIGURE 313 : SETTING TRANSFORMER TYPE

Transformer is used for coupling two voltage levels. To respect SCE data modelling
electrical partitioning, this transformer must belong to a transformer bay arbitrary put in one
of both voltage levels (generally its primary). An extra relation must be set on transformer
refining to which voltage level its secondary (or primary) belongs.
To create such a relation:

• Add the correct relation at transformer level

• Fill the relation with the relevant voltage level

C264/EN AP/B30 Application

Page 272/396 MiCOM C264/C264C

(1)

FIGURE 314: COMPLETING PRIMARY/SECONDARY OF TRANSFORMER

When adding a transformer, some optional datapoints can be created at module level and
must be configured (see chapter 5 DEFINING DATAPOINT):
1. MCB position DPS:
used for AVR function (see chapter 6.5 Defining AVR built-in function), to give Mini
Circuit-Breaker position of associated tap-changer, via DPS datapoint
2. MCB position SPS
used for AVR function (see chapter 6.5 Defining AVR built-in function), to give Mini
Circuit-Breaker position of associated tap-changer, via SPS datapoint

(1)

(2)

FIGURE 315: TRANSFORMER OPTIONAL DATAPOINTS

When it exists, tap position of transformer is controlled by a specific built-in function ‘Tap
changer’ available at transformer module level. For details about transformer control via tap
changer function, refer to chapter 6.4 Defining Tap changer built-in function.
Application C264/EN AP/B30

MiCOM C264/C264C Page 273/396

6.2 Defining Synchrocheck function

6.2.1 Completing circuit-breaker definition for synchrocheck
The following tables give inputs and outputs circuit breaker’s features controlled by the
MiCOM C264 Computer for triple phase and single phase circuit-breaker, when it is
concerned by synchrocheck function. For each datapoint its SCE identification is given by a
number, referenced in the following figure or relevant to the synchrocheck configuration (for
datapoints (22), (23), (24) and (25)).
These tables are complements to those described in chapter 6.1.5.5 Defining circuit-breaker.
To configure correctly a circuit-breaker module with synchrocheck:

• Add the relevant datapoints, relatively to the following tables,

• Configure them (see chapter 5 DEFINING DATAPOINT),

• Do not forget to link via ‘has for feedback’ relation, the control(s) (1), (11) or (10) of the
breaker with the computed switch position (20) datapoint;

• Link the circuit-breaker with an existing synchrocheck function created at bay or

substation level. This link is done at synchrocheck level (for details see 6.2.4 Creating
a synchrocheck function). Up to 2 circuit breakers can be linked to the same internal
synchrocheck.

• Configure properly the synchrocheck function itself (for details see 6.2.4 Creating a
synchrocheck function)

Triple phase circuit-breaker with synchrocheck

OUTPUTS CB TYPE A OUTPUTS CB TYPE B (iv) INPUTS CB ALL TYPES

DEVICE CONTROL (1) DPC control for (11) SPC control for open (8) DPS or (19) SPS
open/close of device of device physical position of the
device (1 phase)
(23) SPC or (22) DPC (10) SPC control for close
control for close with of device (14) SPS (optional) phase
synchrocheck not together information
(23) SPC or (22) DPC
control for close with (20) system DPS the
synchrocheck feedback of the control (i)

DEVICE (9) SPC (optional) control of (9) SPC (optional) control of (15) SPS (optional) device
SELECTION device selection device selection selection position
information
(HARDWARE)
SYNCHROCHECK (24) SPC or (25) DPC (24) SPC or (25) DPC (26) SPS or (27) DPS
SET ON / SET OFF (optional) control of on/off (optional) control of on/off (optional) on/off
synchrocheck synchrocheck synchrocheck information
C264/EN AP/B30 Application

Page 274/396 MiCOM C264/C264C

Single phase circuit-breaker with synchrocheck

OUTPUTS CB TYPE A OUTPUTS CB TYPE B (iv) INPUTS CB ALL TYPES

DEVICE CONTROL (1) DPC control for (2) DPC or (11) SPC control (16) SPS or (5) DPS
open/close of device for open phase A physical position of phase A
(23) SPC or (22) DPC (3) DPC or (12) SPC control (17) SPS or (6) DPS
control for close with for open phase B (pulse) physical position of phase B
synchrocheck
(4) DPC or (13) SPC control (18) SPS or (7) DPS
for open phase C physical position of phase C

(1) DPC control for close of (14) system SPS phase not
device together information (ii)

(23) SPC or (22) DPC (20) system DPS: the

control for close with feedback of the control (iii)
synchrocheck

DEVICE (9) SPC (optional) control of (9) SPC (optional) control of (15) SPS (optional) device
SELECTION device selection device selection selection position
information
(HARDWARE)
SYNCHROCHECK (24) SPC or (25) DPC (24) SPC or (25) DPC (26) SPS or (27) DPS
SET ON / SET OFF (optional) control of on/off (optional) control of on/off (optional) on/off
synchrocheck synchrocheck synchrocheck information
(v)

(i) The computed double signal is equal to the physical status if the phase not together
status is equal to “false” else the computed signal is equal to “jammed”.
(ii) The computed “phases not together” is equal to “false” if all phases are in the same
position else it is equal to “true”.
(iii) The computed signal is equal to the phase A status if the phase not together status is
equal to “false” else the computed signal is equal to “jammed”.
(iv) Only the “DPC close “ is known by the other UCA2 devices :
- For open the device they send the “DPC close” with “open” request
- For close the device they send the “DPC close” with “close” request
(v) Wired SPC and SPS for external synchrocheck and system SPC and SPS for internal
synchrocheck. If is not configured the external synchrocheck module or the
synchrocheck automatism is considered always “set on”. DPC and DPS are used only
for manual synchrocheck.
Application C264/EN AP/B30

MiCOM C264/C264C Page 275/396

(1)
(2)
(3)
(4)
(22)
(5)
(6)
(7)
(8)

(9)
(10)
(11)
(12)
(13)

(23)

(14)
(15)
(16)
(17)

(18)
(19)

(21)

(20)

FIGURE 316: AVAILABLE PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER

WITH SYNCHROCHECK
Do not forget to define ‘Comp. Swit. Pos.’ mandatory SPS at circuit-breaker level as
feedback of Sync CB close SPC/DPC.
C264/EN AP/B30 Application

Page 276/396 MiCOM C264/C264C

Configuration rules and checks

• The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive.
None is mandatory

• If physical position of the device is given by an SPS (19), phase not together
information (14) is mandatory

• Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}

If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then :
- in a set, if one Datapoint is present for a phase, then the two others must be present
as well.
- the Datapoints of the two sets (1) and (2) are mutually exclusive.
- the Datapoints of the two sets (3) and (4) are mutually exclusive.
- if the Datapoint "Switchgear pos." is present, but none of the three Datapoints
"Switch PhA pos", "Switch PhB pos", and "Switch PhC pos" then the SPS Datapoint
"Ph not together" is mandatory.

If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then :
- none of the datapoints referencing a phase (phA, phB or phC) is allowed.

• A Circuit Breaker must be linked only once to a Synchrocheck function (relation "is
synchrocheck of").

• If a Circuit Breaker is linked to a Synchrocheck function (relation "is synchrocheck of"),

then its "Sync CB close" SPC Datapoint must be present.

• "Sync CB close" Datapoint of a "Circuit breaker" linked to a "Ext manual CS" or "Int
synchrocheck" synchrocheck must have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”

• "Sync CB close" Datapoint of a "Circuit breaker" linked to a "Ext auto CS"

synchrocheck must have its profile attribute “SBO mode” set to " SBO Operate Once”
“Open” control sequence of synchronised circuit breakers
This sequence remains identical to the non-synchronised circuit-breaker (refer to chapter
6.1.5.5 Defining circuit-breaker).
“Close” control sequence of synchronised circuit breakers
This sequence is different according to the configuration the synchrocheck type:

• External synchrocheck:
The closure of the device is assumed by an external synchrocheck module

• Internal synchrocheck:
The closure of the device is assumed by an internal synchrocheck automatism in the
MiCOM C264 Computer
Close control sequence can be configured with:

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

• Automatic set on
of the external synchrocheck module or internal synchrocheck automatism
Furthermore, waiting closes the CB by the external module the initiator of the request can:

• Cancel the request

• Close the device by forcing request

Application C264/EN AP/B30

MiCOM C264/C264C Page 277/396

6.2.2 External synchrocheck behaviour

6.2.2.1 Close CB by external synchrocheck with automatic set on
The following shame shows a “close” control for a device in which the external synchrocheck
module is set on automatically by the MiCOM C264 Computer

SPC close with SPC Select device

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

OI SPC Close with

synchrocheck
or

GATE
WAY

DPC open/Close
device

select close

Execute close (x)sequences order

force close
C0220ENa

FIGURE 317: CLOSING BREAKER BY EXTERNAL SYNCHROCHECK WITH AUTOMATIC SET ON

The “close” control sequence performed on the MiCOM MiCOM C264 Computer is done as
follow:
Selection phase:
1. Set on synchrocheck module (if the control is configured)
2. Verify synchrocheck on/off information associated to the output (if is configured)
3. Close device selection output to select the device(if is configured)
4. Verify selection device input information associated to the output (if is configured)
5. Wait the execution request or timeout selection
In case of fail to one of these operations the controls sequence is stopped with a negative
acknowledgement
Execution phase:
1. Close the device using synchrocheck output control
2. Verify the device position become close in the given delay.
3. Set off synchrocheck module if it previously set on
4. Deselect the device if it previously selected
The follow chronogram shows a successful control sequence ”close with synchrocheck”.
C264/EN AP/B30 Application

Page 278/396 MiCOM C264/C264C

SPC ON/ OFFt Sync

SPS ON/OFF Sync

SPC select

SPS select

SPC sync close

DPC open/close
device

DPS open

close

Feedback Feedback Feedback for DO sync close

Delay Delay Selection timeOut

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

1 2 3 4 5

1 selection request 3 execution request 5 End of control

C0221ENa

FIGURE 318: SUCESSFUL CLOSING BREAKER BY EXTERNAL SYNCHROCHECK

WITH AUTOMATIC SET ON
The follow chronogram shows an abnormal termination of control sequence ”close with
synchrocheck”. The device has not taken the expected position “close” in the given delay.
The control sequence is aborted with negative acknowledgement, deselecting previously
synchrocheck and device.

SPC ON/OFF Sync

SPS ON/OFF Sync

SPC select

SPS select

SPC sync close

DPC open/close
device

DPS open

close

Feedback Feedback Feedback for DO sync close

Delay Delay Selection timeOut

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

1 2 3 4 5

1 selection request 3 execution request » 5 End of control

C0222ENa

FIGURE 319: UNSUCESSFUL CLOSING BREAKER BY EXTERNAL SYNCHROCHECK

WITH AUTOMATIC SET ON
Application C264/EN AP/B30

MiCOM C264/C264C Page 279/396

6.2.2.2 Close CB by external synchrocheck with manual set on

By configuration the “close” control of the device may be done in two or three control
sequences:
Two sequences:
1. a “Direct Execute” sequence to put in service the external synchrocheck module
2. a SBO once sequence to close the CB by the synchrocheck module and put out of
service the synchrocheck module.
Three sequences:
1. a “direct execute” sequence to put in service the external synchrocheck module
2. a SBO once sequence to close the CB by the synchrocheck module
3. a “direct execute” sequence to put out service the external synchrocheck module.
The following shame shows a close control request in which the external synchrocheck
module is managed manually from the OI or gateway.

DPC open/close
device SPC Select device
C26X
CIRCUIT
(2) SPC/DPC ON/OF BREAKER
(3) synchrocheck
(4) Synchro
Check
(1)
Module
OI SPC/DPC “SET SPC/DPC Close
or ON” synchrocheck with synchrochec
GATE
WAY
(5)
SPC/DPC “SET
OFF”synchrocheck
(optional)
DPC open/Close
device
Direct execute The external synchrocheck module is set off automatically at
end of the SBO sequence (if it is configured)
select close

Execute close
(x) sequences order
force close C0223ENa

FIGURE 320: CLOSING BREAKER BY EXTERNAL SYNCHROCHECK WITH MANUAL SET ON

First sequence (DIRECT EXECUTE): Set on the external synchrocheck module:
1. close “set on/setoff” output control of the synchrocheck module
2. verify that the synchrocheck module is set (if on/off synchrocheck input information is
configured)
In case of fail to one of these operation the sequence ends with a negative
acknowledgement
Second sequence (SBO ONCE): close the device with synchrocheck”
Selection phase:
1. Close device selection output to select the device(if is configured)
2. Verify selection device input information associated to the output (if is configured)
3. Wait the execution request or timeout selection
4. In case of fail to one of these operations the controls sequence is stopped with a
negative acknowledgement
C264/EN AP/B30 Application

Page 280/396 MiCOM C264/C264C

Execution phase:
1. Close the device via the “close with synchrocheck” control
2. Verify the device position become close in the given delay.
3. Set off the synchrocheck module if is configured to be set off automatically
4. Deselect the device if it previously selected
Third sequence (DIRECT EXECUTE): set off the external synchrocheck module
This sequence takes place only if the setting off of the synchrocheck module is configured
“manual”
1. open “set on/setoff” output control of the synchrocheck module
2. verify that the synchrocheck module is set on(if on/off synchrocheck input information
is configured)
The follow chronogram shows a successful control sequence ”close with synchrocheck”
performed in three sequences. In case of automatic “setting off” of the synchrocheck module
the chronogram remain identical. It is performed at the end of the SBO sequence.

SPC ON/OFF Sync

SPS ON/OFF Sync

SPC select
device

SPSselect device

SPC sync close

DPC open/close
device

DPS open

close

Feedback Feedback Feedback for DO sync close

Delay Delay Selection timeOut

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

3
1 2 4 5 6

1 DE request set on 3 selection request : close 4 execution request 5 DE request set 6 End of control
synchrocheck the device off synchrocheck
C0224ENa

FIGURE 321: SUCESSFUL CLOSING BREAKER BY EXTERNAL SYNCHROCHECK

WITH MANUAL SET ON
NOTE: During SBO sequence after step 5 the initiator of the request may
force the closing of the device.
Application C264/EN AP/B30

MiCOM C264/C264C Page 281/396

6.2.2.3 Close synchronised circuit breakers with forcing

The follow chronogram shows controls sequence ”close with synchrocheck” with “forcing
close request”. The SBO sequence is performed in the same way whether the synchrocheck
module is set on manually or automatically.
Awaiting the device be closed by the external synchrocheck module, the initiator of the
request force to “close without synchrocheck”

SPC select Sync

(optional)

SPS select Sync

(optional)

SPC select
(optional)

SPS select
(optional)

SPC sync close

Forcing on DPC
close : DPC close
is set

SPS open

close

Feedback Delay Feedback Selection Timeout Feedback for DO sync close Feedback
Delay Delay

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

1 2 3 4 5 6

3 execution request 4 synchrocheck bypass 5 End of control

1 selection request
C0225ENa

FIGURE 322: CLOSING EXTERNAL SYNCHRONISED BREAKER WITH FORCING

6.2.2.4 Cancel Close CB with external synchrocheck
Awaiting close the device (0 to 60 mn) by the external synchrocheck module, the initiator of
the close request may cancel this one by a “cancel request”.
The following chronogram shows a cancel close request awaiting close the device by the
external synchrocheck module.

SPCselect Sync

SPSselect Sync

SPC select

SPS select

SPC sync close

DPS open

close

Feedback Feedback FeedBack Delay

Delay Delay Selection timeOut

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

3 4 5 6
1 2

1 selection request 3 execution request 5 End of control

4 Operator «CANCEL »
C0226ENa

FIGURE 323: CANCEL CLOSE OF SYNCHRONISED BREAKER

C264/EN AP/B30 Application

Page 282/396 MiCOM C264/C264C

6.2.3 Internal synchrocheck behaviour

On this configuration synchrocheck is assumed by an internal MiCOM C264 Computer
automatism, which proceed to the synchrocheck voltage calculations and gives or not the
authorisation to close the device.
The PACiS 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 measures come from VT acquisition. So a TIU board
is mandatory in the MiCOM C264 Computer in case of internal synchrocheck usage. For
details about TMU200 board creation, refer to chapter 4.4.1 Adding boards and 4.4.2.3
Setting specific attributes of TMU200 board.
The controls sequence remain similar with the external synchrocheck instead of the setting
on/off of the synchrocheck and close with synchrocheck output control which are not exist on
this configuration
6.2.3.1 Automation description of internal synchrocheck
For each parameter of the internal synchrocheck, its SCE identification is given by (param
<i>), referenced in Figure 338 : SETTING INTERNAL SYNCHROCHECK SETTINGS of the
chapter 6.2.4.1 Setting default settings of internal synchrocheck.
Principle
The synchrocheck function can work in the following schemes :

Operator manual Operator Auto-recloser

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

• Vline and Vbusbar for network coupling

• Vline and Vbusbar for network locking

• Vline and not(Vbusbar)

• not(Vline) and Vbusbar

• not(Vline) and not(Vbusbar)

with Vline and Vbusbar TRUE if the measured voltage is above the threshold V> (param 15 and
param 17), and not(Vline) and not(Vbusbar) TRUE if the measured voltage is below the threshold
V< (param 16 and param 18). These threshold are given in % of the nominal voltage value,
updated at TMU200 board level (refer to chapter 4.4.2.3 Setting specific attributes of
TMU200 board).
The selection of the voltage control is made during the configuration phase.
Application C264/EN AP/B30

MiCOM C264/C264C Page 283/396

Schemes using Vline and not(Vbusbar) / not(Vline) and Vbusbar voltage controls
In case of the absence of one of the two voltages, at the end of a settable delay T2 (param
2), the authorisation of closing is given :

Vline
T2 0
& Closing authorization
Not(Vbusbar)

C0227ENa

FIGURE 324 : VLINE AND NOT(VBUSBAR) VOLTAGE CONTROL

Vbusbar
T2 0
& Closing authorization
Not(Vline)
C0228ENa

FIGURE 325 : NOT(VLINE) AND VBUSBAR VOLTAGE CONTROL

If, during the T2 delay time, one of the 2 criteria is lost, the timer is reinitialised and is
launched again on reappearance of all the criteria.
Schemes using not(Vline) or not(Vbusbar)voltage control
In case of the absence of both voltages, at the end of a settable delay T3 (param 1), the
authorisation of closing is given :

Not(Vline)
T3 0
& Closing authorization
Not(Vbusbar)
C0229ENa

FIGURE 326 : NOT(VLINE) AND NOT(VBUSBAR) VOLTAGE CONTROL

If, during the T3 delay time, one of the 2 criteria is lost, the timer is reinitialised and is
launched again on reappearance of all the criteria.
Schemes using Vline and Vbusbar voltage control
Locking scheme
The closing authorisation will be given if the following conditions are met :

• Presence of both voltages , confirmed after a given delay (param 3) AND

• The difference in amplitude (algebraic) between the two voltages (∆V) is lower than
the seized threshold (Evect) (param 5) AND

• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 6) and
Fmax (param 7) are the extreme acceptable frequencies AND

• The difference between the two frequencies (∆F) is lower than the seized threshold
(Efreq) (param 8) AND

• The phase difference between the two voltages (∆ϕ) is lower than the seized threshold
(Ephase) (param 9).
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorise the CB closing.
If during the delay time T1 one of these criteria is lost, T1 is reinitialised and is relaunched on
reappearance of all the criteria.
C264/EN AP/B30 Application

Page 284/396 MiCOM C264/C264C

T1 depends on the way circuit breaker is controlled (manual closure, manual synchronised
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param
30), (param 35).

Fmin < Fline < Fmax

Fmin < Fbusbar < Fmax
Vline
Vbusbar
& T1 0 Reclosing authorization
∆F <Efreq
∆ϕ < Ephase
∆V < Evect
C0230ENa

FIGURE 327: LOCKING SCHEME

Coupling scheme

In the coupling scheme, the CB can be closed only when the ∆ϕ is equal to 0.
But, in order to authorise the closing, it is first necessary to have the following conditions
met :

• Presence of both voltages AND

• The difference in amplitude (algebraic) between the two voltages (∆V) is lower than
the seized threshold (Evect) (param 10) AND

• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 11) and
Fmax (param 12) are the extreme acceptable frequencies AND

• The difference between the two frequencies (∆F) is lower than the seized threshold
(Efreq) (param 13)
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorise the CB closing.
If during the delay time T1 one of these criteria is lost, T1 is reinitialised and is relaunched on
reappearance of all the criteria.
T1 depends on the way circuit breaker is controlled (manual closure, manual synchronised
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param
30), (param 35).

Fmin < Fline < Fmax

Fmin < Fbusbar < Fmax
Vline T1 0 Autorisation to check ∆ϕ
&
Vbusbar

∆F <Efreq
∆V < Evect
C0231ENa

FIGURE 328: COUPLING SCHEME

Then, since a CB has a response time, it is necessary to wait a known ∆ϕ in order to

anticipate the response time and to close the breaker with a ∆ϕ equal to 0.

Therefore, the closing authorisation will be sent when ∆ϕ = ∆F*360*Ta ± ∆(∆ϕ) where Ta
(param 4) is the anticipation time or response time of the circuit breaker and ∆(∆ϕ) (param
14) is the acceptable mistake on ∆ϕ. There is a delay for such a coupling given in
configuration (param 24).
Application C264/EN AP/B30

MiCOM C264/C264C Page 285/396

6.2.3.2 Close CB with internal synchrocheck with automatic set on

The following sequence describes a “close” request of circuit breaker with internal
synchrocheck in SBO once mode. Synchrocheck automatism is set on automatically.
In direct execute mode the processing remain similar without selection of the device.

SPC/DPC system
ON/OFF fonction
synchorcheck
SPC/DPC close
with synchrocheck SPC Select device
C26X
CIRCUIT
(1) BREAKER
(2) Fonction
(3) Synchro
Check

OI
or SPC/ DPC system
GATE Close with
WAY

DPC open/Close
device

select close
(x) ordre séquences
Execute close

force close C0232ENa

FIGURE 329: CLOSING BREAKER BY INTERNAL SYNCHROCHECK WITH AUTOMATIC SET ON

Selection phase:
1. Close device selection output to select the device (if is configured)
2. Verify selection device input information associated to the output (if is configured)
3. Wait the execution close request or timeout selection
In case of fail to one of these operations, the device is deselected and the controls sequence
is aborted with a negative acknowledgement.
Execution phase:
1. Active the associated internal synchrocheck automatism for authorisation to close the
device
2. Wait authorisation to close

− Case 1: Synchrocheck automatism respond OK before the time-out of the given

delay

⇒ Close the device

⇒ Deselect the device (if it was previously selected)

⇒ Send a positive acknowledgement

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

delay

⇒ Deselect the device (if it was previously selected)

⇒ Send a negative acknowledgement

C264/EN AP/B30 Application

Page 286/396 MiCOM C264/C264C

− Case 3: time-out of the given delay without synchrocheck response

⇒ stop the synchrocheck automatism

⇒ Deselect the device (if it was previously selected)

⇒ Send a negative acknowledgement

− Case 4: reception of cancel request awaiting synchrocheck response

⇒ stop the synchrocheck automatism

⇒ Deselect the device (if it was previously selected)

⇒ Send a negative acknowledgement

The follow chronogram shows a successful control sequence ”close with internal
synchrocheck”.

SPC select

SPS select

Close/open
Device control

DPS open

close

Feedback Feedback feedback Delay

Delay Delay Selection time-out

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

1 2 3 4 5

1 selection close request 3 execution request 5 End of control

C0233ENa

FIGURE 330: SUCCESSFUL CLOSING BREAKER BY INTERNAL SYNCHROCHECK

WITH AUTOMATIC SET ON
The follow chronogram shows an abnormal termination of control sequence ”close with
internal synchrocheck” in case of time-out.

SPC select

SPS select

Close/open
Device control

DPS open

close

Feedback Feedback FeedBack Delay

Delay Delay Selection timeOut

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

1 2 3 4 5

5 End of control
1 selection close request 3 execution request C0234ENa

FIGURE 331: UNSUCCESSFUL CLOSING BREAKER BY INTERNAL SYNCHROCHECK

WITH AUTOMATIC SET ON
Application C264/EN AP/B30

MiCOM C264/C264C Page 287/396

6.2.3.3 Close CB with internal synchrocheck with manual set on

The following sequence describes a “close” request of circuit breaker with internal
synchrocheck in SBO once mode. Synchrocheck automatism is set on by a separate direct
execute control.

SPC/ DPC Close

with synchrocheck

SPC open/close SPC Select device

device C26X
CIRCUIT
(2) BREAKER
(3) Synchro
(4) Check
Module

OI SPC/DPC set on
synchrocheck
or (1)

GATE
WAY
(5)

SPC/DPC set off

synchrocheck DPC open/Close
device
Direct execute
The external synchrocheck module is set off automatically at the
select close end of the SBO sequence (ifisitconfigured)
Execute close
(x) sequences order
force close C0235ENa

FIGURE 332: CLOSING BREAKER BY INTERNAL SYNCHROCHECK WITH MANUAL SET ON

First sequence (DIRECT EXECUTE): Set on the internal synchrocheck automatism
1. Set on synchrocheck automatism for the device
2. set system input “on/off synchrocheck” (if its is configured)
Second sequence (SBO ONCE): close the device with synchrocheck
Selection phase:
1. Close device selection output to select the device(if is configured)
2. Verify selection device input information associated to the output (if is configured)
3. Wait the execution request or timeout selection
4. In case of fail to one of these operations the controls sequence is stopped with a
negative acknowledgement
Execution phase:
1. Ask to the internal automatism to close the device
2. Verify the device position become close in the given delay.
3. Set off the synchrocheck automatism if is configured to be set off automatically
4. Deselect the device if it previously selected
Third sequence (DIRECT EXECUTE): set off the internal synchrocheck automatism
This sequence takes place only if the setting off of the synchrocheck automatism is
configured “manual”
1. set off synchrocheck automatism
2. reset system input “on/off synchrocheck” (if its is configured)
NOTE: During SBO sequence after step 5 the initiator of the request may
force the closing of the device.
C264/EN AP/B30 Application

Page 288/396 MiCOM C264/C264C

6.2.3.4 Close CB with internal synchrocheck with forcing

Awaiting authorisation from the internal synchrocheck for closing the device, the initiator of
the request may force the closing.
After time-out of the given delay without synchrocheck response
1. stop the synchrocheck automatism
2. close the device
3. Deselect the device (if it was previously selected)
4. Send a positive acknowledgement

SPC select

SPS select

Close via output

control

DPS open

close

Feedback Feedback FeedBack Delay

Delay Delay Selection timeOut

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

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

C0236ENa

FIGURE 333: CLOSING INTERNAL SYNCHRONISED BREAKER WITH FORCING

6.2.4 Creating a synchrocheck function
Synchrocheck function can be created at several levels of the electrical topology:

• Substation level, in case of the synchrocheck function is shared by several breakers,

• Bay level, in case of the synchrocheck function is dedicated to a particular breaker of

the bay, or shared by 2 breakers in two different bays managed by the same
computer.
An addition of a synchrocheck is done under SCE via the “Object entry” area at substation or
bay level by clicking on mouse’s right button.
For more details about bay creation, refer to chapter 6.1.4 Defining Bay.
Several typed synchrochecks exist:
1. External automatic synchrocheck
2. External manual synchrocheck
3. Internal synchrocheck
At substation level, only ‘external manual synchrocheck’ is available.
Application C264/EN AP/B30

MiCOM C264/C264C Page 289/396

Only following typed bays allows synchrocheck creation:

• Busbar,

• Bus coupler,

• Bus section,

• Feeder,

• Transformer,

• Generic bay.

(1)

(2)

(3)

FIGURE 334: ADDING SYNCHROCHECK AT BAY LEVEL (E.G. FOR FEEDER)

(2)

FIGURE 335: ADDING SYNCHROCHECK AT SUBSTATION LEVEL

Once added, synchrocheck general features must be set at SCE level:
1. Fill the relation ‘is synchrocheck of’, giving which circuit-breaker module is concerned
by the function.
For substation synchrocheck, several relation ‘is synchrocheck of’ can be added and
filled for all concerned breakers by the same synchrocheck.
For bay synchrocheck, 2 relations ‘is synchrocheck of’ can be filled for breakers of 2
different bays. Nevertheless, these bays must be managed by the same computer,
and the same synchrocheck parameters will be used for the 2 breakers closure.
2. Short and long names of the synchrocheck used for logging, alarms ...
3. automatic out of service (Yes/No):
defines if the synchrocheck is set off manually (No) or automatically (Yes). When
manually set off, an extra sequence is done by MiCOM C264 Computer (see previous
chapters).
For automatic synchrocheck, this attribute is fixed to ‘Yes’.
C264/EN AP/B30 Application

Page 290/396 MiCOM C264/C264C

4. Running time (from 0 to 60s):

this attribute appears in case of automatic out of service.
It corresponds to a latency time before setting out of service the synchrocheck after
successful or unsuccessful closure of the synchronised breaker.

(1)

(2)

(3)
(4)

FIGURE 336: SETTING SYNCHROCHECK GENERAL FEATURES

(E.G. FOR EXTERNAL MANUAL SYNCHROCHECK AT BAY LEVEL)
In case of internal synchrocheck, extra configuration information must be set (see chapter
6.2.4.1 Setting default settings of internal synchrocheck).
When adding a synchrocheck, the following mandatory datapoints is automatically created at
function level and must be configured (see chapter 5 DEFINING DATAPOINT):
1. Accept forcing:
SPS datapoint, given the authorisation to force synchrocheck.
It is a system datapoint: it can not be wired and is managed by the MiCOM C264
Computer running synchrocheck sequence.
Any automation or operator interface asking for a synchrocheck forcing, should be
client of this datapoint and test its status before forcing. So, proper UCA2
configuration must be done for all clients (MiCOM C264 Computer, operator interface)
to insure that feature. For details about UCA2 configuration, refer to chapter 4.5
Networking MiCOM C264 Computer on the station-bus network.

(1)

FIGURE 337: ACCEPT FORCING MANDATORY DATAPOINT FOR SYNCHROCHECK

(E.G. FOR EXTERNAL MANUAL SYNCHROCHECK AT BAY LEVEL)
Application C264/EN AP/B30

MiCOM C264/C264C Page 291/396

6.2.4.1 Setting default settings of internal synchrocheck

Default settings of internal synchrocheck are relevant to parameters of automation
description (see chapter 6.2.3.1 Automation description of internal synchrocheck)
When adding an internal synchrocheck, the following specific attributes must be updated:
General attributes
(param 1) absence deltas test duration (ms)
(param 2) presence test duration (ms)
(param 3) presence deltas test duration (ms)
(param 4) close time of the Circuit Breaker (ms)
Acceptance Conditions
(param 5) voltage delta threshold for locking (%)
(param 6) minimum frequency for locking (Hz)
(param 7) maximum frequency for locking (Hz)
(param 8) frequency delta threshold for locking (Hz)
(param 9) phase delta threshold for locking (°)
(param 10) voltage delta threshold for coupling (%)
(param 11) minimum frequency for coupling (Hz)
(param 12) maximum frequency for coupling (Hz)
(param 13) frequency delta threshold for coupling (Hz)
(param 14) phase delta threshold for coupling (°)
Voltage presence conditions
(param 15) line voltage over threshold (%)
(param 16) line voltage under threshold (%)
(param 17) bus voltage over threshold (%)
(param 18) bus voltage under threshold (%)
Used control schemes
(param 19) manual synchro close : coupling
(param 20) manual synchro close : locking
(param 21) manual synchro close : Line Dead and Bus Live
(param 22) manual synchro close : Line Live and Bus Dead
(param 23) manual synchro close : Line Dead and Bus Dead
(param 24) manual synchro close delay for coupling (s)
(param 25) manual synchro close delay (ms)
(param 26) manual close : locking
(param 27) manual close : Line Dead and Bus Live
(param 28) manual close : Line Live and Bus Dead
(param 29) manual close : Line Dead and Bus Dead
(param 30) manual close delay (ms)
(param 31) automatic close : locking
(param 32) automatic close : Line Dead and Bus Live
(param 33) automatic close : Line Live and Bus Dead
(param 34) automatic close : Line Dead and Bus Dead
(param 35) automatic close delay (ms)
C264/EN AP/B30 Application

Page 292/396 MiCOM C264/C264C

(param 1)

(param 2)
(param 3)

(param 4)

(param 5)
(param 6)
(param 7)
(param 8)
(param 9)
(param 10)
(param 11)
(param 12)
(param 13)
(param 14)

(param 15)
(param 16)
(param 17)
(param 18)

(param 19)
(param 20)
(param 21)
(param 22)
(param 23)
(param 24)
(param 25)
(param 26)
(param 27)
(param 28)
(param 29)
(param 30)
(param 31)
(param 32)
(param 33)
(param 34)
(param 35)
C0237ENa

FIGURE 338 : SETTING INTERNAL SYNCHROCHECK SETTINGS

Application C264/EN AP/B30

MiCOM C264/C264C Page 293/396

When adding an internal synchrocheck, some mandatory system datapoints are

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

(1)
(2)

(3)
(4)

(5)
(6)
(7)

FIGURE 339: INTERNAL SYNCHROCHECK MANDATORY DATAPOINTS

C264/EN AP/B30 Application

Page 294/396 MiCOM C264/C264C

6.2.4.2 Adding synchrocheck specific datapoints

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

(1)
(2)

(3)
(4)

FIGURE 340: SYNCHROCHECK OPTIONAL DATAPOINTS

Configuration rules and checks

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

are mutually exclusive and some must be wired. Here, the term "wired" means that the
datapoint must be linked to a digital/analog channel of a MiCOM C264 Computer, or
linked to an IED address

Substation
Ext manual CS
on/off ctrl DPC
mutually exclusive + wired
on/off ctrl SPC
on/off DPS
on/off SPS mutually exclusive

Feeder
Ext auto CS
on/off ctrl DPC
on/off ctrl SPC mutually exclusive
on/off DPS
on/off SPS mutually exclusive

Ext manual CS
on/off ctrl DPC mutually exclusive + wired
on/off ctrl SPC
on/off DPS
on/off SPS mutually exclusive

(A) automatic out of service - Yes

Int synchrocheck
on/off ctrl DPC - No
mutually exclusive
on/off ctrl SPC
on/off SPS
S0280ENa

• For a "Int synchrocheck" function, having its "automatic out of service" attribute set to
the "Yes" value, the "on/off ctrl DPC" or "on/off ctrl SPC" Datapoint must be present.

• "on/off ctrl DPC" or "on/off ctrl SPC" Datapoint of "Int synchrocheck" synchrocheck
must have its profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute
with SBO popup”
Application C264/EN AP/B30

MiCOM C264/C264C Page 295/396

6.3 Defining Auto-recloser built-in function

6.3.1 Auto-recloser behaviour
80-90% of faults on the electrical network are transient. Such faults are lightning or insulator
flashover. When a fault occurs, the Circuit Breaker is tripped in order to eliminate it. The
auto-recloser function is then used to close the circuit breaker after a set time during which
the fault disappears by itself (this duration is called cycle temporisation and defined in
database during the configuration phase) and therefore to decrease the time of unavailability
of it.
But, as permanent fault can occur, an auto-recloser scheme has to be provided in order to
allow the elimination of a transient fault by a open / close sequence (auto-reclosing cycle)
and the elimination of permanent fault by, after a defined number of auto-reclosing cycle (4
cycles maximum), leaving the circuit breaker in the open state by closing the trip relay.
A transient fault, such as an insulator flash-over, is one which is cleared by immediate
tripping of one or more circuit-breakers to isolate the fault, and which does not recur when
the line is re-energized. Lightning is the most common cause of transient faults.
This means that in the majority of fault incidents, if the faulty line is immediately tripped out,
and time is allowed for the arc to de-ionize, reclosure of the CB will result in the line being
successfully re-energized.
Auto-recloser (AR) schemes are implemented to carry out this duty automatically.
C264/EN AP/B30 Application

Page 296/396 MiCOM C264/C264C

The general diagram of the auto-recloser function is :

Auto-recloser out
of service

In Service request

Auto-recloser in
service

TRIP /TRIP_1P_X

3 phases
no 1 phase
CB_HEALTHY Analysis of the CB_HEALTHY no
Cycle n˚=1
= SET ? received trip = SET ?

yes yes
Waiting CB Waiting CB
opening opening

End of 150 ms timer End of 150 ms

CB open timer CB open
AR locked AR locked
Launch cycle timer Launch cycle timer
(for first single- (for 3-phases cycle)
phase cycle)

TRIP
TRIP_1P_X always set
End of
End of TRIP always set
timer
timer AR locked
AR locked
AR_BLOCKING no
AR_BLOCKING
no = RESET ?
= RESET ?
yes
yes
Closing the CB
Closing the CB

CB closed TRIP New CB

TRIP closed

Launch Cycle = cycle +1

recovering timer

Launch
recovering timer
End of TRIP
timer
Cycle n˚=2
TRIP End of
timer

no
Last cycle?

yes

AR locked
C0137ENa

FIGURE 341 : AUTO-RECLOSER DIAGRAM

In Service / Out of service
The auto-recloser function can be in or out of service due to an operator control (through the
station bus, the MiCOM C264 Computer local HMI or a BI).
If the auto-recloser is out of service, no cycle is authorised.
If an out of service request is received during an auto-reclosing cycle, the cycle is
immediately stopped.
Application C264/EN AP/B30

MiCOM C264/C264C Page 297/396

Analysis of the received trip

This analysis allows to detect the type of auto-recloser cycle, which can be :

• the first single-phase cycle

• the first 3-phases fast cycle

• the second 3-phases slow cycle

• the third 3-phases slow cycle

• the fourth 3-phases slow cycle

This detection is done using :

• the current cycle number

• the TRIP_1P_X or TRIP signal sent by the protection relay (single-phase trip / 3-
phases trip)

• the configured auto-recloser cycles

During this phase, if the CB_HEALTHY signal is not in the SET state, the cycle will be not
authorised and the automation will be re-initialised to wait the first cycle. The CB_HEALTHY
BI is optional : if it doesn’t exist, no check is done.
Waiting CB opening
As soon as the trip as been detected, a 150 ms timer is launched to wait the circuit breaker
opening.
For a 3 single poles CB :

• If the CB position is given on a per pole basis :

− In a single phase cycle, only one phase position is awaited in the OPEN state
(CB_STATE_1P_X)

− In a 3-phases cycle, each one phase positions is awaited in the OPEN state

• If the CB position is given globally :

− In a single phase cycle, the position (CB_STATE) is awaited in the MOTION00

state

− In a 3-phases cycle, the position (CB_STATE) is awaited in the OPEN state

For a triple poles CB :

• Whatever was the cycle, the 3 phase position is awaited in the OPEN state
(CB_STATE)
For a 3-phases cycle, the DO “AR_TRIP-3P” is closed (if configured) as soon as the CB is
detected as open.
The auto-recloser function is locked if the CB is not opened at the end of the timer.
Launch cycle timer
A soon as the CB is detected as open, the timer associated to the current auto-recloser
phase is launched.
During the single-phase cycle, the trip signal must disappear : if not, the auto-recloser
function will be locked. Furthermore, a 3-phases trip could appear. In this case, the current
cycle is stopped and the second 3-phases slow cycle is launched.
C264/EN AP/B30 Application

Page 298/396 MiCOM C264/C264C

Closing the CB
At the end of the cycle timer, the AR_BLOCKING BI is tested : if it is in RESET state, a close
order is sent to the Circuit Breaker. Note that, if present, the synchrocheck function is used
to control the breaker during the second, third and fourth 3-phases slow cycles. The use of
the synchrocheck function during the first 3-phases fast cycle is configurable.
If the AR_BLOCKING BI is in an other state, the automation is re-initialised to wait the first
cycle.
Launch recovering timer
As soon as all concerned CB phases are closed, the Reclaimc recovering timer is launched.
If the CB remains closed during the timer, the reclosing is considered to be successful and
the cycle number is set to 0. The “AR_STATE” signal is set at AR_RECLAIMC state during
this timer.
If a new trip occurs during the timer, the next configured cycle is launched. If the trip occurs
during the last cycle, the auto-recloser is locked.
Particular treatments
Reclaim time on manual close
If the CB becomes closed (through an external action) during an auto-recloser cycle, the
Reclaimmc timer is launched during which the auto-recloser function is inhibited and the
“AR_STATE” signal is set at the AR_RECLAIMMC state.
CB closing failure
If the CB closing order fails, due to DO hardware failure, interlocking scheme, or
synchrocheck inhibition, the AR_FAIL signal is set.
This SI is reset as soon as the CB is closed.
Lock of the auto-recloser
The conditions that lead to an auto-recloser locking are :

• A trip during the last auto-recloser cycle (in this case, the AR_STATE signal is set at
the AR_BAR_SHOTS state)
• A lock signal through the AR_LOCK Binary Input at the SET state
• Trip BI state is Invalid (this BI cannot be suppressed, forced or substitued)
• CB position BI(s) state is (are) Invalid
• The Trip BI is always set at the end of the cycle timer
• There is no pole discordance at the end of the single-phase cycle (i.e. the three
phases are opened)
• 2 phases are in an opened state at the end of the single-phase cycle without 3-phases
trip signal
• The CB is not opened at the end of the 150 ms timer
The AR_STATE signal is set at the AR_BAR_LOCK state if the auto-recloser function is
locked, and the cycle counter is set to 0.
There is 2 configurable methods to unlock the function. These methods are selected during
the configuration phase and can be used separately or together :

• a manual closing of a circuit breaker : in this case, the Reclaimmc timer is launched
(see behaviour § 6.3.2.7.1)
• an “AR_LOCK” signal at the RESET, received either through a BI or an operator order
If none of these methods are selected, the auto-recloser is automatically unlocked if no lock
condition is set and circuit breaker is closed. In this case, the Reclaimml timer is launched. If
the CB is not closed at the end of this timer, the auto-recloser is locked again.
Application C264/EN AP/B30

MiCOM C264/C264C Page 299/396

6.3.2 Creating an auto-recloser function

An addition of a auto-recloser is done under SCE via the “Object entry” area at bay level by
clicking on mouse’s right button.
For more details about bay creation, refer to chapter 6.1.4 Defining Bay.
Only following typed bays allows auto-recloser creation:

• Busbar,

• Bus coupler,

• Bus section,

• Feeder,

• Transformer,

• Generic bay.

FIGURE 342: ADDING AUTO-RECLOSER AT BAY LEVEL

Once added, auto-recloser general features must be set at SCE level:
1. Fill the relation ‘is auto-recloser of’, giving which circuit-breaker module is concerned
by the function
2. Short and long names of the auto-recloser used for logging, alarms ...
3. Functioning mode for 1 phase trip (Not used, 1P, 1P+3P, 1P+3P+3P, 1P+3P+3P+3P),
4. useable only for single phase circuit-breaker
5. up to 4 cycles where the first one is single phase and the others three phase
6. Functioning mode for 3 phase trip (Not used, 3P, 3P+3P, 3P+3P+3P, 3P+3P+3P+3P),
7. useable for single and triple phase circuit-breaker
8. up to 4 cycles where all are three phase
9. Unlocking way (Not used, reinitialisation, manual close, both ways),
For details refer to previous description of ‘lock of auto-recloser’ in chapter 6.3.1 Auto-
recloser behaviour.
10. Fast 3 phase reclose enable (No, Yes),
If a synchrocheck exists for the breaker, auto-recloser can bypass it during the 3-
phases first cycle if the attribute is set to ‘Yes’.
11. 1st period monophased (from 100 to 5000 ms by 10 ms):
Timer of the first single-phase cycle
C264/EN AP/B30 Application

Page 300/396 MiCOM C264/C264C

12. 1st period triphased (from 1000 to 60000 ms by 10 ms):

Timer of the first 3-phases cycle
13. 2nd period triphased (from 100 to 3600000 ms by 1000 ms):
Timer of the second 3-phases cycle
14. 3rd period triphased (from 100 to 3600000 ms by 1000 ms):
Timer of the third 3-phases cycle
15. 4th period triphased (from 100 to 3600000 ms by 1000 ms):
Timer of the fourth 3-phases cycle
16. reclaim delay (from 1000 to 600000 ms by 1000 ms):
corresponds to ‘reclaimc recovering timer’ previously described in ‘launch recovering
timer’ of chapter 6.3.1 Auto-recloser behaviour
17. unlock delay (from 1000 to 600000 ms by 1000 ms):
corresponds to ‘reclaimml recovering timer’ previously described in ‘lock of auto-
recloser’ of chapter 6.3.1 Auto-recloser behaviour
18. manual close delay (from 1000 to 600000 ms by 1000 ms):
corresponds to ‘reclaimmc recovering timer’ previously described in ‘lock of auto-
recloser’ of chapter 6.3.1 Auto-recloser behaviour
Application C264/EN AP/B30

MiCOM C264/C264C Page 301/396

(1)

(2)

(3)
(4)
(5)
(6)

(7)

(8)
(9)
(10)
(11)

(12)
obsolete
(13)

(14)

FIGURE 343: SETTING AUTO-RECLOSER FEATURES

C264/EN AP/B30 Application

Page 302/396 MiCOM C264/C264C

Configuration rules and checks

• The two attributes "functioning mode (1 ph trip)" and "functioning mode (3 ph trip)"
must not be both set to "Not used" value

• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P-3P", then the following rules
must be respected :
- "1st period monophased" < "2nd period triphased"
- "1st period monophased" < "3rd period triphased"
- "1st period monophased " < "4th period triphased"

• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P", then the following rules
must be respected :
- "1st period monophased" < "2nd period triphased"
- "1st period monophased" < "3rd period triphased"

• If "functioning mode (1 ph trip)" value is set to "1P-3P", then the following rule must be
respected :
- "1st period monophased" < "2nd period triphased"

• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P-3P", then the following rules
must be respected :
- "1st period triphased" < "2nd period triphased"
- "1st period triphased" < "3rd period triphased"
- "1st period triphased" < "4th period triphased"

• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P", then the following rules
must be respected :
- "1st period triphased" < "2nd period triphased"
- "1st period triphased" < "3rd period triphased"

• If "functioning mode (3 ph trip)" value is set to "3P-3P", then the following rule must be
respected :
- "1st period triphased" < "2nd period triphased"

• If "functioning mode (1 ph trip)" value is different from "Not used", then the "circuit-
breaker type" must be set to "Single phase CircuitBreaker"

• If "functioning mode (3 ph trip)" value is set to "Not used", then the "circuit-breaker
type" must be set to "Single phase CircuitBreaker"
To assume previous described behaviour, when adding an auto-recloser, some mandatory
datapoints are automatically created at function level and must be configured (see chapter 5
DEFINING DATAPOINT):
1. Autorecloser fault:
MPS datapoint, given the failure reason of auto-recloser function.
This a system datapoint whose available state are:

− State0: failure due to the synchrocheck

− State1: failure to hardware, lock of device or another running automation linked to

the device

− State2: failure due to interlocking function

− State3: no failure.
Application C264/EN AP/B30

MiCOM C264/C264C Page 303/396

2. auto-recloser status:
MPS datapoint, given the status of auto-recloser function.
This a system datapoint whose available state are:

− State1: auto-recloser is in service, unlocked and no cycle is in progress

− State2: auto-recloser is waiting CB opening

− State3: the first single-phase cycle is in progress

− State4: the first 3-phases cycle is in progress

− State5: the second 3-phases cycle is in progress

− State6: the third 3-phases cycle is in progress

− State7: the fourth 3-phases cycle is in progress

− State8: the auto-recloser is waiting CB closing

− State9: the Reclaimc timer is launched

− State10: auto-recloser locking due to a max number of reclosing cycles

− State11: an auto-recloser locking

− State12: the reclaimml timer is launched

− State13: the reclaimmc timer is launched

3. Force trip 3 phases SPC, used during a 3 phase cycle as mentioned in ‘Waiting CB
opening’ in chapter 6.3.1 Auto-recloser behaviour
4. on/off status DPS, corresponds to in / out of service status of the auto-recloser
5. Trip 3 phases SPS, giving information 3-phase trip provided by a relay

(1)

(2)

(3)

(4)

(5)

FIGURE 344: AUTO-RECLOSER MANDATORY DATAPOINTS

C264/EN AP/B30 Application

Page 304/396 MiCOM C264/C264C

To assume previous described behaviour, when adding an auto-recloser, some optional

datapoints can be created at function level and must be configured (see chapter 5
DEFINING DATAPOINT):
1. Blocking SPS:
corresponds to the ‘AR_BLOCKING’ BI described in chapter 6.3.1 Auto-recloser
behaviour
2. Lock/reinit SPS:
Signal to lock / unlock the auto-recloser via SPS
corresponds to the ‘AR_LOCK’ signal described in chapter 6.3.1 Auto-recloser
behaviour
3. Trip phase A SPS:
corresponds to trip status for pole A
4. Trip phase B SPS:
corresponds to trip status for pole A
5. Trip phase C SPS:
corresponds to trip status for pole A
6. Lock/reinit SPC:
Signal to lock / unlock the auto-recloser via SPC
corresponds to the ‘AR_LOCK’ signal described in chapter 6.3.1 Auto-recloser
behaviour
7. on/off control DPC:
To control in / out of service of the auto-recloser via DPC
8. on/off control DPS:
To control in / out of service of the auto-recloser via DPS

(1)
(2)

(3)
(4)
(5)
(6)
(7)
(8)

FIGURE 345: AUTO-RECLOSER OPTIONAL DATAPOINTS

Application C264/EN AP/B30

MiCOM C264/C264C Page 305/396

Configuration rules and checks

• If "functioning mode (1 ph trip)" value is different from "Not used", then at least one of
the three SPS datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is mandatory

• If "functioning mode (1 ph trip)" value is set to "Not used", then none of the three SPS
datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is allowed

• The two datapoints { "on/off ctrl DPC", "on/off ctrl DPS" } are mutually exclusive and,
at least one of them is mandatory

• The two datapoints { "lock/reinit SPC", "lock/reinit SPS" } are mutually exclusive. If the
"unlocking way" attribute value is set to "Reinitialization" or "Both ways" then, at least
one of the two datapoints is mandatory
To assume previous described behaviour, when adding an auto-recloser, some mandatory
datapoints are automatically created at circuit-breaker level and must be configured (see
chapter 5 DEFINING DATAPOINT):
1. CB Healthy:
corresponds to the ‘CB HEALTHY’ BI described in chapter 6.3.1 Auto-recloser
behaviour

(1)

FIGURE 346: AVAILABLE CB HEALTHY PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER

C264/EN AP/B30 Application

Page 306/396 MiCOM C264/C264C

6.4 Defining Tap changer built-in function

6.4.1 Tap changer behaviour
The control of transformer is done via tap changer built-in function and can be performed in
the three modes “Direct Execute”, SBO once” and “SBO many mode” (refer to chapter 5.1.9
Overview of control sequence processing).
Additionally of the selection and execution checks described in the previous chapters the
following checks are performed:

• A “raise” control is refused if the current tap position value corresponds to the
maximum position of the tap.

• A “lower” control is refused if the current tap position value corresponds to the
minimum position of the tap.
In case of “go to min”, “go to max” or “go to position x” request via datapoint (referenced (1)
in Figure 354: AVAILABLE PRE-DEFINED DATAPOINTS FOR TAP CHANGER), the
MiCOM C264 Computer use an internal automatic function (via ISaGRAF) which generates
the desired controls sequences in order to reach automatically the expected position. This
function may generate “Direct execute”, “SBO once” or “SBO many” sequences according
the configuration of the device. Extra datapoints higher and lower positions (referenced (5)
and (6) in Figure 354: AVAILABLE PRE-DEFINED DATAPOINTS FOR TAP CHANGER) can
also be produced by the ISaGRAF function for alarm synthesis.
TCIP feature:
The TCIP input information (tap change in progress referenced (7) in Figure 354:
AVAILABLE PRE-DEFINED DATAPOINTS FOR TAP CHANGER), is used to confirm the
right execution of the low/raise execution. When adding a TCIP at tap changer level, the two
configurable delays must be set at TCIP datapoint level for the correct TCIP management:
1. Start confirmation delay (from 1000 to 60000 ms by 100 ms):
The TCIP information must appear before the time-out of this delay
2. Stop confirmation delay (from 1000 to 60000 ms by 100 ms):
The TCIP information must disappear before the time-out of this delay

(1)

(2)

FIGURE 347 : SETTING TCIP SPECIFIC ATTRIBUTES

Application C264/EN AP/B30

MiCOM C264/C264C Page 307/396

TPI feature:
Because the TCIP input information is not always configured, the tap control is performed
using only the Tap Position Indication (TPI) value to verify the right execution of the request.
The TPI value must change in the given delay.
The following examples are given in “SBO many mode” which is the more complex. The
main difference with the “SBO once mode ” remain to the possibility to execute many “raise”
or “low” controls before ends the sequence. Moreover, the device is not deselected
automatically but only after an unselect order sent by the initiator of the control request.
Control of transformer with TCIP
On this mode, in case the TCIP input information is configured the selection and execution
phase are performed as follow:
Selection phase:
1. Close device selection output to select the device (if is configured)
2. Verify selection device input information associated to the output (if is configured)
3. Wait the execution request (low/raise) or timeout selection
In case of fail to one of these operations, the device is deselected, the controls sequence is
aborted with a negative acknowledgement.
Execution phase:
1. According the request “raise or lower” and the type of device, execute the associate
control
2. Wait the TCIP information and TIP value to confirm execution. Two cases :

− Case 1:
The TCIP information appears and is disappear in the given delays, the TPI take
the expected value : The MiCOM C264 Computer sends a positive
acknowledgement and waits a new request (execution or unselection).

− Case 2:
Timeout awaiting the TCIP appearance or disappearance , or the TPI value is
wrong: The device is deselected (if it was previously selected), and the sequence
is aborted with a negative acknowledgement.
3. Wait new execution request or unselection request to deselect the device:

− In case of new request the MiCOM C264 Computer repeat the steps 4 and 5.

− In case of unselection request the MiCOM C264 Computer deselect the device (if
it was previously selected), and ends the sequence with a positive
acknowledgement
C264/EN AP/B30 Application

Page 308/396 MiCOM C264/C264C

The following controls diagram shows a successful sequence with device selection, two
“raise” controls and device unselection

SPC select
(optional)

SPS select
(optional)

DPC raise/lower
OPEN

TPI Value
(1)
raise/lower
CLOSE

SPS TCIP

Feedback Selection TCIP

Pulse
Delay timeOut disappearance FeedBack
Delay
time Delay Delay

0-5 s 4

0-1 s 0-10mn TCIP apparition 0-1 s 0-1 s

time Delay

11 End of control

1 2 3 0-5 s
4 5 6 7 8 9 10 11
1 selection “raise” request
3 first execution 6 second execution 10 unselect request
request request C0240ENa

FIGURE 348 : SUCCESSFUL TAP CONTROL WITH TCIP INFORMATION (E.G.)

(1) the TPI value must take the expected value at least at the end of TCIP disappearance

The following diagram shows an abnormal termination of tap changer control sequence due
to absence TCIP confirmation. In this case the device is automatically deselected and the
sequence ends with a negative acknowledgement

SPC select
(optional)

SPS select
(optional)

DPC raise/lower
OPEN

raise/lower
CLOSE

SPS TCIP

TIP value

Feedback Selection FeedBack Delay

Pulse
Delay timeOut
Delay

4
0-5 s
0-1 s 0-10mn 0-1 s
TCIP apparition time
1 2 Delay 5 6
1 selection request “raise” 6 End of control

3 0-5 s
3 execution request
C0241ENa

FIGURE 349 : UNSUCCESSFUL TAP CONTROL WITH TCIP INFORMATION (E.G.)

Application C264/EN AP/B30

MiCOM C264/C264C Page 309/396

Control of transformer without TCIP

In case the TCIP input information is not configured the selection and execution phase are
performed as follow:
Selection phase:
1. Close device selection output to select the device (if is configured)
2. Verify selection device input information associated to the output (if is configured)
3. Wait the execution close request or timeout selection
In case of fail to one of these operations, the device is deselected, the controls sequence is
aborted with a negative acknowledgement.
Execution phase:
1. According the request “raise or lower” and the type of device, execute the associate
control
2. Wait the TPI value and compare with the previous value. The difference must confirm
the “low” or “raise” execution. Two cases :

− Case 1:
The TPI value confirms in the given delay the execution request: The MiCOM
C264 Computer sends a positive acknowledgement and waits a new request
(execution or unselection) from the initiator.

− Case 2:
Timeout awaiting the TPI value or unexpected TPI value: The device is deselected
(if it was previously selected), and the sequence is aborted with a negative
acknowledgement.

3. Wait new execution request or unselection request to deselect the device

− In case of new request the MiCOM C264 Computer repeat the steps 4 and 5.

− In case of unselection request the MiCOM C264 Computer deselect the device (if
it was previously selected), and ends the sequence with a positive
acknowledgement
The following controls diagram shows a successful sequence with device selection, a raise
control and device unselection.

SPC select
(optional)

SPS select
(optional)

DPC raise/lower
OPEN

raise/lower
CLOSE

TPI

feedback
Feedback Selection Delay
Pulse
Delay time-out
Delay

4
0-5 s
0-1 s 0-10mn 0-1 s
new TPI value
1 2 Delay 6
1 selection “raise” request 7 End of control
6 Unselect request
3 0-5 s 5
3 execution request
C0242ENa

FIGURE 350 : SUCCESSFUL TAP CONTROL WITHOUT TCIP INFORMATION (E.G.)

C264/EN AP/B30 Application

Page 310/396 MiCOM C264/C264C

The following controls diagram shows an abnormal termination due to the absence of
change of the TPI value in the given delay. The device is automatically deselected, and the
sequence is aborted with negative acknowledgement.

SPC select
(optional)

SPS select
(optional)

DPC raise/lower
OPEN

raise/lower
CLOSE

TPI

Feedback Selection FeedBack

Pulse Delay
Delay timeOut
Delay

4
0-5 s
0-1 s 0-10mn 0-1 s
new SPI value
1 2 Delay 6
1 selection request “raise”
6 End of control

3 0-5 s 5
3 execution request C0243ENa

FIGURE 351 : UNSUCCESSFUL TAP CONTROL WITHOUT TCIP INFORMATION (E.G.)

Suppression, Forcing or Substitution of the TPI
In case of suppress or substitution of TPI value the control sequence is aborted with
negative Acknowledgement. In case of Forcing the sequence is not aborted but the value of
TPI taken in account during the control sequence is the forced value.
6.4.2 Creating a tap changer function
Tap changer is considered as a function because it verifies maximal and minimal useable
positions of tap position indicator. It is like a sub-module of transformer module and owns the
tap position indicator and optional controls (Raise/Lower, Goto Min/Max).
To create a tap-changer built-in function, add it from object entry available at transformer
module level (1).

(1)

FIGURE 352: ADDING A TAP CHANGER BUILT-IN FUNCTION TO TRANSFORMER

When adding a tap changer function, the following general attributes must be updated:
1. Short and long names of the tap changer used for logging, alarms ...
2. Minimal usable position (from 1 to 64)
3. Maximal usable position (from 1 to 64), that must be greater to (2)
4. Execution time-out (from 0 to 5000 ms by 100 ms):
Maximum delay in which tap position must have changed relatively to the current tap
control in progress. If delay expired bad acknowledgement is sent for tap control.
Application C264/EN AP/B30

MiCOM C264/C264C Page 311/396

(1)

(2)
(3)

(4)

obsolete
C0244ENa

FIGURE 353 : SETTING TAP CHANGER ATTRIBUTES

When adding a tap changer function, the mandatory TPI datapoint ‘Tap position indicator’ is
automatically created at function level.
The following tables give inputs and outputs tap changer’s features controlled by the MiCOM
C264 Computer. For each datapoint its SCE identification is given by a number, referenced
in the following figure.
To configure correctly the tap changer of a transformer module:

• Add the relevant datapoints, relatively to the following tables,

• configure them (see chapter 5 DEFINING DATAPOINT)

Tap changer for transformer

OUTPUTS INPUTS

DEVICE (2) DPC raise/lower (8) TPI value

CONTROL (1) DPC (optional) goto (7) SPS (optional) tap change
min/max in progress

DEVICE (4) SPC (optional) transformer (i) SPS (optional) selection

SELECTION selection position information
(HARDWARE)

(i) This SPS is a generic one put at transformer module level and configured as feedback of
SPC transformer selection (4).
C264/EN AP/B30 Application

Page 312/396 MiCOM C264/C264C

(1)

(2)

(3)
(4)

(5)

(6)

(7)

(8)

FIGURE 354: AVAILABLE PRE-DEFINED DATAPOINTS FOR TAP CHANGER

Configuration rules and checks

• "Raise/lower DPC" Datapoint must have its profile attribute “SBO mode” set to "SBO
Operate Many"
6.5 Defining AVR built-in function
6.5.1 AVR behaviour
The Automatic Voltage Regulation (AVR) function is used to automatically maintain the
correct voltage at the lower voltage (LV) of transformers. Secondary voltage is changed by
controlling the tap changer of transformers. AVR is also called Automatic Tap Changer
Control (ATCC).
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

Application C264/EN AP/B30

MiCOM C264/C264C Page 313/396

6.5.1.1 Required datapoints and topology (function interface)

For each transformer, PACiS acquires :

• Current, voltage, active and reactive powers of the LV side :

− MV values: (DPT_Trf 15) to (DPT_Trf 18)
• Electrical topology of the LV side, including connection of the transformer to the
busbar and coupling of busbars into the LV level (see chapter 6.5.2.5 Defining
electrical topology for AVR function)
• Tap Changer MCB state
The operator, through PACiS OI or Telecontrol gateway, has an access to the following
controls :

• Global AVR On/Off:

− SPC control (DPT_Sub 2)
− SPS status (DPT_Sub 6)
• AVR On/Off per busbar:
− SPC control (DPT_Bb 6)
− SPS status (DPT_Bb 5)
• Five Target Voltages per busbar (linked to 5 floating values pre-set in configuration in
the range +/- 10% with a resolution of 1 %):
− SPC control ((DPT_Bb 7) to (DPT_Bb 11))
− SPS status ((DPT_Bb 12) to (DPT_Bb 16))
The current busbar AVR mode (DPT_Bb 5)is equal to (busbar AVR mode) AND (Global
AVR mode).
The following specific alarms and indications are available :
Substation alarms or indications

• Target Not Achievable

− SPS status (DPT_Sub 7)
• AVR defective
− SPS status (DPT_Sub 3)
• Error Log Indication
− SPS status (DPT_Sub 5)
• DBI override
− SPS status (DPT_Sub 4)
Busbar alarms or indications

• Invalid voltage (when different values for parallel transformers)

− SPS status (DPT_Bb 3)
• More than 4 transformers in the group
− SPS status (DPT_Bb 4)
• Under-voltage or over-voltage: AVR INHIBITED
− SPS status (DPT_Bb 1)
• A circuit breaker or a disconnector in an invalid state in the group
− SPS status (DPT_Bb 2)
C264/EN AP/B30 Application

Page 314/396 MiCOM C264/C264C

Transformer alarms or indications

• AVR on/off, used to avoid control of transformer outside the scope of AVR if AVR is
on:

− SPS status (DPT_Trf 1)

• Hunting: this alarm is reset 30 seconds after the group is switched to AVR OFF

− SPS status (DPT_Trf 3)

• MCB tripped

− SPS status (DPT_Trf 10)

• Bad TCIP: this alarm is reset 30 seconds after the group is switched to AVR OFF

− SPS status (DPT_Trf 4)

• Tap Position is not the expected one

− SPS status (DPT_Trf 6)

• Current > Overcurrent value

− SPS status (DPT_Trf 11)

• AVR disconnected

− SPS status (DPT_Trf 8)

• Bay in local mode

− SPS status (DPT_Trf 9)

• Voltage, current, MW and MVAR

− MV values (DPT_Trf 15) to (DPT_Trf 18)

• AVR homing

− MPS status (DPT_Trf 2)

• Invalid Voltage

− SPS status (DPT_Trf 14)

• Low Voltage

− SPS status (DPT_Trf 13)

• Over Voltage

− SPS status (DPT_Trf 12)

• Run Away : this alarm is reset 30 seconds after the group is switched to AVR OFF

− SPS status (DPT_Trf 7)

• Tap long TCIP

− SPS status (DPT_Trf 5)

Application C264/EN AP/B30

MiCOM C264/C264C Page 315/396

The AVR Defective Alarm and the AVR Error Log Indication are grouped alarms with the
following inputs :
Per busbar

• Invalid voltage (when different values for parallel transformers)

• More than 4 transformers in the group

• A circuit breaker or a disconnector in an invalid state in the group

Per transformer

• hunting

• MCB tripped

• bad TCIP

• Tap Position is not the expected one

• Bay disconnected (this takes into account power supply fail)

• Bay in local mode

• invalid voltage
The AVR Defective Alarm is set if one of the input is set, and is reset if all the inputs are
reset.
The AVR Error Log Indication is set if one of the input is set and is reset if the operator
selects the "Clear AVR Faults" command.
6.5.1.2 Groups
6.5.1.2.1 Definition
A group defines a set of interconnected busbars. A transformer belongs to a group if it is
electrically connected to a busbar of this group into the low voltage level.
Group mode is used to allow the automatic control of transformers. Group mode is either In
automatic control, or Out of automatic control. Busbars and transformers have their own
modes used to calculate the group mode.
6.5.1.2.2 Group mode calculation
This section details the group mode calculation. Each transformer, busbar and group is
concerned by attributes, used to calculate the transformer, busbar and group modes.
Attributes are entered during the configuration phase or calculated with the dynamic
electrical topology and settings of the system. Attributes may be ignored to calculate the
mode, this is defined during the configuration phase.
Transformer attributes are :

• Type (Auto or double wound)

• Transformer rating in MVA

• Number of taps

• Tap Span

• Its actual connection with a busbar (topology)

• The state of its MCB (Open or Closed)

• Tertiary reactor capacities (in MVAR)

C264/EN AP/B30 Application

Page 316/396 MiCOM C264/C264C

• The state of its tap changer: normal, abnormal (tap changer control)
the state is abnormal if :

− TCIP signal too late or too long,

− the tap is invalid,

− the tap number is not the required tap, we may have this problem after a tap
operation if the tap number is not the expected one.

• Its hunting status (True or False). Hunting is detected if more than N changes occurs
in less than T. The window time for hunting is comprised between 120 seconds to
1800 seconds in 0,1 second increments.

• Its homing status (On, Off or Inhibited)

• Status of the bay containing the tap change control: local/remote,

connected/disconnected (supervision values)

• Associated Voltage, current, MWs, MVARs, and their validity (measured values)

• Its mode : In or Out (of automatic control).

Mode is Out if:

− The transformer is disconnected and it is not in Homing mode

OR

− The transformer is connected or it is not in Homing mode

AND
(
Tap changer is tripped, OR
tap changer state is abnormal, OR
transformer is hunting, OR
its voltage is invalid, OR
the bay containing the tap changer control is in local mode, OR
the bay containing the tap changer control is not accessible
)
OR

− The busbar is OUT of automatic control

A transformer is disconnected if it is not electrically connected to a busbar.
Busbar attributes are :

• Its transformers (configuration and topology)

• Its topology (busbar section and coupler)

• Its voltage target

• Its priority. This is given by configuration.

• Its actual voltage: This voltage is the average of the LV voltages of the connected
transformers. If one of the voltages differs by more than x% from the average, or if
one voltage is invalid then actual voltage is invalid.

• Its mode: In or Out (of automatic control).

Mode is Out if:

− The mode of one of the transformers connected to it is Out

OR

− Actual Voltage is invalid.

Application C264/EN AP/B30

MiCOM C264/C264C Page 317/396

Group attributes are :

• Its voltage target. This target is deduced from the busbar target composing the group.
The busbar with the highest priority forces the target.

• Its actual voltage. This voltage is the average of the busbar actual voltages. If one of
the voltages differs by more than x% from the average, or if one voltage is invalid then
actual voltage is invalid.

• Its busbars. This is given by the topology.

• Its mode: In or Out (of automatic control).

Mode is Out if:

− Global AVR is Out

OR

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

− Actual Voltage is invalid.

OR

− more than 4 transformers in the group.

OR

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

When a group is set OUT of automatic control, it remains in this state until the operator sets
the group IN automatic control.
It is only necessary to select one busbar in a group to automatic control to place the whole
group under automatic control.
When the substation control mode is Remote, the AVR control is allowed from the RCP and
inhibited from the SCP. When the substation control mode is Local, the AVR control is
allowed from the SCP and inhibited from the RCP.
6.5.1.3 Tap changer control
Tap changer basic control is described in chapter 6.4.1 Tap changer behaviour.
If a transformer is in automatic control and if there is an invalid evolution of the tap changer,
then the tap changer MCB is tripped and the RunAway alarm is set.
6.5.1.4 Moving Tap Changers
6.5.1.4.1 General
Automatic control of a transformer is only allowed if it belongs to a group in Automatic control
mode or for homing. Manual control of a transformer is only allowed if its setting mode is Out
of automatic control.
Note that :

• Automatic control of a tap changer is independent of the mode of the substation

(SCP/RCP)

• Automatic control of a tap changer may be used in conjunction with manual control of
transformer belonging to an other group in manual mode or with manual control of the
rest of the apparatus (breaker, disconnector, protections, ...).

• Simultaneous operations on transformers belonging to independent groups is allowed,

since the electrical topology is not affected.
C264/EN AP/B30 Application

Page 318/396 MiCOM C264/C264C

Decision to move one or more tap changers is caused by one of the following reasons:

• Voltage in one group is outside of the Voltage Target Deadband. This is the most
common situation.

• Voltage is correct, but there is a circulating current between parallel transformers .

This will happen when two groups are interconnected.

• Voltage is correct, but the tap span and patterning may be changed when any of the
relevant switchgear change state.

• Homing of one transformer. This will happen when the circuit breaker at the LV side of
the transformer is open, and Homing status is on.
6.5.1.4.2 Voltage is outside of the Voltage Target Deadband
This paragraph specifies the algorithm used to decide the change of a tap, when voltage is
outside of the voltage deadband.
The target voltage that must be reached is defined by :
Target Voltage
= [Selected Target Voltage + Voltage Compounding] * Voltage SetPoint,
where :

• Selected Target Voltage is one of the five pre-programmed Selected Target Voltages.
(when the AVR starts up, the selected target voltage is a target voltage pre-set in
database)

• Voltage SetPoint is a coefficient typically comprised between 0.9 and 1.

• Voltage Compounding is line drop compensation, it allows to maintain the nominal

voltage at a remote location of the actual measurement point.
There are two methods for line drop compensation. According to the customer, one is
defined during the configuration phase :

• First line drop compensation method :

Voltage Compounding
= Actual busbar load ( MW ) * Resistive multiplier
+ Actual busbar load ( MVAR ) * Reactive multiplier.

• Second line drop compensation method :

Alternatively the line drop compensation can also be achieved by using the resistance
R and reactance X of the connection circuit as compounding settings. In this method,
the measured voltage is adjusted such that :

V = • ((V0 – A)² + B²)

Where:

− V0 actual measured value

− V adjusted measured value. V is used to determine the tapping action by

comparing with the target voltage

− A = (R*P + X*Q) / V0

− B = (X*P - R*Q) / V0

− P active power, Q reactive power,

− R et X are the resistance and the reactance of the connection circuit for the
resistive and reactive compounding respectively.
Application C264/EN AP/B30

MiCOM C264/C264C Page 319/396

Voltage deadband
The Voltage Deadband is expressed as a percentage of the nominal voltage. By
configuration, coefficients are set to adjust the deadband with the number of transformers in
a group.
Voltage deadband = Initial Voltage deadband * coefficient.
Two examples :

case 1 case 2
Group with 1 transformer : 1 1
Group with 2 transformers : 1 1
Group with 3 transformers : 1 2/3
Group with 4 transformers : 1 1/2

Decision to move the tap changer is made when :

• Voltage > Target Voltage + Voltage Deadband * Nominal Voltage

OR

• Voltage < Target Voltage - Voltage Deadband * Nominal Voltage

for more than a time-out T1.
Dual deadbands are used to ensure that the post tapping voltage is sufficiently closed to the
selected target voltage. Deadband 1 is used to initiate tapping and deadband 2 is used to
end tapping.
6.5.1.5 Time outs
Moving the taps of the transformers is achieved with respect of some time-outs.
The "first tap" of a transformer is delayed by a time out T1, the next ones by a time out T2.
Several taps are used if one is not enough to reach the voltage target or the optimisation of
the circulating current. T2 begins after the end of the TCIP (see FS07).
When the voltage is drifting in and out of the deadbands, the system counts up to T1 when
the voltage is outside of the deadband1. If before T1 is reached the voltage returns within the
deadband2 then the system counts down to 0.
When the voltage is crossing from one side of the deadband1 to the other side, the count is
reset to zero and the new time delay is T1.
After an auto-recloser operation , the group (or the two new groups) keeps the same AVR
modes; however the count is reset to zero and the new time delay is T1.
T1 is adjustable between 15 and 120 seconds in 0,1 second increments.
T2 is adjustable between 0 and 120 seconds in 0,1 second increments.
Moreover, the AVR shall not drive the system voltage by more than a pre-set rate (defined in
database). This rate, “maximum voltage change rate” is settable between 0,1kV/min and
5kV/min in 0,1kV/min increment.
If a Tapping is required after a previous tap control:

− Ti is the date when the previous tapping was performed.

− T is the current date

− MVCR is the Max voltage change rate,

− T2 is the inter Tap delay,

− Vi was the secondary voltage at Ti

− V is the current secondary voltage

C264/EN AP/B30 Application

Page 320/396 MiCOM C264/C264C

• for a Tap Up( to increase voltage), tapping is performed as soon as the following are
TRUE

− T > Ti + T2

− V < Vi + MVCR * ( T - Ti)

• for a Tap Down( to decrease voltage), tapping is performed as soon as the following
are TRUE

− T > Ti + T2

− V > Vi - MVCR * ( T - Ti)

The maximum voltage rate is achieved as described in the example below:

Volt
RateMax

Time
T1 T2 T2
T0

Tap RAISE 1 Tap RAISE 2 Tap RAISE 3

C0245ENa

FIGURE 355 : AVR VOLTAGE MANAGEMENT

Tap RAISE 1 is performed after T1.
Tap RAISE 2 is performed T2 after Tap RAISE 1, at this time the voltage change rate is
lower than the maximum rate.
Tap RAISE 3 is NOT performed T2 after Tap RAISE 2, because at this time the voltage
change rate is greater than the maximum rate. It is performed when the current voltage
change rate becomes lower than the maximum rate.
It is possible to choose by configuration a T1 delay as a fixed delay or as an inverse time
delay.
When inverse initial time delay is selected :
DV = | actual group voltage - deadband limit voltage |

• IF DV < 1% target voltage THEN initial tap time delay = T1.

• IF 1% <= DV < 10% target voltage THEN initial tap time delay = T1/DV.

• IF DV >= 10% target voltage THEN initial tap time delay = T1/10.
When a transformer belongs to a group of several transformers, the time out is applied to the
group. Two different groups have separate time out references, thus allowing simultaneous
taps.
The tap is defined as the "first one" when (logical OR):

• The group mode has changed.

• The voltage comes back into the deadband2.

• When the voltage is crossing from one side of the deadband to the other side.
Application C264/EN AP/B30

MiCOM C264/C264C Page 321/396

6.5.1.5.1 Single transformer management

If a group is restricted to 1 transformer and is In automatic control mode, raise and lower
commands are issued if the voltage exceeds the voltage deadband with respect of the time
outs (see last two paragraphs).
6.5.1.5.2 Co-ordination strategy : minimisation of the circulating reactive power
If a group is composed of more than one transformer and is in automatic control mode, then
the co-ordination of the transformers of the group aims at minimising the circulating power.
To achieve this, there are three methods depending on the substation constraint and
customer requirement. By configuration one of the three is chosen.
For the three following methods, if all the transformer tap-changers reach their end stop
while tapping is required to go further, then the substation alarm "target not achievable" is
generated. This alarm disappears when the problem is cleared.
FIRST METHOD: “TAP”
In this case, assumption is made that :

• the primary voltages of the transformers are identical

• the number of taps and tapping ranges of the transformers are identical
Then the maximum tap span between the transformers will be 1 and there will be a balanced
control of them when the voltage is changing.
Calculation is as follows :
1. if voltage is out of the deadband,
1.1) and under the deadband -> action is raise on the transformer with the
lowest Tap
1.2) and upper the deadband -> action is lower on the transformer with the
highest Tap
2. if voltage is in the deadband, the system sets the transformer within one tap
SECOND METHOD: “TRANSFORMER RATIO”
In this case, assumption is made that :

• the primary voltages of the transformers are identical.

Calculation is as follows :
1. if voltage is out of the deadband,
1.1) and under the deadband -> action is raise on the transformer with the
lowest transformer ratio
1.2) and upper the deadband -> action is lower on the transformer with the
highest transformer ratio
2. if voltage is in the deadband, the system sets the transformer within a percentage of
transformer ratio. This percentage P is calculated for all groups :
P = Maximum (tapping range / ( number of taps - 1 ))
Example :
Group with 3 transformers :

• SGT1 : 19 taps, tapping range = 30 %

• SGT2 : 19 taps, tapping range = 30 %

• SGT3 : 16 taps, tapping range = 20 %

P = Max(30 / 18; 30 / 18; 20 / 15) = 30/18 % = 1.67 %
C264/EN AP/B30 Application

Page 322/396 MiCOM C264/C264C

So, the 3 transformers stay within 1.67 %.

Tap operation if (ratioMax - ratioMin) > 0,0167 ratioNom, with :

• ratioMin = Minimum transformer ratio of the 3 transformers

• ratioMax = Maximum transformer ratio of the 3 transformers

• ratioNom = Nominal secondary voltage / Nominal primary voltage (defined in

configuration)
THIRD METHOD: “CIRCULATING CURRENT MINIMISATION”
In this case, there is no assumption that the primary voltages of the transformers are
identical.
With a sample example of two transformers :

SGT1 SGT2

I1 I2

Per transformer, we know:

• Sn ( rating),

• x ( Impedance in % on Sbase : e.g.100 MVA)

• U,I,P,Q,

• Current tap

• Unom ( nominal secondary voltage)

• X (reactance) = x * (Unom)² / Sbase

One transformer can be presented as below :

E
Application C264/EN AP/B30

MiCOM C264/C264C Page 323/396

The both transformers can be presented as below:

I
Ic

X1
X2
U
I1 I2

E1 E2

we have:
U = E1 - X1*I1 = E2 - X2*I2 => E1-E2 = X1*I1 - X2*I2
I = I1 + I2
E1 - E2 = (X1 + X2 ) * Ic
=> Ic = (X1*I1 - X2*I2) / ( X1 + X2)
For each transformer, we have U,I,P,Q (So U1,I1,P1,Q1 and U2,I2,P2,Q2)

We have for i=1 or i=2, Qi/Pi = tan ϕi

According to the signs of Pi and Qi: - < ϕi <

If there is a circulating current from transformer 1 to transformer 2 then ϕ1 > ϕ2.

U1 = U2

I
I2

φ1

I1
C264/EN AP/B30 Application

Page 324/396 MiCOM C264/C264C

Voltage out of the deadband

If the voltage is out of the deadband and active power > 0 (|ϕ| < π/2) then:

• If the voltage is under the target then transformer with highest |ϕ| is tapped UP

• If the voltage is over the target then transformer with lowest |ϕ| is tapped DOWN

• If the voltage is out of the deadband and active power < 0 (|ϕ| > π/2) then

• If the voltage is under the target then transformer with lowest |ϕ| is tapped UP

• If the voltage is over the target then transformer with highest |ϕ| is tapped DOWN
For three or four transformers, the same algorithm is used.
Voltage into the deadband
If the voltage is into the deadband then the circulating current must be checked to know if it
is possible to reduce it.

∆U = E1 – E2 = |X1*I1 - X2*I2|

∆U is compared to the voltage step corresponding to one tap (•U1tap).

− TapSpan : tap span for the transformer

− NbTap: number of taps for the transformer

− Unominal: nominal secondary voltage

− ∆U1tap = (TapSpan/( NbTap -1)) * Unominal

if ∆U > ∆U1tap and if ϕi > ϕj so

If the voltage is out of the deadband and active power > 0 (|ϕ| < π/2) then:

• If the voltage is under the target then transformer with highest |ϕ| is tapped UP

• If the voltage is over the target then transformer with lowest |ϕ| is tapped DOWN

If the voltage is out of the deadband and active power < 0 (|ϕ| > π/2) then

• If the voltage is under the target then transformer with lowest |ϕ| is tapped UP

• If the voltage is over the target then transformer with highest |ϕ| is tapped DOWN
For three or four transformers, the same algorithm is used.
6.5.1.5.3 Target voltage
When the operator changes a target voltage, the new target voltage is indicated immediately.
The actual target voltage will not be changed by more than the corresponding pre-set value if
the busbar is under automatic control. If the busbar is not under automatic control the new
target voltage is immediately achieved.
6.5.1.5.4 AVR inhibited
AVR is inhibited for the corresponding group while the measured system voltage is less than
a pre-set value or higher than an other pre-set value.
Overcurrent on a transformer will also inhibit the transformer's group.
6.5.1.5.5 Homing
Homing is a facility which taps transformers such that their open circuit terminal volts follows
the volts on the busbars that they are selected to within 3% of the busbar voltage when the
mode of this busbar is In automatic control.
Application C264/EN AP/B30

MiCOM C264/C264C Page 325/396

Homing is only able if there is at least one transformer connected on the corresponding
busbar and if transformer busbar disconnector is closed and LV circuit breaker open.
Homing is disabled while the busbar voltage is less than Umin (80% of nominal voltage).
If a transformer is under Homing Mode, a manual control is not accepted.
Homing ceases when the tap changer is faulty and until the operator selects "Clear AVR
faults". If the Tap Changer is still faulty then the transformer remains OUT of automatic
control.
Time out T3 is used for the first tap in the homing mode.
Time out T4 is used between successive taps.
6.5.1.6 Capacity
AVR is able to manage a maximum of :

• 7 transformers

• 4 transformers in parallel

• 8 busbars

• 4 transformers per busbar

• 2 reactors per transformer

• 2 voltage levels
6.5.1.7 List of configurable parameters
General parameters
(param 1) AVR used / or not
(param 2) Homing ON / OFF
(param 3) initial tap time delay (T1) fixed / or not (see chapter 6.5.1.5 Time outs)
(param 4) calculation mode (see chapter 6.5.1.5.2 Co-ordination strategy : minimisation of
the circulating reactive power) :
− method “TAP”

− method “ transformer ratio”

− method “circulating current minimisation”

(param 5) period of AVR calculation (default value: 1 second)
(param 6) percentage of the Homing deadband (default value: +/-3%)
(param 7) initial tap time delay : T1 (default value: 60 seconds; range 15 to 120)
(param 8) inter tap time delay : T2 (default value: 10 seconds; range 0 to 120)
(param 9) initial tap time delay : T3 (default value: 60 seconds; range 15 to 120)
(param 10) inter tap time delay : T4 (default value: 10 seconds; range 0 to 120)
(param 11) hunting window : T5 (default value: 500 seconds; range 120 to 1800)
(param 12) coefficients (see chapter 6.5.1.4.2 Voltage is outside of the Voltage Target
Deadband) for 1, 2, 3 and 4 transformers (default values : 1)
(param 13) maximal number of successive taps in opposite direction for hunting (default
value: 4 )
(param 14) percentage of accepted difference between secondary voltages for transformers
in the same group. (default value: +2%)
(param 15) under-voltage: percentage of nominal voltage under which AVR or Homing is
inhibited (default value: 80%)
C264/EN AP/B30 Application

Page 326/396 MiCOM C264/C264C

(param 16) over-voltage: percentage of nominal voltage over which AVR or Homing is
inhibited (default value: 120%)
(param 17) mode group interconnexion : IN and OUT => IN or IN and OUT => OUT
(param 18) mode if bay in local : IN / OUT
(param 19) compounding method : setpoint adjust or voltage adjust
Parameters per busbar
(param 20) Resistive multiplier (default value: 0.01%; range –0,1% to +0,1%)
(param 21) Reactive multiplier (default value: 0.01%; range –0,1% to +0,1%)
(param 22) SetPoint value (default value: 1; range 0.9 to 1 )
(param 23) Priority : 0 to 4
Parameters per transformer
(param 24) AVR tap minimum and maximum value
(param 25) AVR transformer rating (default value: 240 MVA)
(param 26) AVR transformer impedance on nominal tap on 100 MVA base
(param 27) AVR transformer type (autotransformer or double wound)
(param 28) AVR tapping range :
− upper value (default value: +20%)

− lower value (default value: -20%)

(param 29) Nominal ratio
(param 30) Overcurrent setting (default value: 140%; range 100 to 200% )
Parameters per voltage level
(param 31) Target voltage ramping rate (default value: 1.5 kv per minute)
(param 32) Max voltage change rate (default value: 0,1 kv per minute)
(param 33) voltage deadband1 (default value: +/-1%; range +/-0.5% to +/-5% )
(param 34) voltage deadband2 (default value: +/-1%; range +/-0.5% to +/-5% )
(param 35) Target voltage 1 (default value: 90% of nominal voltage; range +/- 10% of
nominal voltage)
(param 36) Target voltage 2 (default value: 95% of nominal voltage; range +/- 10% of
nominal voltage)
(param 37) Target voltage 3 (default value: nominal voltage; range +/- 10% of nominal
voltage)
(param 38) Target voltage 4 (default value: 105% of nominal voltage; range +/- 10% of
nominal voltage)
(param 39) Target voltage 5 (default value: 110% of nominal voltage; range +/- 10% of
nominal voltage)
(param 40) Target voltage by default
Application C264/EN AP/B30

MiCOM C264/C264C Page 327/396

6.5.2 Creating an AVR function

AVR (or ATCC) is a complex built-in function for it concerns specific modules, bays, voltage
levels (transformer, busbar, voltage level) constituting the substation. At SCE level, AVR
modelling is split in different objects (ATCC function needs) located under each electrical
component relevant to it. The set of these objects corresponds to the parameterisation of
AVR substation built-in function.
Adding ‘ATCC function needs’ object under electrical component permits automatic
datapoint creation. These datapoints concerns AVR real-time information and controls
relevant to this electrical component.
Voltage levels managed by AVR do not need specific datapoints for the AVR function. So,
specific attributes put at voltage level objets are preferred to give extra AVR function needs
for each voltage level.
In the following sub-chapters, required datapoints for AVR function are prefixed with an
identifier, refered in chapter 6.5.1.1 Required datapoints and topology (function interface) of
AVR behaviour.
Configuration rules and checks

• If there is no ATCC under the Substation, then :

- a "Voltage level" must not have its "ATCC existence" attribute set to "Yes".
- the "ATCC fct needs" is allowed neither under a "transformer" nor under a "BusBar".

• If there is an "ATCC fct needs" under a "transformer", then :

- the "Tap changer" with its "Raise/lower DPC" Datapoint are mandatory.
- one of the two Datapoints { "MCB position DPS", "MCB position SPS" } is mandatory.
They are mutually exclusive.
- the "transformer" must be linked to a Voltage level through one and only one of the
relations { "has its primary on", "has its secondary on" }. The Voltage level must be
different from the one under which the transformer is located.
6.5.2.1 Defining AVR function needs at substation level
The entry point of AVR configuration is done at substation level.
This is done under SCE via the “Object entry” area at substation level by clicking on mouse’s
right button.

(1)

FIGURE 356: ADDING AVR FUNCTION AT SUBSTATION LEVEL

Once added, AVR features must be set at SCE level:
1. Fill the relation ‘is manages by’, giving which MiCOM C264 Computer runs and
supervises AVR function at substation level.
2. Short and long names of the AVR used for logging, alarms ...
C264/EN AP/B30 Application

Page 328/396 MiCOM C264/C264C

‘General’ attributes:
‘calculation’ attributes
3. Calculation period
corresponds to (param 5) in chapter 6.5.1.7 List of configurable parameters
4. Calculation mode
corresponds to (param 4) in chapter 6.5.1.7 List of configurable parameters
‘Homing’ attributes
5. Active homing
corresponds to (param 2) in chapter 6.5.1.7 List of configurable parameters
6. Homing deadband
corresponds to (param 6) in chapter 6.5.1.7 List of configurable parameters
‘ATCC mode changing’ attributes
7. Mode on group interconnection
corresponds to (param 17) in chapter 6.5.1.7 List of configurable parameters
8. Mode on bay in local
corresponds to (param 18) in chapter 6.5.1.7 List of configurable parameters
‘Compounding’ attributes
9. Compounding method
corresponds to (param 19) in chapter 6.5.1.7 List of configurable parameters
‘Delays’ attributes:
‘Nominal’ attributes
10. fixed initial tap delay
corresponds to (param 3) in chapter 6.5.1.7 List of configurable parameters
11. initial tap delay (in ms)
corresponds to (param 7) in chapter 6.5.1.7 List of configurable parameters
12. inter tap delay (in ms)
corresponds to (param 8) in chapter 6.5.1.7 List of configurable parameters
‘Homing’ attributes
13. homing initial tap delay (in ms)
corresponds to (param 9) in chapter 6.5.1.7 List of configurable parameters
14. homing inter tap delay (in ms)
corresponds to (param 10) in chapter 6.5.1.7 List of configurable parameters
‘Hunting’ attributes
15. hunting window (in ms)
corresponds to (param 11) in chapter 6.5.1.7 List of configurable parameters
16. opposite max tap changes
corresponds to (param 13) in chapter 6.5.1.7 List of configurable parameters
‘Inhibition’ attributes
‘Inhibition conditions’ attributes
17. max voltage difference (ratio)
corresponds to (param 14) in chapter 6.5.1.7 List of configurable parameters
18. tolerable nominal under voltage (ratio)
corresponds to (param 15) in chapter 6.5.1.7 List of configurable parameters
19. tolerable nominal over voltage (ratio)
corresponds to (param 16) in chapter 6.5.1.7 List of configurable parameters
Application C264/EN AP/B30

MiCOM C264/C264C Page 329/396

‘Busbar voltage’ attributes

Coefficients for busbar voltage calculation attributes
corresponds to (param 12) in chapter 6.5.1.7 List of configurable parameters
20. voltage coefficient for 1 transfo
21. voltage coefficient for 2 transfos
22. voltage coefficient for 3 transfos
23. voltage coefficient for 4 transfos

(1)

(2)

(3)
(4)
(5)
(6)
(7)
(8)
(9)

FIGURE 357: SETTING GENERAL FEATURES TO AVR

C264/EN AP/B30 Application

Page 330/396 MiCOM C264/C264C

(10)
(11)

(12)
(13)
(14)
(15)
(16)

FIGURE 358: SETTING DELAYS ATTRIBUTES TO AVR

(17)
(18)

(19)

FIGURE 359: SETTING INHIBITION ATTRIBUTES TO AVR

(20)
(21)

(22)
(23)

FIGURE 360: SETTING BUSBAR VOLTAGE ATTRIBUTES TO AVR

Application C264/EN AP/B30

MiCOM C264/C264C Page 331/396

When adding an AVR at substation, the following mandatory datapoints are automatically
created and must be configured (see chapter 5 DEFINING DATAPOINT):
(DPT_Sub 1) ATCC clear alarm SPC
(DPT_Sub 2) ATCC on/off control SPC
(DPT_Sub 3) AVR defect alarm SPS
(DPT_Sub 4) DBI override SPS
(DPT_Sub 5) ErrorLog SPS
(DPT_Sub 6) On/off SPS
(DPT_Sub 7) Target unreached SPS

(DPT_Sub 1)

(DPT_Sub 2)
(DPT_Sub 3)

(DPT_Sub 4)

(DPT_Sub 5)
(DPT_Sub 6)

(DPT_Sub 7)

C0246ENa

FIGURE 361: MANDATORY DATAPOINTS FOR AVR AT SUBSTATION LEVEL

6.5.2.2 Defining AVR function needs at voltage level
For each voltage level containing a transformer concerned by an AVR function, extra AVR
configuration must be done.
This is done under SCE at voltage level, by setting the attribute ‘ATCC existence’ to ‘Yes’
(1).
1. Then an extra ‘ATCC’ tab-pane appears with the following attributes to update:
‘General’ attributes:
‘voltage targets’ attributes
2. voltage target by default
corresponds to (param 40) in chapter 6.5.1.7 List of configurable parameters
3. voltage target 1
corresponds to (param 35) in chapter 6.5.1.7 List of configurable parameters
4. voltage target 2
corresponds to (param 36) in chapter 6.5.1.7 List of configurable parameters
5. voltage target 3
corresponds to (param 37) in chapter 6.5.1.7 List of configurable parameters
6. voltage target 4
corresponds to (param 38) in chapter 6.5.1.7 List of configurable parameters
7. voltage target 5
corresponds to (param 39) in chapter 6.5.1.7 List of configurable parameters
C264/EN AP/B30 Application

Page 332/396 MiCOM C264/C264C

‘regulation’ attributes
8. voltage target ramping rate (kV/mn)
corresponds to (param 31) in chapter 6.5.1.7 List of configurable parameters
9. max tap change rate (kV/min)
corresponds to (param 32) in chapter 6.5.1.7 List of configurable parameters
10. voltage deadband to end tapping
corresponds to (param 33) in chapter 6.5.1.7 List of configurable parameters
11. voltage deadband to initiate tapping
corresponds to (param 34) in chapter 6.5.1.7 List of configurable parameters
When a voltage level is concerned by an AVR function, do not forget to set correctly its
attribute ‘nominal value (kV)’ (refer to chapter 6.1.3 Defining Voltage level). It is used for
transformer nominal ratio computation.

(1)

(2)

(3)

(4)

(5)

(6)
(7)

(8)
(9)
(10)
(11)

FIGURE 362: SETTING AVR FUNCTION AT VOLTAGE LEVEL

Application C264/EN AP/B30

MiCOM C264/C264C Page 333/396

6.5.2.3 Defining AVR function needs at busbar level

For each busbar bay concerned by an AVR function, extra AVR configuration must be done.
For details about busbar bay creation, refer to chapter 6.1.4 Defining Bay.
This is done under SCE via the “Object entry” area at busbar level by clicking on mouse’s
right button.

(1)

FIGURE 363: ADDING AVR FUNCTION NEEDS AT BUSBAR LEVEL

Once added, AVR busbar features must be set at SCE level:
‘General’ attributes:
1. Setpoint ponderation
corresponds to (param 22) in chapter 6.5.1.7 List of configurable parameters
2. Priority
corresponds to (param 23) in chapter 6.5.1.7 List of configurable parameters
‘line drop compensation (if setpoint adjustement)’ attributes
3. Resistive coefficient
corresponds to (param 20) in chapter 6.5.1.7 List of configurable parameters
4. Reactive multiplier
corresponds to (param 21) in chapter 6.5.1.7 List of configurable parameters
‘line drop compensation (if voltage adjustement)’ attributes
5. Resistive coefficient
corresponds to (param 20) in chapter 6.5.1.7 List of configurable parameters
6. Reactive multiplier
corresponds to (param 21) in chapter 6.5.1.7 List of configurable parameters

(1)
(2)
(3)
(4)
(5)
(6)

FIGURE 364: SETTING GENERAL BUSBAR FEATURES TO AVR

C264/EN AP/B30 Application

Page 334/396 MiCOM C264/C264C

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

(DPT_Bb 1)
(DPT_Bb 2)
(DPT_Bb 3)

(DPT_Bb 4)
(DPT_Bb 5)
(DPT_Bb 6)
(DPT_Bb 7)

(DPT_Bb 8)
(DPT_Bb 9)
(DPT_Bb 10)
(DPT_Bb 11)
(DPT_Bb 12)
(DPT_Bb 13)
(DPT_Bb 14)
(DPT_Bb 15)
(DPT_Bb 16)
(DPT_Bb 17)

(DPT_Bb 18)

FIGURE 365: MANDATORY DATAPOINTS FOR AVR AT BUSBAR LEVEL

Application C264/EN AP/B30

MiCOM C264/C264C Page 335/396

6.5.2.4 Defining AVR function needs at transformer level

For details about transformer bay (and subsequent transformer module) creation, refer to
chapters 6.1.4 Defining Bay.
For each transformer concerned by an AVR function, extra AVR configuration must be done
at several levels:

• Set properly the following features for transformer module (refer to chapter 6.1.5.7
Defining transformer):

− ‘Transformer type’ attribute

corresponds to (param 27) in chapter 6.5.1.7 List of configurable parameters

− ‘Power value’ attribute (from 1 to 300 MVA),

corresponds to (param 25) in chapter 6.5.1.7 List of configurable parameters

− ‘Impedance’ attribute, whose unit is a percent of value for S=100 MVA (from 0,01
to 24,99 by step 0,01)
corresponds to (param 26) in chapter 6.5.1.7 List of configurable parameters

− MCB position SPS or DPS is mandatory

• Add and configure a Tap-changer built-in function for the transformer module (refer to
chapter 6.4 Defining Tap changer built-in function), with the following features:

− Raise/Lower DPC is mandatory

− Tap in progress SPS is mandatory

− MCB open SPC is mandatory

• Add and configure an ‘ATCC fct needs’ object for transformer, via the “Object entry”
area at transformer module level by clicking on mouse’s right button (1):

(1)

FIGURE 366: ADDING AVR FUNCTION NEEDS AT TRANSFORMER LEVEL

Once added, the features of AVR function needs for transformer must be set at SCE level:
‘General’ attributes:
‘Tpi range’ attributes
1. Up range
corresponds to (param 28 – upper value) in chapter 6.5.1.7 List of configurable
parameters
2. Down range
corresponds to (param 28 – lower value) in chapter 6.5.1.7 List of configurable
parameters
C264/EN AP/B30 Application

Page 336/396 MiCOM C264/C264C

‘Inhibition conditions’ attributes:

3. Overcurrent ratio
corresponds to (param 30) in chapter 6.5.1.7 List of configurable parameters

(1)
(2)

(3)

FIGURE 367: SETTING GENERAL TRANSFORMER FEATURES TO AVR

When adding an AVR function needs at transformer level, the following mandatory
datapoints are automatically created and must be configured (see chapter 5 DEFINING
DATAPOINT):
(DPT_Trf 1) ATCC on/off
(DPT_Trf 2) ATCC homing
(DPT_Trf 3) ATCC hunting
(DPT_Trf 4) TAP bad TCIP
(DPT_Trf 5) TAP long TCIP
(DPT_Trf 6) TAP invalid
(DPT_Trf 7) Run away
(DPT_Trf 8) ATCC disc eqpt
(DPT_Trf 9) ATCC local bay
(DPT_Trf 10) MCB trip
(DPT_Trf 11) ATCC overcurrent
(DPT_Trf 12) ATCC overvoltage
(DPT_Trf 13) ATCC low-voltage
(DPT_Trf 14) ATCC inv voltage
(DPT_Trf 15) Second. voltage
(DPT_Trf 16) Second. current
(DPT_Trf 17) Second. active P
(DPT_Trf 18) Second. react. Q
Application C264/EN AP/B30

MiCOM C264/C264C Page 337/396

(DPT_Trf 1)
(DPT_Trf 2)
(DPT_Trf 3)
(DPT_Trf 4)
(DPT_Trf 5)
(DPT_Trf 6)
(DPT_Trf 7)
(DPT_Trf 8)
(DPT_Trf 9)
(DPT_Trf 10)
(DPT_Bb 11)
(DPT_Trf 12)
(DPT_Trf 13)
(DPT_Trf 14)
(DPT_Trf 15)
(DPT_Trf 16)
(DPT_Trf 17)
(DPT_Trf 18)

FIGURE 368: MANDATORY DATAPOINTS FOR AVR AT TRANSFORMER LEVEL

C264/EN AP/B30 Application

Page 338/396 MiCOM C264/C264C

6.5.2.5 Defining electrical topology for AVR function

For correct behaviour of AVR function, electrical topology of the LV side, including
connection of the transformer to the busbar and coupling of busbars into the LV level must
be defined.
Any electrical topology can be defined by modules interconnected by nodes.
A node is in relation with at least on module. The most common “node” is busbars.
Electric modules are mostly dipoles. Switchgears and circuit-breakers are connected to two
nodes. Special module cases are:

• motor/generator that are connected to only one node,

• Line arrival that is a node

• special (german) double switch that is in fact association of earth switch and
disconnector

• transformer connected to 3 nodes but the third node is reserved to neutral

compensation.
At SCE level, nodes are special attributes of module, whose values are given by integers.
Each identified node in the electrical topology has a unique arbitrary value. Two
interconnected modules share the same node value. The best practice to value nodes is to
do it directly from the substation electrical diagram.

obsolete

FIGURE 369: IDENTIFYING NODES IN ELECTRICAL DIAGRAM (E.G.)

Application C264/EN AP/B30

MiCOM C264/C264C Page 339/396

Then, this manual approach of nodes identification must be projected at SCE electrical
object level:

• “Busbar” bay, where one node reference must be filled (1),

• “External line” module of “Feeder” bay, where one node reference must be filled (2),

• “Circuit-breaker” and “Switchgear” module, where two node reference must be filled
(3),

• “Transformer” module, where at least two node must be filled, and a extra one in case
of neutral compensation (4),

• “Capacitor” and “inductor” module, used for neutral compensation , where one node
reference must be filled (5) and corresponds to the neutral node of the associated
transformer.

(1)

FIGURE 370 : SETTING BUSBAR NODE REFERENCE (AVR FUNCTION)

(2)

FIGURE 371 : SETTING EXTERNAL LINE NODE REFERENCE (AVR FUNCTION)

C264/EN AP/B30 Application

Page 340/396 MiCOM C264/C264C

(3)

FIGURE 372 : SETTING CIRCUIT-BREAKER NODE REFERENCES (AVR FUNCTION)

(3)

FIGURE 373 : SETTING TRANSFORMER NODE REFERENCES (AVR FUNCTION)

Application C264/EN AP/B30

MiCOM C264/C264C Page 341/396

6.6 Defining electrical regulation by user function

PACiS allows the user to configure specific control sequences or automations (e.g. switching
sequences, busbar transfer, load shedding, GIS-pressure supervision, etc …) during the
configuration phase.
To do that, there are two main solutions:

• Using ISaGRAF workbench for slow automations, where the execution of the
automation is cyclic, based on a cycle that can not be less than 50 ms.

• Using extended logical function modelling (boolean, timer, bistable functions) via FBD
workbench, where the execution is event-driven.
User function can be put at any level of the electrical topology except Site. Moreover, slow
automation is unavailable at module level. User function must always specify on which
MiCOM C264 Computer it runs.
Extra solutions for simpler needs exist at configuration level (they could be seen as
restriction of particular FBD functions):

• Group modelling :
SPS production based on a pre-defined boolean function working on a set of
datapoint,

• xPS-xPC association:
on a particular state of xPS, ability to control a given xPC

• SPS-DPS association:
DPS production based on the synthesis of 2 SPS

• Interlocking definition:
production of virtual SPS datapoints used to control opening and/or closure of
modules. These virtual datapoints are defined through specific FBD logical diagrams
where inputs are generally breaker and switch positions.

• Automatic/manual dependency set at control level (SPC, DPC or SetPoint):

When a control is linked to a SPS or DPS via the automatic/manual dependency,
control is refused if the SPS (resp. DPS) is in the SET (resp. CLOSED) state.
6.6.1 Defining a FBD fast automation
To define a FBD fast automation, the three following steps must be done:

• FBD interface definition at SCE level:

− FBD function ‘header’ creation

− creation of input plugs, that will be linked to SPS, DPS, MV, MPS, SPC or DPC
(fast automations take into account the logical value of these datapoints, defined
for interlocking management), added as sub-objects to this header.

− creation of output plugs, that will be linked to SPC, DPC (control of relays) or to a
SPS (production of SPS real-time value), added as sub-objects to this header.

• FBD body (coding in PSL) definition via launching at SCE level the FBD editor
(contextual menu on the FBD interface object) and doing diagram edition of boolean,
timer and bistable functions, and links to input/output plugs.

• Effective linking of input and output plugs to existing datapoints

C264/EN AP/B30 Application

Page 342/396 MiCOM C264/C264C

6.6.1.1 Creating a FBD fast automation (header definition)

An addition of a FBD fast automation is done under SCE via the “Object entry” area at any
level of the electrical topology (except Site) by clicking on mouse’s right button.
For more details about electrical topology creation, refer to chapter 6.1 Defining electrical
topology.

obsolete

C0247ENa

FIGURE 374: ADDING A FBD FAST AUTOMATION

(E.G. FOR FEEDER BAY LEVEL)
Once added, FBD fast automation features must be set at SCE level:
1. Fill the relation ‘runs on’, giving which MiCOM C264 Computer PLC will manage the
automation. This relation is automatically filled by SCE if FBD automation is located
under a bay whose MiCOM C264 Computer manager has ever been entered (for
details about MiCOM C264 Computer manager of a bay refer to chapter 6.1.4 Defining
Bay)
2. Short and long names of the fast automation used for internal SCE identification

(1)

(2)

FIGURE 375: SETTING FBD FAST AUTOMATION FEATURES

Application C264/EN AP/B30

MiCOM C264/C264C Page 343/396

6.6.1.2 Creating FBD input plug (header definition)

An addition of a FBD input plug is done under SCE via the “Object entry” area at the FBD
automation level by clicking on mouse’s right button.

FIGURE 376: ADDING A FBD INPUT PLUG

Once added, FBD input plug features must be set at SCE level:
1. Short and long names of the fast automation used for identification in FDB editor

(1)

FIGURE 377: SETTING FBD INPUT PLUG ATTRIBUTES

6.6.1.3 Creating FBD output plug (header definition)
An addition of a FBD output plug is done under SCE via the “Object entry” area at the FBD
automation level by clicking on mouse’s right button.

FIGURE 378: ADDING A FBD OUTPUT PLUG

C264/EN AP/B30 Application

Page 344/396 MiCOM C264/C264C

Once added, FBD output plug features must be set at SCE level:
1. Short and long names of the fast automation used for identification in FDB editor

(1)

FIGURE 379: SETTING FBD OUTPUT PLUG ATTRIBUTES

6.6.1.4 Using FBD editor (body definition)
The launching of the FBD editor is done at FBD automation level via its contextual menu
(right clic).

(1)

FIGURE 380: LAUNCHING FBD EDITOR

Once launched, FBD editor allows diagram edition of the automation. For details about FBD
user manual refer to <ADU SCE User Manual>
Application C264/EN AP/B30

MiCOM C264/C264C Page 345/396

FIGURE 381: USING FBD EDITOR

6.6.1.5 Linking datapoints to FBD inputs and outputs
To assign a datapoint to a FBD input:

• Add the relation ‘uses <XXX>’ (1) at FBD input level, where XXX corresponds to the
datapoint kind (SPS, DPS, MPS, MV, SPC or DPC)

• Fill the relation with the relevant datapoint

(1)

FIGURE 382: LINKING A FBD INPUT TO A DATAPOINT

C264/EN AP/B30 Application

Page 346/396 MiCOM C264/C264C

To assign a datapoint to a FBD output:

• Add the relation ‘controls <XXX>’ (1) or ‘produces SPS’ at FBD input level, where XXX
corresponds to the control datapoint kind (SPC or DPC)

• Fill the relation with the relevant datapoint

(1)

FIGURE 383: LINKING A FBD OUTPUT TO A DATAPOINT

Several datapoints can be assigned to the same FBD output.
Configuration rules and checks

• For one "FBD input" plug, only one relation is allowed.

• For one "FBD output" plug :

- the count of relations towards DPC or SPC Datapoints must be ≤ 4
- the count of relations towards SPS Datapoints must be ≤ 4

• A "DPC" or "SPC" Datapoint can be linked to an Output plug of a FBD Automation

through the relation "controls DPC" or "controls SPC". These relations are not
compatible with the following ones :
- relations defining the Control Source, except the "…wired on" relation(s)
- relation "has for UCA2/IEC address" whatever the link type
- relation "has for SCADA address".
- relation "is controlled on state change of".
- relation "has for AutoManu dependency".
- relation "has for feedback".
- relation "has for local/remote dependency".
Application C264/EN AP/B30

MiCOM C264/C264C Page 347/396

6.6.2 A "DPC" or "SPC"

Datapoint can be linked to an Input plug of a FBD Automation through the relation "uses
DPC" or "uses SPC". These relations are not compatible with the following ones :
- relations defining the Control Source : "…wired on"
- relation defining the Control Source : "has for IED address"Defining an ISaGRAF slow
automation
Slow automation modelling is articulated around a ‘Slow automation’ object that corresponds
to an ISaGRAF project.Slow automation can own datapoints for status, control of automation
itself (automation management). For instance, a load-shielding automation can have a
control to put it in/out of service and a relevant status.
They also reference via links datapoints located in system or electrical topologies. There are
two kinds of link:

• ‘client’ link, that means that the slow automation uses the datapoint that is acquired or
managed outside the ISaGRAF automation. For instance, the load-shielding
automation can be client of some ‘circuit-breaker status’ input datapoints and some
‘circuit-breaker control’ output datapoints;

• ‘server’ link, that means that the slow automation produces or manages the datapoint.
For instance, a slow automation can be used to produce the sum of feeder
measurements. This sum is also a measurement located at voltage level for instance.
To define a slow automation, the three following steps must be done:

• Interface definition of the slow automation at SCE level:

− Slow automation ‘header’ creation

− If required, creation of datapoints at slow automation level, used for the function
management

− Creation of the client links for the slow automation,

− Creation of the server links for the slow automation,

• Slow automation body definition via launching at SCE level the ISaGRAF editor
(contextual menu on the slow automation interface object) and using available
languages and previously client/server defined links.

• Effective client/server links entering to existing datapoints

C264/EN AP/B30 Application

Page 348/396 MiCOM C264/C264C

6.6.2.1 Creating an ISaGRAF slow automation (header definition)

An addition of an ISaGRAF slow automation is done under SCE via the “Object entry” area
at any level of the electrical topology (except Site and module) by clicking on mouse’s right
button.
For more details about electrical topology creation, refer to chapter 6.1 Defining electrical
topology.

obsolete

C0248ENa

FIGURE 384: ADDING AN ISaGRAF SLOW AUTOMATION

(E.G. FOR FEEDER BAY LEVEL)
Once added, ISaGRAF slow automation features must be set at SCE level:
1. Fill the relation ‘runs on’, giving which MiCOM C264 Computer PLC will manage the
automation. This relation is automatically filled by SCE if slow automation is located
under a bay whose MiCOM C264 Computer manager has ever been entered (for
details about MiCOM C264 Computer manager of a bay refer to chapter 6.1.4 Defining
Bay)
2. Short and long names of the slow automation used for logging and alarm

(1)

(2)

FIGURE 385: SETTING ISaGRAF SLOW AUTOMATION FEATURES

Application C264/EN AP/B30

MiCOM C264/C264C Page 349/396

6.6.2.2 Adding specific datapoints to slow automation (interface definition)

An addition of a slow automation datapoint is done under SCE via the “Object entry” area at
slow automation level by clicking on mouse’s right button.
For more details about datapoints and their configuration, refer to chapter 5 DEFINING
DATAPOINT.

FIGURE 386: ADDING DATAPOINTS TO SLOW AUTOMATION

Slow automation datapoint is integrally produced or managed by the slow automation and
subsequently by ISaGRAF. It can not be linked to another acquisition or control source and
the ISaGRAF project must update/run its value changes or controls. Slow automation input
datapoint are stored in a non-volatile memory at MiCOM C264 Computer level to restart on
their last known values in case of MiCOM C264 Computer reboot.
C264/EN AP/B30 Application

Page 350/396 MiCOM C264/C264C

6.6.2.3 Creating ISaGRAF client link (interface definition)

An addition of an ISaGRAF client is done under SCE via the “Object entry” area at the slow
automation level by clicking on mouse’s right button and adding a ‘is client of’ relation.
Choose the correct relation depending on datapoint kind that will be used.

FIGURE 387: ADDING A ISaGRAF CLIENT LINK

Application C264/EN AP/B30

MiCOM C264/C264C Page 351/396

6.6.2.4 Creating ISaGRAF server link (interface definition)

An addition of an ISaGRAF server is done under SCE via the “Object entry” area at the slow
automation level by clicking on mouse’s right button and adding a ‘manages’ relation.
Choose the correct relation depending on datapoint kind that will be managed.

FIGURE 388: ADDING A ISaGRAF CLIENT LINK

C264/EN AP/B30 Application

Page 352/396 MiCOM C264/C264C

6.6.2.5 Using ISaGRAF editor (body definition)

The launching of the ISaGRAF editor is done at slow automation level via its contextual
menu (right clic).

(1)

FIGURE 389: LAUNCHING ISaGRAF EDITOR

Once launched, ISaGRAF editor allows diagram edition of the automation. For details about
ISaGRAF workbench and SCE datapoint coupling, refer to 8 Annex A: Coupling SCE data
model and ISAGRAF.

FIGURE 390: USING ISAGRAF EDITOR

6.6.2.6 Linking datapoints to ISaGRAF client and server links
Just fill the relation ‘is client of’ or ‘manages’ with the relevant datapoint
Application C264/EN AP/B30

MiCOM C264/C264C Page 353/396

6.6.3 Defining a group

A group is a logical OR, AND, NOR or NAND combination of components whose kind is
SPS, DPS or groups. A component can belong to several groups. Resulting datapoint
associated to a group is a SPS object called ‘Group SPS’ in data modelling.
Group SPS can only belongs to bays or modules. The MiCOM C264 Computer that
manages the bay (of eventually the bay of the module) always computes it. Its composition
description is done via linking it to SPS, DPS, or Group SPS.
A group SPS can be seen as a particular fast automation reduced to one boolean function
with one implicit output plug (the group SPS itself) and input plugs corresponding to each
component of the group.
An addition of a group SPS is done under SCE via the “Object entry” area at bay or module
level of the electrical topology by clicking on mouse’s right button.
For more details about electrical topology creation, refer to chapter 6.1 Defining electrical
topology.

FIGURE 391: ADDING A GROUP SPS

(E.G. FOR FEEDER BAY LEVEL)
Once added, Group SPS features must be set at SCE level, as SPS datapoint. For details
about SPS datapoint configuration, refer to chapter 5.1.2 Defining SPS datapoint.
Nevertheless, the specific attribute ‘group type’ (1) must be set for the group. It corresponds
to the logical function (OR, AND, NOR or NAND) applied on all the components of the group.
C264/EN AP/B30 Application

Page 354/396 MiCOM C264/C264C

(1)

FIGURE 392: SETTING ‘GROUP TYPE’ ATTRIBUTE TO A GROUP SPS

To assign a component to a group (SPS, DPS or group):

• Add the relation ‘contains the <XXX>’ (1) at Group SPS level, where XXX corresponds
to the datapoint kind (SPS or DPS)

• Fill the relation with the relevant datapoint

(1)

FIGURE 393: ADDING A COMPONENT TO A GROUP

Application C264/EN AP/B30

MiCOM C264/C264C Page 355/396

6.6.4 Controlling xPC by xPS change of state

For specific needs, some SPS or DPS can acts on SPC or DPC. This relation is called xPS-
xPC association. Such an acted xPC does not necessary need a channel for wiring. It can be
a xPC used for automation management for instance.
The link defines for each state of the xPS which order must be sent.
To create such a relation:

• Add the relation ‘controls on state change’ (1) at SPS/DPS level; two relations are
available depending on control kind to act (SPC or DPC). Choose the correct one.

• Fill the relation with the relevant SPC or DPC (2)

• Set the relation attributes (3) giving for each state of the xPS, the order to send:
None, Open (resp. Off) or Close (resp. On) for DPC (resp. SPC)

(1)

(2)

(3)

FIGURE 394: CONTROLLING XPC THROUGH XPS (E.G.)

C264/EN AP/B30 Application

Page 356/396 MiCOM C264/C264C

6.6.5 Producing DPS from 2 SPS

For specific needs, two SPS (one for open state, and the other for closed state) can be used
to manage a DPS. This relation is called SPS-DPS association.
To produce a DPS from 2 SPS:

• Create the 3 datapoints and configure them (see chapter 5 DEFINING DATAPOINT)

• At the DPS level, add the relations ‘has open state given by’ (1) and ‘has closed state
given by’ (2)

• Fill the 2 relations with the previously created SPS datapoint

(2)

(1)

FIGURE 395: PRODUCING DPS FROM 2 SPS (E.G.)

6.6.6 Defining interlocking
Any DPC (or SPC) belonging to a bay or module can have interlocking equation for opening
order (Off order for SPS) and/or closing order (On order for SPC).
Interlocking equation corresponds to a logical function that must be ‘true’ to send the order.
In data modelling, interlocking equation are put under SPC or DPC by adding specific SPS:

• ‘Off interlock SPS’ and ‘On interlock SPS’ for SPC,

• ‘Open interlock SPS’ and ‘Close interlock SPS’ for DPC

These SPS contain the logical function definition of the interlocking, that is coded with the
FBD editor.
Interlocking equation diagrams seem FBD fast automation diagrams, except that:

• Timer, bistable function are unusable,

• There is no output plug.

An addition of an interlock SPS is done under SCE via the “Object entry” area at SPC/DPC
datapoint level by clicking on mouse’s right button.
For more details about electrical topology creation, refer to chapter 6.1 Defining electrical
topology.
Application C264/EN AP/B30

MiCOM C264/C264C Page 357/396

FIGURE 396: ADDING A INTERLOCK SPS

(E.G. FOR MODULE DPC LEVEL)
Once added, interlock SPS features must be set at SCE level, as SPS datapoint. For details
about SPS datapoint configuration, refer to chapter 5.1.2 Defining SPS datapoint.
To define interlocking equation for a interlock SPS:

• Add at interlock SPS level, a FBD interlock object (1)

• Configure this FBD interlock (refer to chapter 6.6.1 Defining a FBD fast automation),
with the existing following restrictions:

− only input plugs are available for its interface definition.

− for its body description via FBD editor, timer and bistable functions do not exist.

obsolete

(1)

FIGURE 397: DEFINIG INTERLOCKING EQUATION FOR A INTERLOCK SPS

C264/EN AP/B30 Application

Page 358/396 MiCOM C264/C264C

6.6.7 Defining an automatic/manual dependency

Automatic/manual dependency can be set at control level (SPC, DPC or SetPoint):
When a control is linked to a SPS or DPS via the automatic/manual dependency, control is
refused if the SPS (resp. DPS) is in the SET (resp. CLOSED) state.To create an
automatic/manual dependency:

• Add the relation ‘has for AutoManu dependency’ (1) at control level; two relations are
available depending on the input kind setting the dependency (SPS or DPS). Choose
the correct one.

• Fill the relation with the relevant SPS or DPS (2)

(1)

FIGURE 398: DEFINING AN AUTOMATIC/MANUAL DEPENDENCY (E.G.)

Configuration rules and checks

• For each "DPC", "SPC" or "Setpoint" Datapoint, 2 relations "has for AutoManu
dependency" are available, but they are mutually exclusive.
Application C264/EN AP/B30

MiCOM C264/C264C Page 359/396

7. DEFINING MiCOM C264 COMPUTER LOCAL HMI

All kinds of MiCOM C264 Computers (except C364), can have a GHU200 board for led
managing and possible local bay mimic panel animations in case of complete GHU200
board (refer to chapter 4.4.2.2 Setting specific features of GHU200 board),.
7.1 Defining bitmap table
To define MiCOM C264 Computer bay mimics, bitmaps are used. Their definition is located
at graphic root of the data modelling.
At MiCOM C264 Computer bay mimic definition level, objects only reference these bitmaps.
So it is an easier way to propagate a bitmap change for instance to all objects that reference
it.
At SCE level, bitmap object definition is extended to embed animation: up to 5 elementary
static bitmaps can be grouped in a bitmap object:

• one (mandatory) for default representation,

• one for ‘open’ (or reset) representation

• one for ‘closed’ (or set) representation

• one for ‘open withdrawn’ representation

• one for ‘closed withdrawn’ representation

Each representation corresponds to a filename containing the static bitmap definition.
An addition of a bitmap definition is done under SCE via the “Object entry” area at Bitmap
table level of the graphical topology by clicking on mouse’s right button.

FIGURE 399: ADDING A BITMAP

Once added, bitmap features must be set at SCE level:
1. Short and long names of the bitmap used for internal SCE identification
2. Reference index of the bitmap,
that must be unique for the set of defined bitmaps. This index will be used in bay
mimic definition as described previously.
3. Type (Single or 5-uple):
single is used for static bitmap definition,
5-uple allows dynamic bitmap definition as described previously
4. Filename by default of the bitmap:
corresponds to the filename containing the bitmap definition used for default
representation
5. Filename for open (reset) state, visible if type is set to 5-uple,
corresponds to the filename containing the bitmap definition used for open state
representation
C264/EN AP/B30 Application

Page 360/396 MiCOM C264/C264C

6. Filename for closed (set) state, visible if type is set to 5-uple,

corresponds to the filename containing the bitmap definition used for closed state
representation
7. Filename for withdrawn open state, visible if type is set to 5-uple,
corresponds to the filename containing the bitmap definition used for withdrawn open
state representation
8. Filename for withdrawn closed state, visible if type is set to 5-uple,
corresponds to the filename containing the bitmap definition used for withdrawn closed
state representation

(1)

(2)
(3)
(4)
(5)
(6)
(7)
(8)

FIGURE 400: SETTING BITMAP ATTRIBUTES

Attributes (7) and (8) can be omitted if breakers and switchgears represented in bay mimic
are not concerned with withdrawn information.
To set a file name (attributes (4) to (8)) and define graphically a bitmap:

• select the attribute

• edit graphically a bitmap using the bitmap editor at SCE level

• save the graphical definition of the bitmap by giving a file name in bitmap editor
For details about bitmap editor usage refer to SCE user’s manual.
Application C264/EN AP/B30

MiCOM C264/C264C Page 361/396

FIGURE 401: USING BITMAP EDITOR

Color usage in bitmap editor are not significant for MiCOM C264 Computer monochrome
LCD.Configuration rules and checks

• The "reference index" attribute value of each "Bitmap" of the "Bitmap table" must be
unique.

• Depending on the "type" attribute value, 1 or 5 PNG file(s) can be linked to a Bitmap.
For each one, the bitmap size must be ≤ 512 bytes.
7.2 Defining MiCOM C264 Computer workspace
Via a complete GHU200 board (refer to chapter 4.4.2.2 Setting specific features of GHU200
board), each MiCOM C264 Computer with local HMI references a workspace that groups its
bay mimic definitions. MiCOM C264 Computer workspaces can not be shared by several
MiCOM C264 Computers because mimics are local to bays managed by a specific MiCOM
C264 Computer.
Up to 24 bay mimics can be put in a MiCOM C264 Computer workspace, and up to 2 mimics
can be linked to the same bay.
Usual labels are used by MiCOM C264 Computer local HMI (LHMI). They are located for all
MiCOM C264 Computer LHMI in one object grouping all translatable labels, located in
“MiCOM C264 Computer workspaces” folder in Graphic topology.
C264/EN AP/B30 Application

Page 362/396 MiCOM C264/C264C

7.2.1 Settings LHMI labels

To modify an usual label used at MiCOM C264 Computer LHMI level, just select and update
the corresponding attribute at LHMI labels object.

FIGURE 402: SETTINGS LHMI LABELS

7.2.2 Creating a workspace
An addition of a workspace is done under SCE via the “Object entry” area at graphic level by
clicking on mouse’s right button.

FIGURE 403: ADDING A MiCOM C264 COMPUTER WORKSPACE

Once added, MiCOM C264 Computer workspace general features must be set at SCE level:

• Precise which GHU200 board is concerned by created workspace by filling the relation
‘has for workspace’ at concerned GHU board level (refer to chapter 4.4.2.2 Setting
specific features of GHU200 board).

• Setting the short and long name (1) attributes of the workspace used for internal SCE
identification,

• Setting ‘local/remote password usage’ (Yes/No) attribute (2), to precise if password is

required to set Local/remote for bays managed by the MiCOM C264 Computer.

(1)

(2)

FIGURE 404: SETTING MiCOM C264 COMPUTER WORKSPACE ATTRIBUTES

Application C264/EN AP/B30

MiCOM C264/C264C Page 363/396

7.3 Defining MiCOM C264 Computer bay mimic

7.3.1 Creating a MiCOM C264 Computer bay mimic
An addition of a MiCOM C264 Computer bay mimic is done under SCE via the “Object entry”
area at MiCOM C264 Computer workspace level by clicking on mouse’s right button.

FIGURE 405: ADDING A MiCOM C264 COMPUTER BAY MIMIC

Once added, bay mimic general features must be set at SCE level:
1. Short and long names of the bay mimic used for internal SCE identification
2. Define with representation is used for bargraph associated to MV datapoint assigned
to bay mimic (refer to chapter 7.3.4 Assigning MV to bay mimic): Horizontal, vertical or
none.
3. Precise if module short names are displayed at mimic level (Yes/No), when a module
is represented on bay mimic (refer to chapter 7.3.3 Defining dynamic part: pre-defined
dynamic text, generic module representation, transformer representation)
4. Fill the relation ‘represents’, giving which bay is represented by the mimic (for details
about bay refer to chapter 6.1.4 Defining Bay)
5. If necessary, set the attribute ‘mimic rank’ of the ‘represents’ relation to correct value.
This attribute is used when 2 mimics are configured to display an entire bay: as bay is
split in 2 representations, the ‘mimic rank’ attribute gives their display rank at MiCOM
C264 Computer LHMI level (1 or 2).
C264/EN AP/B30 Application

Page 364/396 MiCOM C264/C264C

(1)

(2)

(3)

(4)

(5)

FIGURE 406: SETTING BAY MIMIC FEATURES

When adding a bay mimic at workspace level, its core structure (canvas) is automatically
created and displayed at SCE level, via bay mimic editor and in SCE tree browser. Its core
structure consists of:
1. Reserved zone for bay name display
2. Reserved zone for bay local/remote display ((2’) in tree browser)
3. Reserved zone for ‘interlocking bypass in progress’ information ((3’) in tree browser)
4. Reserved zone for ‘synchrocheck bypass in progress’ information ((4’) in tree browser)
5. Configurable zone for graphical representation of the bay (static and dynamic parts)
6. Reserved zone for message
Application C264/EN AP/B30

MiCOM C264/C264C Page 365/396

(1)

(2)

(3)

(4)

(5)

(6)

(3‘)

(2‘)

(4‘)

FIGURE 407: CORE STRUCTURE OF BAY MIMIC

For more details about MiCOM C264 Computer LCD usage, refer to document User
Interface (coded HI for Human Interface) of MiCOM C264 documentation binders.
The configurable zone of a bay mimic can be split in two parts:

• A static part with no real-time animation

• A dynamic part with real-time animated representations.

C264/EN AP/B30 Application

Page 366/396 MiCOM C264/C264C

Configuration rules and checks

• The MiCOM C264 Computer managing a bay represented by a "Bay mimic" must be
the same as the one linked to the "Comp. workspace" (MiCOM C264 Computer
workspace) of this "Bay mimic".

• A bay can be represented by 0, 1 or 2 "Bay mimic". Each "represents" relation has an

attribute "mimic rank for the set of bay mimic". In the case of 2 relations, each attribute
value must be unique.

• For a MiCOM C264 Computer, the maximum count of managed bays (relation "is
managed by") which are linked to a "Bay mimic" (relation "represents"), is 12.

• Limits of the count of symbols:

Graphic
Comp. workspace
Bay mimic max = 24 / Comp. workspace
LHMI Transformer max = 9 / Bay mimic
LHMI Gen module
LHMI bitmap max = 5 / Bay mimic
LHMI line max = 30 / Comp. workspace max = 18 / Bay mimic
LHMI text max = 5 / Bay mimic (1 is reserved for the Bay name) + 1 reserved
… for the Bay name
S0285ENa

7.3.2 Defining static part: line, bitmap, fixed text

The static part of a MiCOM C264 Computer bay mimic is described via graphical basic
shapes:

• LHMI line: horizontal or vertical line with configurable thickness and length,

• LHMI bitmap: bitmap that references a bitmap object in the bitmap table (see 7.1
Defining bitmap) where default representation is only taken into account,

• Fixed text: multi-lingual fixed text

Once added, these elements automatically appears in the window of the bay mimic editor at
SCE level.
Configuration rules and checks

• The coordinates (x, y) of a symbol must not be located outside the mimic area.
7.3.2.1 Adding a line
An addition of a line in bay mimic is done under SCE via the “Object entry” area at bay mimic
level by clicking on mouse’s right button.

FIGURE 408: ADDING A LINE IN MiCOM C264 COMPUTER BAY MIMIC

Application C264/EN AP/B30

MiCOM C264/C264C Page 367/396

Once added, line attributes must be set at SCE level:

1. Short and long names of the line used for internal SCE identification
2. X-coordinate
3. Y-coordinate
4. Length (in LCD pixel)
5. Orientation: Horizontal or vertical
6. Thickness (from 1 to 8 LCD pixel)

(1)

(2)

(3)

(4)
(5)

(6)

FIGURE 409: SETTING LINE ATTRIBUTES

X-coordinate, Y-coordinate and length of a line can be directly managed using mouse in bay
mimic editor (for detail, refer to SCE user’s manual)
7.3.2.2 Adding a bitmap
An addition of a bitmap in bay mimic is done under SCE via the “Object entry” area at bay
mimic level by clicking on mouse’s right button.

FIGURE 410: ADDING A BITMAP IN MiCOM C264 COMPUTER BAY MIMIC

C264/EN AP/B30 Application

Page 368/396 MiCOM C264/C264C

Once added, bitmap attributes must be set at SCE level:

1. Short and long names of the line used for internal SCE identification
2. X-coordinate
3. Y-coordinate
4. Bitmap reference: corresponds to a link in the bitmap table (refer to chapter 7.1
Defining bitmap table)

(1)

(2)

(3)

(4)

FIGURE 411: SETTING BITMAP ATTRIBUTES

X-coordinate, Y-coordinate of a bitmap can be directly managed using mouse in bay mimic
editor (for detail, refer to SCE user’s manual)
Configuration rules and checks

• The link from an element to its bitmap is defined with the attribute : "bitmap reference".
The value of this attribute must refer to an existing bitmap in the "Bitmap table".
7.3.2.3 Adding a fixed text
An addition of a fixed text in bay mimic is done under SCE via the “Object entry” area at bay
mimic level by clicking on mouse’s right button.

FIGURE 412: ADDING A FIXED TEXT IN MiCOM C264 COMPUTER BAY MIMIC
Application C264/EN AP/B30

MiCOM C264/C264C Page 369/396

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

1. Fixed text value: text appearing at mimic level
2. X-coordinate
3. Y-coordinate

(1)

(2)

(3)

FIGURE 413: SETTING BITMAP ATTRIBUTES

X-coordinate, Y-coordinate of a fixed text can be directly managed using mouse in bay mimic
editor (for detail, refer to SCE user’s manual). Text area length at bat mimic is automatically
deduced from text value length (attribute (1)).
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation, transformer
representation
To define dynamic part of MiCOM C264 Computer bay mimics, 3 kinds of objects are
available:

• Pre-defined dynamic text, used:

− to display local/remote and SBMC status of the bay

− to manage Synchrocheck and interlock bypass during control sequence on the

bay

− to display time and synchronisation status

Generic module representation,
used to display module status, linked to a specific SPS or DPS electrical datapoint. Implicit
link to possible xPC associated datapoint is given to MiCOM C264 Computer for command
purpose at local HMI level, via the existence of the relation ‘is feedback of’ between the xPS
and the xPC.

• A generic module is composed of 2 sub-objects:

− a name for display (mandatory),

− a ‘xPS muti-state’ for dynamic module state display (mandatory), referencing a

dynamic bitmap object in the bitmap table, and whose relation to a xPS datapoint
(SPS or DPS) has to be filled up to precise animation datapoint.
C264/EN AP/B30 Application

Page 370/396 MiCOM C264/C264C

• Transformer representation,
used to display transformer module; linked to a optional Tap Position Indicator.
Transformer is composed of 5 sub-objects:

− a name for display (mandatory),

− a ‘TPI muti-state’ for transformer display (mandatory), referencing a dynamic

bitmap object in the bitmap table, and whose relation to a TPI datapoint can be
filled up to precise the concerned datapoint for the following animation,

− an optional ‘current TPI value’ object to display dynamically the current value of
the TPI,

− an optional ‘max TPI value’ object to display upper available value for the TPI,

− an optional ‘min TPI value’ object to display lower available value for the TPI
7.3.3.1 Adding time information
An addition of the time information in bay mimic is done under SCE via the “Object entry”
area at bay mimic level by clicking on mouse’s right button.

FIGURE 414: ADDING TIME INFORMATION IN MiCOM C264 COMPUTER BAY MIMIC
Once added, time information attributes must be set at SCE level:
1. Short and long names of the line used for internal SCE identification
2. X-coordinate
3. Y-coordinate

(1)

(2)

(3)

FIGURE 415: SETTING TIME INFORMATION ATTRIBUTES

X-coordinate, Y-coordinate of a bitmap can be directly managed using mouse in bay mimic
editor (for detail, refer to SCE user’s manual)
Application C264/EN AP/B30

MiCOM C264/C264C Page 371/396

7.3.3.2 Positioning Local/Remote status, Synchrocheck bypass or Interlock bypass

When creating a bay mimic, the following objects are implicitly created in the mimic at a pre-
defined location:
1. Local/remote status
2. Synchrocheck bypass ‘button’
3. Interlock bypass ‘button’
Depending on customer’s need, these data can be positioned at a different location:

• directly by using mouse drag and drop in bay mimic editor

• by editing the X-coordinate and Y-coordinate attributes of the object.

(1)
(2)

(3)

FIGURE 416: POSITIONNING PRE-DEFINED TEXT INFORMATION IN BAY MIMIC

7.3.3.3 Adding SBMC information
An addition of the SBMC information in bay mimic is done under SCE via the “Object entry”
area at bay mimic level by clicking on mouse’s right button. For details about SBMC, refer to
chapter 6.1.4.3 Defining SBMC for bay.

FIGURE 417: ADDING SBMC INFORMATION IN MiCOM C264 COMPUTER BAY MIMIC
Depending on customer’s need, SBMC information can be positioned at any location in bay
mimic:

• directly by using mouse drag and drop in bay mimic editor

• by editing the X-coordinate and Y-coordinate attributes of the object.

C264/EN AP/B30 Application

Page 372/396 MiCOM C264/C264C

7.3.3.4 Adding a generic module representation

In bay mimic, ‘LHMI Gen module’ is used for module dynamic representation. A ‘LHMI Gen
module’ is a graphical group constituted of:

• the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS
datapoint and to a dynamic bitmap in bitmap table

• the graphical name of the module (Name), always located on the right of the module
representation
An addition of a generic module representation in bay mimic is done under SCE via the
“Object entry” area at bay mimic level by clicking on mouse’s right button.

FIGURE 418: ADDING A GENERIC MODULE IN MiCOM C264 COMPUTER BAY MIMIC
Once added, the representation features must be set at SCE level:
1. Short and long names of the representation used for internal SCE identification
2. X-coordinate
3. Y-coordinate
4. Control availability (Yes/No): flag to precise if control of the module can be directly
done via bay mimic. This flag is significant if SPS/DPS linked to the generic module
representation (via (5) relation) is feedback of a control SPC or DPC. If so, control
availability concerns this SPC/DPC.
5. Relation ‘is managed by’ that must be filled to precise which SPS or DPS is used for
bitmap animation.
6. Multi-bitmap reference: corresponds to a link in the bitmap table (refer to chapter 7.1
Defining bitmap table).
7. Name of the module: text displayed on LCD (up to 4 characters).
Application C264/EN AP/B30

MiCOM C264/C264C Page 373/396

(1)

(2)
(3)

(4)

(5)

(6)
(7)

FIGURE 419: SETTING FEATURES OF GENERIC MODULE REPRESENTATION

X-coordinate, Y-coordinate of a generic module can be directly managed using mouse in bay
mimic editor (for detail, refer to SCE user’s manual).
Configuration rules and checks

• The link from an element to its bitmap is defined with the attribute : "bitmap reference".
The value of this attribute must refer to an existing bitmap in the "Bitmap table".

• The "Bitmap" linked to a "LHMI xPS MultiSt" MultiState must be defined as follow :
- its "type" attribute must be set to "5-uple" value
- its 3 first file names { "file name by default", "file name for 'open' state", "file name for
'closed' state" } are mandatory and each one must be unique.

Furthermore, if the MultiState is linked to a SPS or DPS Datapoint of a module

containing a "Withdrawn" SPS Datapoint, through the "is managed by" relation, then
the following constraints are added to the "Bitmap" definition :
- its 2 file names { "file name for 'withdrawn open' state", "file name for 'withdrawn
closed' state" } are both mandatory and each one must be unique.
C264/EN AP/B30 Application

Page 374/396 MiCOM C264/C264C

7.3.3.5 Adding a transformer representation

In bay mimic, ‘LHMI Transformer’ is used for dynamic transformer representation. A ‘LHMI
transformer’ is a graphical group constituted of:

• the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS
datapoint and to a dynamic bitmap in bitmap table

• the graphical name of the module (Name), always located on the right of the module
representation
An addition of a transformer representation in bay mimic is done under SCE via the “Object
entry” area at bay mimic level by clicking on mouse’s right button.

FIGURE 420: ADDING A GENERIC MODULE IN MiCOM C264 COMPUTER BAY MIMIC
Once added, the representation features must be set at SCE level:
1. Short and long names of the representation used for internal SCE identification
2. X-coordinate
3. Y-coordinate
4. Control availability (Yes/No): flag to precise if control of the transformer can be directly
done via bay mimic. This flag is significant if Raise/Lower DPC control exists for Tap
changer built-in function containing the TPI datapoint used for transformer animation
(via (5) relation). If so, control availability concerns this DPC.
5. Relation ‘is managed by’ that must be filled to precise which TPI is used for
transformer animation
6. Multi-bitmap reference: corresponds to a link in the bitmap table (refer to chapter 7.1
Defining bitmap table)
7. Name of the transformer: text displayed on LCD (up to 4 characters)
Application C264/EN AP/B30

MiCOM C264/C264C Page 375/396

(1)

(2)
(3)

(4)

(5)

(6)
(7)

FIGURE 421: SETTING FEATURES OF TRANSFORMER REPRESENTATION

X-coordinate, Y-coordinate of a transformer can be directly managed using mouse in bay
mimic editor (for detail, refer to SCE user’s manual)
When adding a transformer representation, extra values about associated TPI datapoint can
be placed in the bay mimic:

• Current TPI value (dynamic)

• Maximal TPI value

• Minimal TPI value

An addition of such TPI information in bay mimic is done under SCE via the “Object entry”
area at transformer representation level by clicking on mouse’s right button.

FIGURE 422: ADDING A TPI INFORMATIION IN MiCOM C264 COMPUTER BAY MIMIC
C264/EN AP/B30 Application

Page 376/396 MiCOM C264/C264C

Once added, TPI information can be positioned at a different location:

• directly by using mouse drag and drop in bay mimic editor

• by editing the X-coordinate and Y-coordinate attributes of the object.

Configuration rules and checks

• The link from an element to its bitmap is defined with the attribute : "bitmap reference".
The value of this attribute must refer to an existing bitmap in the "Bitmap table".
7.3.4 Assigning MV to bay mimic
A MV datapoint is assigned to a specific bay mimic by adding the relation ‘visualizes’ at bay
mimic level and filling it with the MV.

FIGURE 423: ASSIGNING MV DATAPOINT TO BAY MIMIC

Once the relation added and filled, its attributes ‘scale’ must be set at SCE level:
1. Scale (120%, 200% or ‘no bargraph’), to precise which representation is used for the
MV in the bay mimic

(1)

FIGURE 424: SETTING MV REPRESENTATION IN BAY MIMIC

Configuration rules and checks

• A MV Datapoint visualized in a "Bay mimic" (relation "visualizes") must belong to the

bay represented by the "Bay mimic" (relation "represents").

• For each visualized MV Datapoint, the "transmission on event" attribute must be set
neither to "Cyclic short period" value nor to "Cyclic long period" value to avoid overflow
of the Bay mimic input buffer.
Application C264/EN AP/B30

MiCOM C264/C264C Page 377/396

7.4 Displaying datapoint status with Led

SPS and DPS datapoint status can be displayed via leds of GHU200 board by adding the
relation ‘has state displayed on’ at datapoint level (1). Only datapoint managed by MiCOM
C264 Computer can be displayed via the Leds of its GHU200 board.

(1)

FIGURE 425: DISPLAYING DATAPOINT STATUS WITH LED

(E.G. FOR BAY SPS DATAPOINT)
Once added at SPS (resp. DPS) level, the relation must be filled with the relevant associated
Led and the following relation attributes should be updated:
1. Led status for ‘Set’ (rep. ‘Closed’) state: Off, On, Blinking slow, Blinking fast
2. Led status for ‘Reset’ (rep. ‘Open’) state: Off, On, Blinking slow, Blinking fast
3. Led status for ‘Invalid’ state: Off, On, Blinking slow, Blinking fast

(1)

(2)

(3)

FIGURE 426: SETTING LED STATUS FOR DATAPOINT

(E.G. FOR SPS DATAPOINT)
Configuration rules and checks

• If the value of the "HMI type" attribute is "Simple", then "Led#4" must not be used (no
relation link from "Led#4" to a Datapoint)
C264/EN AP/B30 Application

Page 378/396 MiCOM C264/C264C

8. ANNEX A: COUPLING SCE DATA MODEL AND ISaGRAF

8.1 ISaGRAF presentation
The SCE will use the 4.11 version of the ISaGRAF software from CJ-International (Altersys
Incorporation).
The 4.11 version is actually a 4.10 upgraded version with specific software developments for
the AREVA company.
8.1.1 ISaGRAF workbench description

• The workbench is used to design and develop distributed process control

applications. These applications are organised in projects.

• A project gathers the whole of all program elements and is composed of

configurations.

• A configuration is a hardware platform which supports kernels that executes

resources. In our version there is only one resource.

• A resource is composed of several units of program (POU). In the current version

there is exactly one resource per configuration.

• The POUs (Program Organisation Unit) can be programs, functions or functional

blocs. They are described using the IEC 1131-3 compliant textual or graphic
languages. They are organised on a hierarchical basis architecture.

• The kernel or virtual machine is the real time software that runs the code of a
resource.

• A target is attached to a configuration. It must be installed on a platform that support a

multi-task operating system such NT or VxWorks.

• The dictionary includes all the variables (input, output or internal), all the function
parameters definitions, all the types (simple or user defined) and all the defined words
(constants definition).

• The languages can be either graphic or textual. They are used to describe the
Program organisation units (POU). They are compliant with the IEC 1131-3 standard.

− SFC : Sequential Function Chart (grafcet),

− FBD : Function Block Diagram (functional diagram),

− LD : Ladder Diagram (Boolean logic based language),

− ST : Structured Text

− IL : Instruction List.
There is another graphic language in the workbench: FC (Flow Chart). Nevertheless, it is not
in the standard.
The automatism functions can be designed from any of the graphic or textual languages
proposed by ISaGRAF. According to the problem which the automata must solve, a
language can be better adapted than another.
All languages except the SFC can be instantiated, i.e. they can be used for creation of a
functional block.
Application C264/EN AP/B30

MiCOM C264/C264C Page 379/396

Hardware
platform
PROJECT
CONFIGURATION TARGET
RESOURCE KERNEL

Exchange PRJLIBRARY.MDB file *.STF files

diagrams
POU
Dictionary
Graphical
Dictionary Language Editors

C0251ENa

FIGURE 427: ISAGRAF WORKBENCH DESCRIPTION

The workbench contains a exchanges diagram (display of the resources and their possible
links), a view of material architecture (presentation of the configurations with their
resources), the data dictionary and the graphic editors which allow to visualise the POUs
(SFC editor, FC editor and multi-language editor for FBD, LD, ST and IT languages).
8.1.2 Directories structure of ISAGRAF
When the workshop is installed, the following directories tree structure is created :
<root directory>
Bin Executables
Grp Windows Groups
Help
Prj Projects
<project name> single project directory
config1 1 directory ! 1 config.
resource1 1 directory ! 1 resource
Simul
Tmp
Tpl projects models
<project name> model name
<configuration>
<resource>

A project is composed of:

• the MS Access database file in the root directory of the project

• the source files of the POU of the resource in the repertory /config1/ressource1.
All the data dictionary is saved in the MS Access database file.
The POU files have the STF extension.
When a POU is added into a resource, a STF file is created in the resource folder. It contains
the graphic description (elements coordinates in the editor) as well as the algorithms.

Prj
PROJECT NAME
PRJLIBRARY.MDB
Config1
Ressource1
POU1.STF
POU2.STF

ISaGRAF PROJECT STRUCTURE

The compilation of a project produces several files such *.XTC embedding the TIC code. The
TIC code is the “interpretable code” of the automatism.
C264/EN AP/B30 Application

Page 380/396 MiCOM C264/C264C

8.1.3 Uploaded files towards the target

During upload, the workbench transfers several files to hardware platforms.
The files that are transferred are the following ones:

• Resource (for each resource of that platform) :

− A resource configuration file is downloaded.

Name of that file on workbench = RESOURCENAME_Conf.xtc.
Name of that file (or memory module) on hardware platform = ISPxxx03 (with xxx
being resource number in hexadecimal).

− A file containing resource symbols (variable names and so on) will be downloaded
if ‘embed symbol table’ option has been checked in resource properties).
Name of that file on workbench = RESOURCENAME_SymbolsTarget.xtc (this
table is complete or reduced according to resource properties option at last
compiling).
Name of that file on target = IDSxxx01

• POU (for each POU of a resource):

− All POU TIC code files on workbench (file name =

ResourceName_POUName_xtc) will be concatenated into a single file.

− Order for the concatenation is the one given by workbench file

ResourceName_DWLOrder.xtc.

− On hardware platform side, the name of that file will be ISPxxx01.

• Hardware platform:

− The hardware configuration file is downloaded.

− On workbench, file is stored in the project configuration directory, (not in a

resource directory).

− The workbench file name is : ConfigName_NetworkConf.xtc.

− On hardware platform side, the name of that file is ISPffe0d.

Note that this document does not speak about which files are transferred in on-line
modification case (ISPxxx15)
Thus, the files must be modified before download to the target:

• RESOURCE1_Conf.xtc must be renamed as ISP00103

• RESOURCE1_SymbolsTarget.xtc must be renamed as IDS00101

• Config1_NetworkConf.xtc must be renamed as ISPffe0d

All POU TIC files will be concatenated in file ISP00101 in the order described the
DwlOrder.txt file.
Application C264/EN AP/B30

MiCOM C264/C264C Page 381/396

8.2 Usage of SCE datapoints in ISaGRAF

The DataPoint (DP) are defined inside the SCE. They will be used by the slow automation as
I/Os. An automation can interact with the system only via these DataPoint.
Any DP used in the code of an automation must be defined beforehand in the SCE.
There are three different kinds of relation between a slow automation and DataPoints:

• The function owns the DataPoint (hierarchical Relation) :

see chapter 6.6.2.2 Adding specific datapoints to slow automation

• The function is server of the Data Point (Relation server) :

see chapter 6.6.2.4 Creating ISaGRAF server link (interface definition)

• The function is client of the Data Point (Client relationship):

see chapter6.6.2.3 Creating ISaGRAF client link (interface definition)
8.2.1 Hierarchical relationship: Function management DPs.
In the electrical tree structure these DP are defined under the function. The function is the
owner of the DP.
For instance these DP can be :

• ON/OFF command of the automatism,

• functions parameters,
• current values and current state of the automatism.
The function has the following rights on the real time attributes of the DP :

• status (SPS, DPS, MPS, SPC, DPC, SetPoint) : read/write

• value (MV, TPI, Counter) : read/write
• quality (all DP except SPC, DPC, SetPoint) : read/write
• threshold value (MV, Counter) : read
• alarm (global alarm status) : read
The hierarchical relationship implies that the DP can be seen as input as well as output of
the function.
8.2.2 Server relationship
The DPs are supplied by the function. They are not attached to the tree structure of the
function. Their parent are components from the electric tree structure or the system tree
structure (bay, module, physical device). The function is charged to update the status/value
and quality attributes of these DPs.
For instance these DP can be :

• DP resulting from a logical or analogic mathematical formula which is implemented by

an automatism

• synthesis DP (for example a device position)

• commands received and treated by the automatism

The function has the following rights on the real time attributes of its supplied DPs :

• status (SPS, DPS, MPS, SPC, DPC, SetPoint) : read/write

• value (MV, Counter, TXT) : read/write
• quality (all DP except SPC, DPC, SetPoint) : read/write
• threshold value (MV, Counter) : read
• alarm (global alarm status) : read
C264/EN AP/B30 Application

Page 382/396 MiCOM C264/C264C

8.2.3 Client relationship

The function is client of the DP. The DP is not attached to the tree structure of the function.
Its parent is a component from the electric tree structure or the system tree structure (bay,
module, physical device).
The function reads and uses the status/value and quality attributes of the DP.
If the type of the DP is SPC, DPC or SetPoint, the function can also send command
requests. In this case, the equipment that manages the DP acknowledges this request (via
UCA2 AckCode), executes the command and updates the status and value attributes.
The command requests include parameters and quality modification. This is done in the
same way (acknowledge + attributes updates by the equipment that manages the DP). Thus,
the DP is known as controllable.
For instance these DP can be :

• commands sent by an automatism toward a device

• devices or bay state influencing the automatism execution.

• threshold modification request

• forcing, deletion, substitution request

• extended counter driving.

The function has the following rights on the real time attributes of the DPs wich the function
is client of :

• status (SPS, DPS, MPS read

• status (SPC, DPC, SetPoint) : read/control

• value (MV, Counter, TXT) : read

• quality (all DP except SPC, DPC, SetPoint) : read/control

• threshold value (MV, Counter) : read/control

• alarm (global alarm status) : read

8.2.4 Access rights summary table

DataPoint type Access types ISaGRAF variables

type
The function owns the DP whatever DP read/write input / output
Threshold, alarm read input
La function serves the DP whatever DP read/write input/output
(the function provides values) Threshold, alarm read control
La function is client of the DP SPS, DPS, SPS read input
(the function read the values) SPC, DPC, SP read and control input/output
MV read input
COUNTER read and control input/output
Threshold, alarm read input
Application C264/EN AP/B30

MiCOM C264/C264C Page 383/396

8.2.5 Equivalence of SCE datapoint in ISaGRAF

The DataPoints are represented by variables inside the ISaGRAF projects. The type of these
variables is chosen according to the access type to the DataPoint.
The input DPs correspond to read-only variables of a structured type. These structures
contain only the DataPoint attribute useable inside the automatisms (see chapter 8.2.6
ISaGRAF dictionary data structure ).
Within the calculators ISaGRAF kernel, the output DPs are reached by C functions, using an
ID (see chapter 8.2.7 Prototype and usage of PACiS function for ISaGRAF). Therefore, the
DPs are projected in the ISaGRAF workshop by an integer which represents the address of
the DP (its ID). This integer is stored in the equivalences table. In an ISaGRAF project, this
table contains some aliases : a name and its value. Theses aliases must be used in the
ISaGRAF programs to identify a variable. The name of an equivalence is made with the
name of the variable, plus the suffix ADR. The value of an equivalence is the address of the
DP. The final values are set during the compilation of PLC project. An equivalence is added
automatically when a Datapoint is added from the SCE application. The input/output DPs
(read/write access) are represented as input as well as output the workbench.
All “DP variables” have unique Ids stored in the equivalences table. The name of the variable
is in conformity with to the following rules:
The I/O symbols of the ISaGRAF workshop must correspond to the configuration DPs of the
SCE. They must be unique, easily recognisable to facilitate the programming in the
workshop but they must be short enough not to weigh down the diagrams nor the POUs
texts.
To give a name to the variables inside the ISaGRAF projects, we must consider that :

• The name must be unique

• ISaGRAF is not case sensitive

• The maximum length of name is 128 characters

• The first character must be a letter

• The following characters must be, either a letter, either a digit or an underscore.
So the identifier of I/O symbols is made with a prefix (in, out, in_out) and a identifier number.
In the workshop, the user will have an alias made up of the short names of the bay, module
and DataPoint in the form bay_module_datapoint. The used short name language will be the
one which is declared as “automata language”, i.e. one of the 4 AREVA T&D basic
languages : English, French Spanish or German. Complete identifier SCE will appear in the
data dictionary of the workshop inside the comment field.
The “DP variables” are located in different groups according to their type and relationship to
the function. These groups are not created in order to prevent the user from adding
variables in these groups.
In the SCE application, the address is stored as an attribute of the link between the function
and the DP. This attribute is updated during the fusion of the functions projects towards the
PLC project and the equivalence table is updated with the new values of the variables
addresses.
C264/EN AP/B30 Application

Page 384/396 MiCOM C264/C264C

8.2.6 ISaGRAF dictionary data structure

Each following table corresponds to a structure at ISaGRAF dictionary level.
8.2.6.1 SPS, DPS and MPS

SCE ISaGRAF
Status Status DINT
Quality Quality DINT
GlobalAlarmStatus Alarm SINT

Status attribute for SPS

• RESET / FORCED RESET / SUBSTITUTED RESET = 1

• SET / FORCED SET / SUBSTITUTED SET = 2

Status attribute for SPS

• Motion00 = 3
• Open / FORCED open / SUBSTITUTED OPEN = 4
• CloseD / FORCED closed / SUBSTITUTED closed = 5
NOTE : UNDEFINED state is seen as INVALID (see Quality attribute)
Status attribute for MPS

• State1 / FORCED state1 / SUBSTITUTED state1 = 7

• State2 / FORCED state2 / SUBSTITUTED state2 = 8
• State3 / FORCED state3 / SUBSTITUTED state3 = 9
• State4 / FORCED state4 / SUBSTITUTED state4 = 10
• State5 / FORCED state5 / SUBSTITUTED state5 = 11
• State6 / FORCED state6 / SUBSTITUTED state6 =12
• State7 / FORCED state7 / SUBSTITUTED state7 =13
• State8 / FORCED state8 / SUBSTITUTED state8 = 14
• State9 / FORCED state9 / SUBSTITUTED state9 = 15
• State10 / FORCED state10 / SUBSTITUTED state10 = 16
• State11 / FORCED state11 / SUBSTITUTED state11 = 17
• State12 / FORCED state12 / SUBSTITUTED state12 = 18
• State13 / FORCED state13 / SUBSTITUTED state13 = 19
• State14 / FORCED state14 / SUBSTITUTED state14 = 20
• State15 / FORCED state15 / SUBSTITUTED state15 = 21
• State16 / FORCED state16 / SUBSTITUTED state16 = 22
Quality attribute

• VALID = 0
• INVALID ≠ 0 (TOGGLING, UNKNOWN, SELFCHECK FAULTY, SUPPRESSED,
UNDEFINED)
If Quality attribute is INVALID, Status attribute is non-significant.
Alarm attribute
Unusable
Application C264/EN AP/B30

MiCOM C264/C264C Page 385/396

8.2.6.2 SPC, DPC

SCE ISaGRAF
Status Status DINT
GlobalAlarmStatus Alarm SINT

Status attribute for SPC

• OFF = 0

• ON = 1
Status attribute for DPC

• OPEN = 0

• CLOSE = 1
Alarm attribute
Unusable
8.2.6.3 SetPoint

SCE ISaGRAF
Status Status DINT
GlobalAlarmStatus Alarm SINT

Not yet implemented

8.2.6.4 MV, TPI

SCE ISaGRAF
Value Value REAL
HHHThresholdValue Threshold_hhh REAL
HHThresholdValue Threshold_hh REAL
HthresholdValue Threshold_h REAL
LthresholdValue Threshold_l REAL
LLThresholdValue Threshold_ll REAL
LLLThresholdValue Threshold_lll REAL
Quality Quality DINT
GlobalAlarmStatus Alarm SINT

Quality attribute

• VALID = 0

• SELFCHECK FAULTY = 1

• UNKNOWN = 2

• FORCED = 4

• SUPPRESSED = 8

• SUBSTITUTE = 16

• SATURATED = 64

• UNDEFINED = 128
C264/EN AP/B30 Application

Page 386/396 MiCOM C264/C264C

• OPEN CIRCUIT = 256

• L_THRESHOLDVIOLATION = 512

• LL_ThresholdViolation = 1024

• LLL_ThresholdViolation = 2048

• H_thresholdViolation = 4096

• HH_ThresholdViolation = 8192

• HHH_ThresholdViolation = 16384
At a given time, only one value is available. FORCED and SUBSTITUTED states have
higher priority than threshold violation states.
Alarm attribute
Unusable
8.2.6.5 Counter

SCE IsaGRAF
Value Value REAL
FrozenCumulativeValue FrozenCValue REAL
HHHThresholdValue Threshold_hhh REAL
HHThresholdValue Threshold_hh REAL
HthresholdValue Threshold_h REAL
LthresholdValue Threshold_l REAL
LLThresholdValue Threshold_ll REAL
LLLThresholdValue Threshold_lll REAL
Quality Quality DINT
GlobalAlarmStatus Alarm SINT

Quality attribute

• VALID = 0

• SELFCHECK FAULTY = 1

• UNKNOWN = 2

• OVERRANGE = 64

• UNDEFINED = 128
At a given time, only one value is available.
The attributes FrozenCValue, Threshold_hhh, Threshold_hh, Threshold_h, Threshold_lll,
Threshold_ll, Threshold_l et Alarm are unusable.
Application C264/EN AP/B30

MiCOM C264/C264C Page 387/396

8.2.7 Prototype and usage of PACiS function for ISaGRAF

IMPORTANT

• All the following described functions must never be called in ISaGRAF SFC transitions
but only in actions.

• When an action calls the function Wait_Ack_Order, the following transition must at
least test the TRUE value of the function return code (indicating that control has been
well received)
8.2.7.1 Send_Binary_Order
This function concerns the following DP used in ‘in client’ or ‘manages’ relation:

• SPC, DPC,

• Select part for SBO on SetPoint

Name Comment Parameter/retur Acces C Type Available values

n code (CEI Type)
Return code Output Unsigned FALSE : KO
char TRUE : OK
(BOOL)
Order Order Parameter Input Char (SINT) 0 : OFF / OPEN
1 : ON / CLOSE

4 : SELECT OFF / OPEN

or SELECT Setpoint
5 : SELECT ON / CLOSE
Bypass Forcing Parameter Input Long (DINT) Masks :
1 = Interlock bypass
(unused if
Order=SELECT) 2 = Locking bypass
4 = Mode bypass
8 = Uniqueness bypass
16 = Automation bypass
32 = Synchrocheck
bypass
Several masks can be set
simultaneously
Ref_DP Internal reference of Parameter Input Long (DINT) Use equivalent word
the DP in host linked to the datapoint
equipment (<var>_ADR)
Ref_cm Identifier of the Parameter Output Long (DINT) Use a locale variable
d command

Prototype C :
Unsigned char Send_Binary_Order(char Order, long Bypass, long Ref_DP ,long Ref_Cmd)
C264/EN AP/B30 Application

Page 388/396 MiCOM C264/C264C

8.2.7.2 Send_Digital_Order
This function concerns SetPoints used in ‘in client’ or ‘manages’ relation.
Select for SBO is done via function Send_Binary_Order.

Name Comment Parameter/retur Acces C Type Available values

n code (CEI Type)
Return code Output Unsigned FALSE : KO
char (BOOL) TRUE : OK
Order Value order Parameter Input Float (REAL)
Ref_DP Internal reference of Parameter Input Long (DINT) Use equivalent word
the DP in host linked to the datapoint
equipment (<var>_ADR)
Ref_cmd Identifier of the Parameter Output Long (DINT) Use a locale variable
command

Prototype C :
Unsigned char Send_Digital_Order(float Order, long Ref_DP, long Ref_cmd)
8.2.7.3 Send_Threshold_Order
This function concerns the MV and COUNTER used in ‘in client’ or ‘manages’ relation.

Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
Return code Output Unsigned FALSE : KO
char (BOOL) TRUE : OK
Threshold_used Mask of thresholds Parameter Input char (SINT) bit 0 :
to update THRESHOLD_HHH
bit 1 :
THRESHOLD_HH
bit 2 : THRESHOLD_H
bit 3 : THRESHOLD_L
bit 4 :
THRESHOLD_LL
bit 5 :
THRESHOLD_LLL
Threshold_HHH Threshold high- Parameter Input Float (REAL)
high-high
Threshold_HH Threshold high-high Parameter Input float (REAL)
Threshold_H Threshold high Parameter Input float (REAL)
Threshold_L Threshold low-low- Parameter Input float (REAL)
low
Threshold_LL Threshold low-low Parameter Input float (REAL)
Threshold_LLL Threshold low Parameter Input float (REAL)
Ref_DP Internal reference Parameter Input long (DINT) Use equivalent word
of the DP in host linked to the datapoint
equipment (<var>_ADR)
Ref_cmd Identifier of the Parameter Output Long (DINT) Use a locale variable
command

Prototype C :
unsigned char Send_Thresholds_Order(char Threshold_used, float Threshold_HHH, float
Threshold_HH, float Threshold_H, float Threshold_L, float Threshold_LL, float
Threshold_LLL, long Ref_DP, long Ref_cmd)
Application C264/EN AP/B30

MiCOM C264/C264C Page 389/396

8.2.7.4 Send_Quality_Order
This function concerns SPS, DPS, MPS, MV, TPI, COUNTER used in ‘in client’ or ‘manages’
relation for Forcing/Suppression/Substitution functionality.

Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
Return code Output Unsigned char FALSE : KO
(BOOL) TRUE : OK
Quality Asked quality Parameter Input Char (SINT) 1 : FORCING
2 : SUBSTITUTING
3 : UNFORCING
4 : UNSUBSTITUTING
5 : SUPRESSING
6 : UNSUPRESSING
Binary_Value Forcing or Parameter Input Char (SINT) SPS
substitution
1 : RESET
value for SPS,
2 : SET
DPS, MPS

DPS
3 : JAMMED
4 : OPEN
5 : CLOSE

MPS
7 : STATE1
8 : STATE2
9 : STATE3
10 : STATE4
11 : STATE5
12 : STATE6
13 : STATE7
14 : STATE8
15 : STATE9
16 : STATE10
17 : STATE11
18 : STATE12
19 : STATE13
20 : STATE14
21 : STATE15
22 : STATE16
Digital_Value Forcing or Parameter Input Float (REAL)
substitution
value for MV,
TPI, COUNTER
Ref_DP Internal Parameter Input Long (DINT) Use equivalent word
reference of the linked to the datapoint
DP in host (<var>_ADR)
equipment
Ref_cmd Identifier of the Parameter Output Long (DINT) Use a locale variable
command

Prototype C :
unsigned char Send_Quality_Order(char Quality, char Binary_Value, float Digital_Value,
long Ref_DP, long Ref_cmd)
C264/EN AP/B30 Application

Page 390/396 MiCOM C264/C264C

8.2.7.5 Send_Ack_Order
This function is used when the automatism manages a DP to answer a awaited command
(Wait_xxx_Order). It allows acknowledgement of received order. It is only used for "User
Function DP".

Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
Return code Output Unsigned char FALSE : KO
(BOOL) TRUE : OK
Ref_DP Internal Parameter Input Long (DINT) Use equivalent word linked to the
reference of datapoint (<var>_ADR)
the DP in host
equipment
Order Order of the Parameter Input Char (SINT) 0 : OFF / OPEN
run command 1 : ON / CLOSE

4 : SELECT OFF / OPEN or

SELECT Setpoint
5 : SELECT ON / CLOSE
Value digital order Parameter Input Float (REAL)
value
Ack_code Acknowledge Parameter Input Long (DINT) See hereafter
ment code

Prototype C :
unsigned char Send_Ack_Order(long Ref_DP, char Order, real Value, long Ack_code)
Available acknowledgement codes
0. ACK_OK - positive acknowledgement
1. INCOHERENT_REQUEST - incoherent command
2. MICOM C264 COMPUTER_NOT_READY - command when MiCOM C264 Computer
is initializing
3. BAY_SUBST_MODE_FAULT - error on substation or bay Local/remote mode
4. CONTROL_MODE_FAULT - command when MiCOM C264 Computer is in
maintenance or faulty
5. DEVICE_LOCKED - locked device
6. REQUEST_IN_PROGRESS - command in progress for the device or reception of a
command during delay of forbidden command (inter-control delay)
7. INTERLOCK_NOK - refused by interlock
8. DEVICE_ALREADY_IN_POS - command similar to device current state
9. HW_FAULT - DO board fault
10. POS_INVALID - invalid position of device
11. TIMEOUT_FAILED - time-out between selection and execution or time-out in IED
answer
12. AUTOMATION_RUNNING - device locked by relevant AutoManu information
13. DEVICE_ALREADY_SELECTED - reception of a selection demand as device is still
selected
Application C264/EN AP/B30

MiCOM C264/C264C Page 391/396

14. DEVICE_NOT_SELECTABLE - reception of a selection demand as device is Direct

Execute
15. UNIQUENESS_INCOHERENCY - failure in command uniqueness
16. NO_SELECTED - reception of a execution demand as device is not yet selected
17. OPERATOR_CANCEL - cancel operator
18. EXTERNAL_FAULT - time-out on feedback
19. ACK_FAILED_ORDER - acknowledgement UCA2 failed
20. ACK_BAD_TCIP - time-out waiting presence of TCIP SPS
21. ACK_TCIP_TOO_LONG - time-out waiting OFF state of TCIP information
22. ACK_BAD_TAP - bad tap position following a command
23. ACK_MIN_TAP - reception of order "lower" as TPI is on Min value
24. ACK_MAX_TAP - reception of order "raise" as TPI is on Max value
25. DEVICE_FAILED_TO_OPERATE - command towards disconnected IED
26. SYNCHRO_NOK – command refused by synchrocheck
8.2.7.6 Wait_Binary_Order
This function is used when the ISaGRAF module must wait for an execution order relevant to
SPC or DPC. It is only used for "User Function DP".

Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
Return code Output Unsigned char FALSE : KO
(BOOL) TRUE : OK
Order Order Parameter Output Char (SINT) 0 : OFF / OPEN
1 : ON / CLOSE
Ref_DP Internal reference of Parameter Input Long (DINT) Use equivalent word linked to
the DP in host the datapoint (<var>_ADR)
equipment

Prototype C :
Unsigned char Wait_Binary_Order(char Order, long Ref_DP)
If the order has a SBO type, the Select will be computed outside ISaGRAF (so Select can
only be soft).
A Wait_Binary_Order must be followed by a Send_Ack_Order.
C264/EN AP/B30 Application

Page 392/396 MiCOM C264/C264C

8.2.7.7 Wait_Digital_Order
This function is used when the ISaGRAF module must wait for an execution order relevant to
SetPoint. It is only used for "User Function DP".

Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
Return Output Unsigned char FALSE : KO
code (BOOL) TRUE : OK
Order Order Parameter Output Float (REAL)
Ref_DP Internal reference Parameter Input Long (DINT) Use equivalent word linked
of the DP in host to the datapoint
equipment (<var>_ADR)

Prototype C :
Unsigned char Wait_Digital_Order(float Order, long Ref_DP)
If the order has a SBO type, the Select will be computed outside ISaGRAF (so Select can
only be soft).
A Wait_Digital_Order must be followed by a Send_Ack_Order.
8.2.7.8 Wait_Ack_Order
This function is used when the ISaGRAF module is waiting for an acknowledgement of one
of its commands (Send_xxx_order). It concerns the DP used in ‘in client’ or ‘manages’
relation.

Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
Return code Output Unsigned char FALSE : KO
(BOOL) TRUE : OK
Ref_cmd Command Parameter Input Long (DINT) Use the variable associated
reference on which to Ref_cmd used in the
acknowledgement function Send_xxx_order
is awaited
Ack_code Acknowledgement Parameter Sortie Long (DINT) Cf. Send_Ack_Order
code

Prototype C :
Unsigned char Wait_Ack_Order(long Ref_cmd, long Ack_code)
Application C264/EN AP/B30

MiCOM C264/C264C Page 393/396

8.2.7.9 Set_xPS
This function is used to give to the host equipment the SPS, DPS, MPS whose all attributes
can be updated by ISaGRAF module. This function uses "User Function DP".

Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
Return code Output Unsigned char FALSE : KO
(BOOL) TRUE : OK
DP_value DP to update Parameter Input Struct_xPS { Status field:
long
Status (DINT);
SPS :
long
Quality (DINT); 1 : Reset
char 2 : Set
Alarm (SINT);
}
DPS :
3 : Jammed
4 : Open
5 : Close
6 : Undefined

MPS :
7 : State1
8 : State2
9 : StatE3
10 : State4
11 : State5
12 : State6
13 : State7
14 : State8
15 : State9
16 : State10
17 : State11
18 : State12
19 : State13
20 : State14
21 : State15
22 : State16

Quality field:
0 : VALIDE
1 : INVALIDE

Alarm field:
(not significant)
Ref_DP Internal reference of Parameter Input Long (DINT) Use equivalent word
the DP in host linked to the datapoint
equipment (<var>_ADR)

Prototype C :
Unsigned char Set_xPS(struct_xPS DP_Value, long Ref_DP)
For DPS managed through Set_xPS function, the non-complementarity delays (00 and 11)
must be set to 0 in configuration.
C264/EN AP/B30 Application

Page 394/396 MiCOM C264/C264C

8.2.7.10 Set_MV
This function is used to give to the host equipment the MV whose all attributes can be
updated by ISaGRAF module. This function uses "User Function DP".

Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
Return code Output Unsigned char (BOOL) FALSE : KO
TRUE : OK
DP_value DP to update Parameter Input Struct_MV { Value field:
float Value (REAL); any real value
float compatible with
Threshold_hhh (REAL) ; configuration data
float of the DP
Threshold_hh (REAL) ;
float
Threshold_h (REAL) ; Quality field:
float Threshold_l (REAL) ; 0 : VALIDE
float 1 : INVALIDE
Threshold_ll (REAL) ;
float Threshold_xxx &
Threshold_lll (REAL) ; Alarm fields:
long Quality (DINT); (not significant)
char Alarm (SINT);
}
Ref_DP Internal reference Parameter Input Long (DINT) Use equivalent
of the DP in host word linked to the
equipment datapoint
(<var>_ADR)

Prototype C :
Unsigned char Set_MV(struct_xMV DP_Value, long Ref_DP)
Application C264/EN AP/B30

MiCOM C264/C264C Page 395/396

8.2.7.11 Set_Counter
This function is used to give to the host equipment the Counters whose all attributes can be
updated by ISaGRAF module. This function uses "User Function DP".

Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
Return code Output Unsigned char (BOOL) FALSE : KO
TRUE : OK
DP_value DP to update Parameter Input Struct_Counter { Value field:
float Value (REAL); any real value
float compatible with
FrozenCValue (REAL); configuration data
float of the DP
Threshold_hhh (REAL) ;
float
Threshold_hh (REAL); Quality field:
float 0 : VALIDE
Threshold_h (REAL) ; 1 : INVALIDE
float Threshold_l (REAL);
float Threshold_xxx &
Threshold_ll (REAL) ; Alarm fields:
float (not significant)
Threshold_lll (REAL) ;
long Quality (DINT);
char Alarm (SINT);
}
Ref_DP Internal reference Parameter Input Long (DINT) Use equivalent
of the DP in host word linked to the
equipment datapoint
(<var>_ADR)

Prototypage C :
Unsigned char Set_Counter(struct_Counter DP_Value, long Ref_DP)
C264/EN AP/B30 Application

Page 396/396 MiCOM C264/C264C

BLANK PAGE
Settings C264/EN ST/B30

MiCOM C264/C264C

SETTINGS
Settings C264/EN ST/B30

MiCOM C264/C264C Page 1/10

CONTENT

1. SCOPE OF THE DOCUMENT 3

1.1 Tree Panel Navigation 3
1.2 Tree Panel Parameters 4
C264/EN ST/B30 Settings

Page 2/10 MiCOM C264/C264C

BLANK PAGE
Settings C264/EN ST/B30

MiCOM C264/C264C Page 3/10

1. SCOPE OF THE DOCUMENT

This document is a chapter of MiCOM C264 documentation binders. It describes the Settings
-or on-line- parameters, which can be modified in runtime on MiCOM C264 computers. The
setting is done through the LCD Local Control Display. It is only available with a GHU200 or
a GHU201 front face.
This chapter details settings mentioned in C264/EN HI (Human Interface) part with default
and range values.
1.1 Tree Panel Navigation

Tree panel is accessible from bay panels by selecting the following key: !
All data points are grouped into features and folders. To access a given feature the operator
should navigate the panels using the arrow keys. The folders hierarchy is displayed in each
panel.

" switches to neighbouring folder

# switches to neighbouring folder

$ select and expand the folder switching to its first item

% go up to father folder

At the bottom of the hierarchy, the folder is the single point of information, control or
parameter. Edit mode allows the operator to change values.

! & Enter into Edit mode. It then asks to enter the level 2 password.

' Cancel edition and the data point modification

The most commonly used settings and controls are selected into a list. To browse the list the
operator navigates using the arrow keys. The modification/control sequence is cancelled by
'. The selection is confirmed by !.
C264/EN ST/B30 Settings

Page 4/10 MiCOM C264/C264C

1.2 Tree Panel Parameters

Available Values
Parameter
MENU TREE Or
signification
[min;max](step)(unit)
COMMAND
MAIN
- RESET OP HOURS RESET To reset the number of
the C264 operating
hours.
- CHANGE MODE OP OPERAT, MAINT, TEST To change the C264
mode into active,
maintenance or test
mode.
- GLB ACK ALARM ACK To acknowledge all
C264 alarms
- GLB CLR ALARM CLEAR To clear all
acknowledged and
reset alarms
- DATE DATE To change the date.
Accepted if the C264 is
not synchronised
- TIME TIME To change the time.
Accepted if the C264 is
not synchronised. The
time format is hh : mn :
sec.
- DB SWITCH YES To switchover active
and standby
databases.
- LANGUAGE LG1, LG2 To switchover
Language1 and
language2.
COUNTER
Counter 1
…
Counter N
- COUNTER value Counter value To change the counter
value.
CONFIG
COMPUTER
MAIN
- IP ADDRESS xxx.xxx.xxx.xxx To read the C264 IP
address
BAY
Bay 0
…
Bay N
INTERNAL S/C
- S/C associated Dev XXXX To read the name of
the device associated
to the synchrocheck
Settings C264/EN ST/B30

MiCOM C264/C264C Page 5/10

Available Values
Parameter
MENU TREE Or
signification
[min;max](step)(unit)
- THRES PRES LINE [0.5;1.1](0.01)(V) Multiplier of nominal
voltage above which
the line is LIVE.
- THRES ABS LINE [0.1;0.6](0.01)(V) Multiplier of nominal
voltage below which
the line is DEAD.
- THRES PRES BUS [0.5;1.1](0.01)(V) Multiplier of nominal
voltage above which
the bus is LIVE.
- THRES ABS BUS [0.1;0.6](0.01)(V) Multiplier of nominal
voltage below which
the bus is DEAD.
- DELTA VOLT LOCK [0.02;0.5](0.01)(V) Voltage difference
between bus and line
above which locking
close is not possible.
- DELTA FREQ LOCK [0;1](0.01)(hz) Frequency difference
between bus and line
above which locking
close is not possible.
- DELTA PHASE LOCK [0;30](1)(deg) Phase difference
between bus and line
above which locking
close is not possible.
- FMIN LOCK [45;65](0.01)(hz) Minimum acceptable
frequency for locking
close.
- FMAX LOCK [45;65](0.01)(hz) Maximum acceptable
frequency for locking
close.
- DELTA VOLT COUPL [0.02;0.5](0.01)(V) Voltage difference
between bus and line
above which coupling
close is not possible.
- DELTA FREQ COUPL [0;1](0.01)(hz) Frequency difference
between bus and line
above which coupling
close is not possible.
- DELTA PHASE COUPL [0;30](1)(deg) Phase difference
between bus and line
above which coupling
close is not possible.
- FMIN COUPL [45;65](0.01)(hz) Minimum acceptable
frequency for coupling
close.
- FMAX COUPL [45;65](0.01)(hz) Maximum acceptable
frequency for coupling
close.
C264/EN ST/B30 Settings

Page 6/10 MiCOM C264/C264C

Available Values
Parameter
MENU TREE Or
signification
[min;max](step)(unit)
- REAC TIME [0; 1000](10)(ms) Circuit breaker close
time in order to
anticipate the close
order for the coupling.
- ABS V CONF TIME [200;10000](20)(ms) Time after which the
line and the bus are
considered dead.
- ONLY V CONF TIME [200;10000](20)(ms) Time after which only
one voltage among the
line or the bus is
considered live.
- PRES V CONF TIME [200;10000](20)(ms) Time after which the
line and the bus are
considered live.
- CLOSE TO MAN SYN [200;10000](20)(ms) Time waited for having
locking conditions.
- CLOSE TO MAN SY C [1; 3600](20)(s) Time waited for having
coupling conditions.
- CLOSE TO MANUAL [200;10000](20)(ms) Time waited for having
dead-dead or dead-live
conditions.
- CLOSE TO AUTO [200;10000](20)(ms) Time waited for closing
conditions in case of
auto-recloser control.
- MAN SYN CLO COUPL YES, NO Flag to permit or not
the coupling for a
“close with
synchrccheck”
operator control.
- MAN SYN CLO LCK YES, NO Flag to permit or not
the locking for a “close
with synchrccheck”
operator control.
- MAN SYN CLO LDBL YES, NO Flag to permit or not a
control with a dead line
and a live bus for a
“close with
synchrccheck”
operator control.
- MAN SYN CLO LLBD YES, NO Flag to permit or not a
control with a live line
and a dead bus for a
“close with
synchrccheck”
operator control.
- MAN SYN CLO LDBD YES, NO Flag to permit or not a
control with a dead line
and a dead bus. for a
“close with
synchrccheck”
operator control.
Settings C264/EN ST/B30

MiCOM C264/C264C Page 7/10

Available Values
Parameter
MENU TREE Or
signification
[min;max](step)(unit)
- MAN CLO LCK YES, NO Flag to permit or not
the locking for a
“normal close” operator
control.
- MAN CLO LDBL YES, NO Flag to permit or not a
control with a dead line
and a live bus for a
“normal close” operator
control.
- MAN CLO LLBD YES, NO Flag to permit or not a
control with a live line
and a dead bus for a
“normal close” operator
control.
- MAN CLO LDBD YES, NO Flag to permit or not a
control with a dead line
and a dead bus. for a
“normal close” operator
control.
- AUTO CLO LCK YES, NO Flag to permit or not
the locking in case of
auto-recloser control.
- AUTO CLO LDBL YES, NO Flag to permit or not a
control with a dead line
and a live bus in case
of auto-recloser
control.
- AUTO CLO LLBD YES, NO Flag to permit or not a
control with a live line
and a dead bus in case
of auto-recloser
control.
- AUTO CLO LDBD YES, NO Flag to permit or not a
control with a dead line
and a dead bus. in
case of auto-recloser
control.
AR
Circuit breaker name
- FIRST CYCLE MONO [100;5000](10)(ms) Time between the first
protection trip and the
Circuit Breaker close
order for a 1 phase
trip.
- FIRST CYCLE TRI [100;60000](10)(ms) Time between the first
protection trip and the
Circuit Breaker close
order for a 3 phases
trip.
C264/EN ST/B30 Settings

Page 8/10 MiCOM C264/C264C

Available Values
Parameter
MENU TREE Or
signification
[min;max](step)(unit)
- SECOND CYCLE [1000;3600000](1000)(ms) Time between the
second protection trip
and the Circuit Breaker
close order.
- THIRD CYCLE [1000;3600000](1000)(ms) Time between the third
protection trip and the
Circuit Breaker close
order.
- FOURTH CYCLE [1000;3600000](1000)(ms) Time between the
fourth protection trip
and the Circuit Breaker
close order.
- RECLAIM TIME [1000;600000](1000)(ms) Time during which the
Circuit Breaker must
remain closed to
consider that the
reclose has
succeeded.
- UNLOCK TIME [1000;600000](1000)(ms) Time during which the
Circuit Breaker must
remain closed after a
manual close or reinit
message in the lock
state to consider that
the unlocked has
succeeded
- MAN CLOSE TIME [1000;600000](1000)(ms) Time during which the
Circuit Breaker must
remain closed after a
manual close in clear
state to consider that
the closure has
succeeded and to
avoid locking
definitively in case of
trip.
- 1PH TRIP SCHEME 0 to 4 Indicates how to use
the autorecloser with 1
phase trip:
0: AR_NOT_USED
1: AR_1P
2: AR_1P3P
3: AR_1P3P3P
4: AR_1P3P3P3P
- 3PH TRIP SCHEME 0 to 4 Indicates how to use
the autorecloser with 3
phases trip:
0: AR_NOT_USED,
1: AR_3P,
2: AR_3P3P,
3: AR_3P3P3P,
4: AR_3P3P3P3P
Settings C264/EN ST/B30

MiCOM C264/C264C Page 9/10

Available Values
Parameter
MENU TREE Or
signification
[min;max](step)(unit)
DEVICE
short name 1
…
short name N
- TIME OPEN [0;1000](1)(ms) Time duration for the
open contact.
- TIME CLOSE [0;1000](1)(ms) Time duration for the
close contact.
BI
Bi 1
…
Bi N
- MOTION00 FILT [0;600](100)(ms) Time of non
complementarity
filtering in the state 00:
only use for double
digital input.
- MOTION11 FILT [0;600](100)(ms) Time of non
complementarity
filtering in the state 11:
only use for double
digital input.
- PERS OPEN FILT [0;1200](100)(ms) Time of persistence
filtering in the state
Open or 0
- PERS CLOSE FILT [0;1200](100)(ms) Time of persistence
filtering in the state
Close or 1
- TOGGLING OPTION YES, NO Flag to validate or
inhibit the The toggling
option.
MV
Mv 1
…
Mv N
- HYSTERESIS [1;50](1)(%) % of hysteresis applied
on thresholds.
- DEADBAND [1;50](1)(%) % of variation within
the Analogue Input is
not transmitted.
- THRESHOLD 1 [Min;Max](0.01)(XXX) Low low low threshold
(Lowest threshold of
the analogue input)
- THRESHOLD 2 [Min;Max](0.01)(XXX) Low low threshold
- THRESHOLD 3 [Min;Max](0.01)(XXX) Low threshold
- THRESHOLD 4 [Min;Max](0.01)(XXX) High threshold
- THRESHOLD 5 [Min;Max](0.01)(XXX) High high threshold
C264/EN ST/B30 Settings

Page 10/10 MiCOM C264/C264C

Available Values
Parameter
MENU TREE Or
signification
[min;max](step)(unit)
- THRESHOLD 6 [Min;Max](0.01)(XXX) High high high
threshold (highest
threshold of the
analogue input)
COMM. PORT
Com 1
…
Com 4
- BAUDRATE baudrate * Baudrate of the
communication port
among:
50,100,200,300,600,12
00,2400,4800,9600,19
200,38400, 56000,
64000.
- NB STOP BIT 1, 2 Number of stop bits
- NB BIT PER CHAR 7, 8 Number of bits per
character
- PARITY odd, even, none Parity
HMI
MAIN
- EXIT MT TIME [5;300](1)(s) Time after which the
Menu tree is
automatically left if
there is no pressed
button.
- BACK LIGHT DELAY [5;300](1)(s) Time after which the
back light disappears if
there is no pressed
button.
- SELECT EXIT TIME [5;300](1)(s) Maximum time
between selection and
execution orders.
- PASSWORD XXXX Password: needed to
modify parameters.
- BYPASS DELAY [20;120](1)(s) Time after which a
bypass is automatically
deselected.
BAY
Bay 0
…
Bay N
- SBMC DISPLAY YES, NO Flag to validate or
inhibit the display of
the SBMC mode
- DISPLAY DEV NAME YES, NO Flag to validate or
inhibit the display of
the Name od Devices
in the Bay Panel.

FIGURE 1 : MENU TREE FOLDER ORGANISATION

Communications C264/EN CT/B30

MiCOM C264/C264C

COMMUNICATIONS
Communications C264/EN CT/B30

MiCOM C264/C264C Page 1/92

CONTENT

1. SCOPE OF THE DOCUMENT 5

2. SCP COMMUNICATION 6
2.1 Communication on Station bus 6
2.1.1 Finality 6
2.1.2 Inputs 6
2.1.3 Supported services 7
2.1.4 Supported data objects 8

3. SCADA COMMUNICATION 9
3.1 Overview 9
3.2 SCADA common functionality 9
3.2.1 Interface to SCADA 9
3.2.2 Behaviour and specific treatments 10
3.2.3 Data sent to SCADA 11
3.2.4 Data sent to MiCOM C264 13
3.3 Slave DNP3 profile 14

4. IMPLEMENTATION TABLE 17
4.1 Slave IEC 60870-5-101 profile 21
4.1.1 System or device 21
4.1.2 Network configuration 21
4.1.3 Physical layer 22
4.1.4 Link layer 22
4.1.5 Application layer 23
4.1.6 Basic application functions 27
4.1.7 Protocol Requirements 31
4.1.8 Application Functions 31
4.2 Slave IEC 60870-5-104 Server profile 33
4.2.1 System or device 33
4.2.2 Network configuration (Network-specific parameter) 33
4.2.3 Physical layer (Network-specific parameter) 34
4.2.4 Link layer (Network-specific parameter) 34
4.2.5 Protocol Requirements 35
4.2.6 Application layer 36
C264/EN CT/B30 Communications

Page 2/92 MiCOM C264/C264C

5. BASIC APPLICATION FUNCTIONS 41

5.1 Slave DNP3 (TCP/IP) profile 44
5.2 Slave Modbus (MODICON) profile 45
5.2.1 Introducing MODBUS 45
5.2.2 Slave responses 46
5.2.3 Serial transmission mode 47
5.2.4 MODBUS Functions 47
5.2.5 Function 01 / 02 : Read Coil Status – Read Input Status 49
5.2.6 Function 03 / 04: Read Holding Registers / Input Registers 50
5.2.7 Function 05: Force Single Coil 52
5.2.8 Function 06: Preset single register 52
5.2.9 Function 08: Diagnostic [Sub-function 0 only] 53
5.2.10 Function 15 : Force Multiple Coils 53
5.2.11 Function 16 : Preset multiple registers 53

6. IED COMMUNICATION 54
6.1 Overview 54
6.2 IED Common functionality 55
6.2.1 Interface to IEDs 55
6.2.2 Behaviour 55
6.2.3 Data received from IEDs 59
6.2.4 Data sent to IEDs 60
6.2.5 Tunnelling 61
6.2.6 Limits and Performances 63
6.3 MODBUS communication 64
6.3.1 Finality 64
6.3.2 Interface to IEDs 64
6.3.3 Behaviour 64
6.3.4 Data received from IEDs 65
6.3.5 Data sent to IEDs 65
6.3.6 Error management 66
6.3.7 Limits and Performances 66
6.4 DNP 3.0 Communication 67
6.4.1 Finality 67
6.4.2 Interface to IEDs 67
6.4.3 Behaviour 68
6.4.4 Data received from IEDs 69
6.4.5 Data sent to IEDs 69
6.5 Master DNP3.0 Profile 70
Communications C264/EN CT/B30

MiCOM C264/C264C Page 3/92

7. DNP.3 LEVEL 3 IMPLEMENTATION TABLE 73

7.1 IEC 60870-5-103 Communication 77
7.1.1 Finality 77
7.1.2 Interface to IEDs 77
7.1.3 Behaviour 78
7.1.4 Data received from IEDs 79
7.1.5 Data sent to IEDs 80
7.2 IEC 60870-5-101 Communication 81
7.2.1 Finality 81
7.2.2 Master IEC 60870-5-101 profile 81
7.2.3 System or device 81
7.2.4 Network configuration 81
7.2.5 Physical layer 82
7.2.6 Link layer 82
7.2.7 Application layer 83
7.2.8 Basic application functions 87
7.2.9 Application Functions 90
C264/EN CT/B30 Communications

Page 4/92 MiCOM C264/C264C

BLANK PAGE
Communications C264/EN CT/B30

MiCOM C264/C264C Page 5/92

1. SCOPE OF THE DOCUMENT

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

• SCADA Communication: communication with an upper level SCADA system over

protocols (IEC 60870-5-101, IEC 60870-5-104, DNP3.0, MODBUS, DNP3 on TCP)

• IED Communication: communication with legacy IEDs. The MiCOM C264 is

considered as a master (IEC 60870-5-103, DNP3.0, MODBUS, IEC 60870-5-101)
C264/EN CT/B30 Communications

Page 6/92 MiCOM C264/C264C

2. SCP COMMUNICATION
2.1 Communication on Station bus
2.1.1 Finality
This item describes UCA2 implementation inside MiCOM C264.
2.1.2 Inputs
2.1.2.1 Information: MiCOM C264 application ! SCP
The type of information that can be transmitted are:

• Changes of state of binary inputs

• Measurements (Analogue or CT/VT)

• Counters

• Controls

• Control acknowledgements

• Time synchronisation message

• Records (Event, fault, disturbance)

• MiCOM C264 information (Init. report, Operating mode, control mode, Date)
2.1.2.2 Information SCP ! MiCOM C264 application
The type of information that can be transmitted are:

• Changes of state of binary inputs

• Measurements (Analogue or CT/VT)

• Counters

• Controls

• Control acknowledgements

• Time synchronisation message

• Request for records

• Database downloading
Communications C264/EN CT/B30

MiCOM C264/C264C Page 7/92

2.1.3 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
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
C264/EN CT/B30 Communications

Page 8/92 MiCOM C264/C264C

2.1.4 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
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
Communications C264/EN CT/B30

MiCOM C264/C264C Page 9/92

3. SCADA COMMUNICATION
3.1 Overview
A MiCOM C264 can be connected to a SCADA through networks using various protocols:
1. DNP3 (serial link)
2. T101 (serial link)
3. T104 (TCP/IP link)
4. DNP3 (TCP/IP link)
5. MODBUS (serial link)
It is possible to have:

• Two different protocols running in parallel on different links

• The same protocol on two links (redundant mode

• For protocols running on TCP/IP link, there is only one Ethernet port. So redundancy
is not available for those protocols, and they all are physically running on the same
network (including UCA2 protocol).
Common features to all SCADA communication and all protocols are specified below.
Specific features to each protocol are specified in subsequent paragraphs.
3.2 SCADA common functionality
3.2.1 Interface to SCADA
This paragraph describes the exchange of data between the “SCADA communication”
function and the Master SCADA. It is split into two sub-paragraphs:

• Inputs: data received from SCADA.

• Outputs: data sent from the “SCADA communication” function to SCADA.

For each kind of protocol, it is indicated if the data is treated or not:
3.2.1.1 Input

Data DNP3 T101 T104 DNP3 on IP MODBUS

Remote link initialisation Treated Treated Treated Treated Treated
General interrogation Treated Treated Treated Treated Not Treated
Control Treated Treated Treated Treated Treated
Setpoint Treated Treated Treated Treated Treated
Time synchronisation Treated Treated Treated Treated Not Treated
Database (download) Not Treated Not Treated Not Treated Not Treated Not Treated
C264/EN CT/B30 Communications

Page 10/92 MiCOM C264/C264C

3.2.1.2 Output

Data DNP3 T101 T104 DNP3 on MODBUS

IP
Digital input Treated Treated Treated Treated Treated
Dated Digital input Treated Treated Treated Treated Not Treated
Measurement (Events) Treated Treated Treated Treated Not Treated
Measurement (Cyclical) Treated Treated Treated Treated Treated
Counter Treated Treated Treated Treated Treated
Tap position Treated Treated Treated Treated Treated
Control acknowledgement Treated Treated Treated Treated Treated
Setpoint acknowledgement Treated Treated Treated Treated Treated
MiCOM C264 Disturbance Not Treated Not Treated Not Treated Not Treated Not Treated
Sequence Of Event File Not Treated Treated Treated Not Treated Not Treated

3.2.2 Behaviour and specific treatments

NOTE: In subsequent paragraphs, the master station (e.g.: SCADA) is
referred to as the controlling station.
3.2.2.1 Initialisation
There is a running database for each SCADA link. At initialisation, a GI is performed on the
application in order to initialise these databases.
The GI sequence consists of different requests to the MiCOM C264 application in order to
get the value and state of all data (Binary input, measurement, counter, step position
indication).
3.2.2.2 General interrogation
The Outstation interrogation function is used for updating the controlling station after the
internal station initialisation procedure, or when the controlling station detects a loss of
information, or when the link layer connection has been re-established. The general
interrogation function of the controlling station requests the MiCOM C264 to transmit the
actual values of all addressed datapoints.
The MiCOM C264 marks the end of the general interrogation procedure by sending an
indication to the controlling station when the protocols allow it.
3.2.2.3 Clock synchronisation
Clock in MiCOM C264 may be synchronised by the controlling station.
NOTE: The clock can be synchronised by other means: external clock,
Master Clock, operator. Only one source will be selected at a given
time. This selection is performed by the clock synchronisation function
based on configuration and priority level. However the controlling
station is not informed of this fact and must continue to send clock
synchronisation commands.
The controlling station must perform the correction made on the time sent in synchronisation
commands.
3.2.2.4 Local/remote mode
A substation or a bay can be in local or remote mode. When it is in local mode it can not be
controlled remotely and when it is in remote mode, it can not be controlled locally.
Each Mode can be associated to a binary input.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 11/92

3.2.2.5 Taking Control

A Substation can be configured in taking control mode. This means:

• At a given time, only one SCADA can send controls to the substation (the one which
has the control).

• To be allowed to send controls, a SCADA must take control of the substation by

sending a specific command to the MiCOM C264.
On each SCADA link, there is a binary input indicating if the corresponding SCADA has the
control of the substation.
On reception of a Taking Control command, the MiCOM C264:

• Puts the substation in Remote mode (if it was in Local Mode)

• Gives the control to the (last) SCADA which asks for it

− Reset the “Taking Control Binary input” of the SCADA which had previously the
control

− Set the “Taking Control Binary input” of the SCADA which asks the control
If the take control command is set for a SCADA, MiCOM C264 should refuse all commands
from other SCADAs.
3.2.2.6 SBMC mode
This mode is used to test a substation while it is in Remote mode. As this mode is a test
mode, MiCOM C264 won’t send all changes of state to SCADA.
When bay turns to SBMC mode, MiCOM C264 will send to SCADA all concerned data
(configured Bay Based in the SCE) at specific states defined in the SCE for the management
of SBMC.
For those data, change of state won’t be transmitted, but will be memorised by MiCOM C264
while the Bay is in SBMC mode.
When the Bay returns to Non SBMC mode, MiCOM C264 will send the current state of any
data that has changed whilst the Bay has been in SBMC mode.
3.2.2.7 Redundancy
Serial links can be configured as redundant. In this case, SCADA can send requests on both
serial links: “main link “or “redundant link”.
MiCOM C264 always responds on the link used by SCADA for requesting the slave
3.2.2.8 Synchrocheck
SCADA can send control to synchronised circuit breakers with a facility to bypass the
synchrocheck.
3.2.3 Data sent to SCADA
After the initialisation sequence, MiCOM C264 Slave sends the state of all of its data to the
SCADA. The current state of data is sent as state or as change of state messages,
depending on the protocol.
The data, which can be sent to SCADA, is detailed in the paragraphs below.
3.2.3.1 Binary inputs
Binary inputs can be sent as states or as changes of state depending on the protocol.
A binary input can be associated with a single point or a double point.
NOTE: Multipoint status is not treated.
C264/EN CT/B30 Communications

Page 12/92 MiCOM C264/C264C

3.2.3.2 Measurements
Measurements can be sent in various formats: float, integer, normalised, scaled…
Measurements can be sent as periodical messages or as changes of state: variation,
threshold, and invalidity.
The choices of format and mode of transmission are done by configuration according to the
protocol.
3.2.3.3 Counters
Counters can be sent as spontaneous messages (changes of state) or on demand (counter
General Interrogation).
The choice whether to use spontaneous messages for a counter is done by configuration,
according to the protocol.
3.2.3.4 Tap position
Tap position indication (TPI) can be sent to SCADA.
3.2.3.5 Sequence Of Events File (SOE)
The SOE is a circular file where Events of the MiCOM C264 are stored. There is one SOE
for each SCADA link.
The Events, which can be stored in SOE, are Binary Input and measurements. The choice is
done by configuration.
Following information in MiCOM C264 configuration are used to manage SOE file:

• For each SCADA protocol

− A flag indicating if SOE file have to be managed

− Identification of the SOE file on the link (Name, Address, …)

− The maximum size of the file

− The percentage of filling from which the MiCOM C264 will try to transmit the SOE
file

• For each BI / measurement

− A flag indicating if it must be stored in SOE

Rules for the SOE management are the following:

• At starting of the MiCOM C264, the SOE file is Empty

• When the SOE is full, the oldest Event is deleted and the new one is added

• As soon as the percentage of filling indicated in configuration is reached, the MiCOM

C264 tries to up-load the SOE file

• Once a SOE file has been successfully up-loaded, all Event sent are deleted from
SOE
3.2.3.6 Synchronisation status
MiCOM C264 can inform the controlling station about its synchronisation status.
According to the protocol, this may be done by a specific message or by a binary input.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 13/92

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.
At the end of the control sequence an acknowledgement is sent to SCADA if protocol allows
it.
3.2.4.2 Counter commands
The commands allowed on counters are:

• Reset of a group of Counters

• Reset of all Counters

• 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.
C264/EN CT/B30 Communications

Page 14/92 MiCOM C264/C264C

3.3 Slave DNP3 profile

DNP V3.00 Device Profile

Highest DNP Level Supported : Device Function :

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

MiCOM C264/C264C Page 15/92

DNP V3.00 Device Profile

Timeouts while waiting for:

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

Count > 1 # Never Always Sometimes Configurable

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

Queue # Never Always Sometimes Configurable

Clear Queue # Never Always Sometimes Configurable
• Select timeout : configurable (same value for all controls)

FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICES ONLY:

Reports Binary Input Change Events when no Reports time-tagged Binary Input Change Events
Specific variation requested: When no specific variation requested:
Never Never
# Only time-tagged # Binary Input Change With Time
Only non-time-tagged Binary Input Change With Relative Time
Configurable to send both, one or the other Configurable (attach explanation)
(explanation below)
User option to have all Binary Input
Change Events returned as either:
• time-tagged OR
• non-time-tagged
C264/EN CT/B30 Communications

Page 16/92 MiCOM C264/C264C

DNP V3.00 Device Profile

Send Unsolicited Responses: Send Static Data in Unsolicited Responses:

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

User option to return all static counters in User option to select roll over:
one of the following variations: • 32 bit counters roll over at 2^32.
• 32-Bit Binary Counter • 16 bit counters roll over at 2^16
• 32-Bit Binary Counter Without Flag
• 16-Bit Binary Counter
• 16-Bit Binary Counter Without Flag
Send Multi-Fragment Responses: # Yes No
Binary Input (BI) double management :
For a BI double, two binary inputs are configured, with a point address for the open contact and the
address + 1 for the close contact. All the BI double are transmitted this way.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 17/92

4. IMPLEMENTATION TABLE
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes (2)
(dec) (hex)
(dec) (hex)
1 0 Binary Input – All Variations 1 00,01,06,17,28
1 1 Binary Input 1 00,01,06, 17,28 129 00,17,28
1 2 Binary Input with Status 1 00,01,06,17,28 129 00,17,28
2 0 Binary Input Change - All Variations 1 06,07,08 129,130 17
2 1 Binary Input Change without Time 1
2 2 Binary Input Change with Time 1 06,07,08 129,130 17
2 3 Binary Input Change with Relative Time 1
10 0 Binary Output - All Variations 1
10 1 Binary Output
10 2 Binary Output Status 1
12 0 Control Block - All Variations (1)
12 1 Control Relay Output Block (1) 3,4,5,6 17,28 129 Request
echo
12 2 Pattern Control Block
12 3 Pattern Mask
20 0 Binary Counter - All Variations 1,7,8,9,10 00,01,06,17,28
20 1 32-Bit Binary Counter 1 00,01,06,17,28 129 00,17,28
20 2 16-Bit Binary Counter 1 00,01,06,17,28 129 00,17,28
20 3 32-Bit Delta Counter
20 4 16-Bit Delta Counter
20 5 32-Bit Binary Counter without Flag 1 00,01,06,17,28 129 00,17,28
20 6 16-Bit Binary Counter without Flag 1 00,01,06,17,28 129 00,17,28
20 7 32-Bit Delta Counter without Flag
20 8 16-Bit Delta Counter without Flag

1. Qualifier Codes (in hexa)

Request Qualifier
Response Qualifier (example of Binary Input)
Range of Points (8 bits) 0
Range of Points (16 bits) 1
All Points 6
Count of Points (8 bits) 7
Count of Points (16 bits) 8
List of Points (8 bits) 17
List of Points (16 bits) 28
2. Qualifier Codes 17 and 28 are only available on one point, except for controls (controls can be selected/executed on one
or more points)

3. “Binary Counter - All Variations” (Object 20, Var 0):

Functions 7,8 ,9 & 10 are only available with qualifiers 06, 17 and 28
C264/EN CT/B30 Communications

Page 18/92 MiCOM C264/C264C

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes (2)
(dec) (hex)
(dec) (hex)
21 0 Frozen Counter - All Variations 1 00,01,06,17,28
21 1 32-Bit Frozen Counter 1 00,01,06,17,28 129 00,17,28
21 2 16-Bit Frozen Counter 1 00,01,06,17,28 129 00,17,28
21 3 32-Bit Frozen Delta Counter
21 4 16-Bit Frozen Delta Counter
21 5 32-Bit Frozen Counter with Time of
Freeze
21 6 16-Bit Frozen Counter with Time of
Freeze
21 7 32-Bit Frozen Delta Counter with Time
of Freeze
21 8 16-Bit Frozen Delta Counter with Time
of Freeze
21 9 32-Bit Frozen Counter without Flag 1 00,01,06,17,28 129 00,17,28
21 10 16-Bit Frozen Counter without Flag 1 00,01,06,17,28 129 00,17,28
21 11 32-Bit Frozen Delta Counter without
Flag
21 12 16-Bit Frozen Delta Counter without
Flag
22 0 Counter Change Event - All Variations 1 06,07,08
22 1 32-Bit Counter Change Event without
Time
22 2 16-Bit Counter Change Event without
Time
22 3 32-Bit Delta Counter Change Event
without Time
22 4 16-Bit Delta Counter Change Event
without Time
22 5 32-Bit Counter Change Event with Time 1 06,07,08 129,130 17
22 6 16-Bit Counter Change Event with Time 1 06,07,08 129,130 17
22 7 32-Bit Delta Counter Change Event with
Time
22 8 16-Bit Delta Counter Change Event with
Time
23 0 Frozen Counter Event - All Variations 1 06,07,08
23 1 32-Bit Frozen Counter Event without
Time
23 2 16-Bit Frozen Counter Event without
Time
23 3 32-Bit Frozen Delta Counter Event
without Time
23 4 16-Bit Frozen Delta Counter Event
without Time
23 5 32-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17
23 6 16-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17
23 7 32-Bit Frozen Delta Counter Event with
Time
23 8 16-Bit Frozen Delta Counter Event with
Time
30 0 Analog Input - All Variations 1 00,01,06,17,28
Communications C264/EN CT/B30

MiCOM C264/C264C Page 19/92

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes (2)
(dec) (hex)
(dec) (hex)
30 1 32-Bit Analog Input 1 00,01,06,17,28 129 00, 17,28
30 2 16-Bit Analog Input 1 00,01,06,17,28 129 00,17,28
30 3 32-Bit Analog Input without Flag 1 00,01,06,17,28 129 00,17,28
30 4 16-Bit Analog Input without Flag 1 00,01,06,17,28 129 00,17,28
31 0 Frozen Analog Input - All Variations
31 1 32-Bit Frozen Analog Input
31 2 16-Bit Frozen Analog Input
31 3 32-Bit Frozen Analog Input with Time of
Freeze
31 4 16-Bit Frozen Analog Input with Time of
Freeze
31 5 32-Bit Frozen Analog Input without Flag
31 6 16-Bit Frozen Analog Input without Flag
32 0 Analog Change Event - All Variations 1 06,07,08
32 1 32-Bit Analog Change Event without
Time
32 2 16-Bit Analog Change Event without
Time
32 3 32-Bit Analog Change Event with Time 1 06,07,08 129,130 17
32 4 16-Bit Analog Change Event with Time 1 06,07,08 129,130 17
33 0 0 Frozen Analog Event - All Variations
33 1 32-Bit Frozen Analog Event without
Time
33 2 16-Bit Frozen Analog Event without
Time
33 3 32-Bit Frozen Analog Event with Time
33 4 16-Bit Frozen Analog Event with Time
40 0 Analog Output Status - All Variations
40 1 32-Bit Analog Output Status
40 2 16-Bit Analog Output Status
41 0 Analog Output Block - All Variations
41 1 32-Bit Analog Output Block 3,4,5,6 17,28 129 Request
echo
41 2 16-Bit Analog Output Block 3,4,5,6 17,28 129 Request
echo
50 0 Time and Date - All Variations
50 1 Time and Date 1,2 07 (quantity=1)
50 2 Time and Date with Interval
51 0 Time and Date CTO - All Variations
51 1 Time and Date CTO
51 2 Unsynchronized Time and Date CTO
52 0 Time Delay - All Variations
52 1 Time Delay Coarse
52 2 Time Delay Fine
60 0
C264/EN CT/B30 Communications

Page 20/92 MiCOM C264/C264C

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes (2)
(dec) (hex)
(dec) (hex)
60 1 Class 0 Data 1 06,07,08
60 2 Class 1 Data 1 06,07,08
20,21 06
60 3 Class 2 Data 1 06,07,08
20,21 06
60 4 Class 3 Data 1 06,07,08
20,21 06
70 0 File management – All variations
70 2 Authentication Object 29 5b 129 5b
70 3 File Command Object 25,27 5b 129 5b
70 4 File Command Status Object 26,30 5b 129 5b
70 5 File Transfert Object 1,2 5b 129 5b
70 7 File Description 28 5b 129 5b
80 1 Internal Indications

81 1 Storage Object
82 1 Device Profile
83 1 Private Registration Object
83 2 Private Registration Object Descriptor
90 1 Application Identifier
100 1 Short Floating Point
100 2 Long Floating Point
100 3 Extended Floating Point
101 1 Small Packed Binary-Coded Decimal
101 2 Medium Packed Binary-Coded Decimal
101 3 Large Packed Binary-Coded Decimal
No Object (Cold Restart)
No Object (Warm Restart)
No Object (Delay Measurement
Communications C264/EN CT/B30

MiCOM C264/C264C Page 21/92

4.1 Slave IEC 60870-5-101 profile

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

$ Function or ASDU is not used

⌧ Function or ASDU is used as standardized (default)

R Function or ASDU is used in reverse mode

B Function or ASDU is used in standard and reverse mode

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

$ Controling station definition (Master)

Controlled station definition (Slave)

4.1.2 Network configuration
(network-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ Point-to-point ⌧ Multipoint-party line

⌧ Multiple point-to-point ⌧ Multipoint-star

C264/EN CT/B30 Communications

Page 22/92 MiCOM C264/C264C

4.1.3 Physical layer

(network-specific parameter, all interfaces and data rates that are used are to be marked ‘X’)
Transmission speed (control direction)

Unbalanced interchange
CIRCUIT V24/V28 Balanced interchange
Circuit X24/X27
Standard Recommended if > 1200 bits/s

" 100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s " 56000 bits/s
" 200 bits/s ⌧ 4800 bits/s ⌧ 4800 bits/s " 64000 bits/s

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

⌧ 600 bits/s ⌧ 19200 bits/s ⌧ 19200 bits/s
⌧ 1200 bits/s ⌧ 38400 bits/s

Transmission speed (monitor direction)

Unbalanced interchange
Circuit V24/V28 Balanced interchange
Circuit X24/X27
Standard Recommended if > 1200 bits/s

" 100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s " 56000 bits/s

" 200 bits/s ⌧ 4800 bits/s ⌧ 4800 bits/s " 64000 bits/s

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

⌧ 600 bits/s ⌧ 19200 bits/s ⌧ 19200 bits/s
⌧ 1200 bits/s ⌧ 38400 bits/s

4.1.4 Link layer

(network-specific parameter, all options that are used are to be marked ‘X’. Specify the
maximum frame length. If a non-standard assignment of class 2 messages is implemented
for unbalanced transmission, indicate the type ID and COT of all messages assigned to
class 2.)
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively
in this companion standard.
Link transmission procedure Address field of the link

⌧ Balanced transmission " Not present (balanced transmission only)

⌧ Unbalanced transmission ⌧ One octet

⌧ Two octets

" Structured

⌧ Unstructured

Frame length (number of bytes)

255 Maximum length L in control direction

up to 255 Maximum length L in monitor direction – configurable

Communications C264/EN CT/B30

MiCOM C264/C264C Page 23/92

4.1.5 Application layer

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

⌧ One octet ⌧ Two octets

Information object address

(system-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ One octet ⌧ Structured

⌧ Two octets ⌧ Unstructured

⌧ Three octets

Cause of transmission
(system-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ One octet ⌧ Two octets (with originator address)

Selection of standard ASDUs

Process information in monitor direction
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <1> := Single-point information M_SP_NA_1

⌧ <2> := Single-point information with time tag M_SP_TA_1

⌧ <3> := Double-point information M_DP_NA_1

⌧ <4> := Double-point information with time tag M_DP_TA_1

⌧ <5> := Step-position information M_ST_NA_1

⌧ <6> := Step-position information with time tag M_ST_TA_1

$ <7> := BitString of 32 bit M_BO_NA_1

$ <8> := BitString of 32 bit with time tag M_BO_TA_1

⌧ <9> := Measured value, normalized value M_ME_NA_1

⌧ <10> := Measured value, normalized value with time tag M_ME_TA_1

⌧ <11> := Measured value, scaled value M_ME_NB_1

⌧ <12> := Measured value, scaled value with time tag M_ME_TB_1

⌧ <13> := Measured value, short floating point value M_ME_NC_1

⌧ <14> := Measured value, short floating point value with time tag M_ME_TC_1

⌧ <15> := Integrated totals M_IT_NA_1

C264/EN CT/B30 Communications

Page 24/92 MiCOM C264/C264C

⌧ <16> := Integrated totals with time tag M_IT_TA_1

$ <17> := Event of protection equipment with time tag M_EP_TA_1

$ <18> := Packed start events of protection equipment with time tag M_EP_TB_1

$ <19> := Packed output circuit transmission of protection equipment with time tag M_EP_TC_1

$ <20> := Packed single-point information with status change detection M_PS_NA_1

$ <21> := Measured value, normalized value without quality descriptor M_ME_ND_1

⌧ <30> := Single-point information with time tag CP56Time2a M_SP_TB_1

⌧ <31> := Double-point information with time tag CP56Time2a M_DP_TB_1

⌧ <32> := Step-position information with time tag CP56Time2a M_ST_TB_1

$ <33> := Bistring of 32 bits with with time tag CP56Time2a M_BO_TB_1

⌧ <34> := Measured value, normalized with time tag CP56Time2a M_ME_TD_1

⌧ <35> := Measured value, scaled with time tag CP56Time2a M_ME_TE_1

⌧ <36> := Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1

⌧ <37> := Integrated totals with time tag CP56Time2a M_IT_TB_1

$ <38> := Event of protection equipment with time tag CP56Time2a M_EP_TD_1

$ <39> := Packed start events of protection equipment with time tag CP56Time2a M_EP_TE_1

$ <40> := Packed output circuit information of protection equipment with time tag CP56Time2a M_EP_TF_1

Process information in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <45> := Single command C_SC_NA_1

⌧ <46> := Double command C_DC_NA_1

⌧ <47> := Regulating step command C_RC_NA_1

⌧ <48> := Set point command, normalized value C_SE_NA_1

⌧ <49> := Set point command, scaled value C_SE_NB_1

⌧ <50> := Set point command, short floating point value C_SE_NC_1

$ <51> := BitString of 32 bits C_BO_NA_1

System information in monitor direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <70> := End of initialisation M_EI_NA_1

Communications C264/EN CT/B30

MiCOM C264/C264C Page 25/92

System information in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <100> := Interrogation command C_IC_NA_1

⌧ <101> := Counter Interrogation Command C_CI_NA_1

$ <102> := Read command C_RD_NA_1

⌧ <103> := Clock synchronisation command C_CS_NA_1

⌧ <104> := Test command C_TS_NB_1

$ <105> := Reset process command C_RP_NC_1

$ <106> := Delay acquisition command C_CD_NA_1

Parameter in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ <110> := Parameter of measured value, normalized value P_ME_NA_1

$ <111> := Parameter of measured value, scaled value P_ME_NB_1

$ <112> := Parameter of measured value, short floating point value P_ME_NC_1

$ <113> := Parameter activation P_AC_NA_1

File transfer
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <120> := File ready F_FR_NA_1

⌧ <121> := Section ready F_SR_NA_1

⌧ <122> := Call directory, select file, call file, call section F_SC_NA_1

⌧ <123> := Last section, last segment F_LS_NA_1

⌧ <124> := Ack file, ack section F_AF_NA_1

⌧ <125> := Segment F_SG_NA_1

⌧ <126> := Directory F_DR_TA_1

Special use
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)
None
C264/EN CT/B30 Communications

Page 26/92 MiCOM C264/C264C

Type identifier and cause of transmission assignments

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

Type ID Cause of transmission

20 to 37 to
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45 46 47
36 41
<1> M_SP_NA_1 X X X X
<2> M_SP_TA_1 X X

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

MiCOM C264/C264C Page 27/92

Type ID Cause of transmission

20 to 37 to
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45 46 47
36 41
<47> C_RC_NA_1 X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X
<51> C_BO_NA_1 X
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1 X
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1 X X X X X
<105> C_RP_NA_1 X
<106> C_CD_NA_1 X
<110> P_ME_NA_1 X

<111> P_ME_NB_1 X
<112> P_ME_NC_1 X
<113> P_AC_NA_1 X
<120> F_FR_NA_1 X X X X
<121> F_SR_NA_1 X X X X
<122> F_SC_NA_1 X X X X
<123> F_LS_NA_1 X X X X
<124> F_AF_NA_1 X X X X
<125> F_SG_NA_1 X X X X
<126> F_DR_TA_1 X X

4.1.6 Basic application functions

Station initialisation
(station-specific parameter, mark ‘X’ if function is used)

" Remote initialisation

Cyclic data transmission

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Cyclic data transmission

Read procedure
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ Read procedure

Spontaneous transmission
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Spontaneous transmission
C264/EN CT/B30 Communications

Page 28/92 MiCOM C264/C264C

Link state between Controlling and Controlled Station

⌧ Management of the COM lost (Problem detecting on the link)

⌧ Management of the COM recovering (Problem not detecting on the link)

General interrogation
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ global

⌧ group 1 ⌧ group 7 ⌧ group 13

⌧ group 2 ⌧ group 8 ⌧ group 14

⌧ group 3 ⌧ group 9 ⌧ group 15

⌧ group 4 ⌧ group 10 ⌧ group 16

⌧ group 5 ⌧ group 11 Addresses per group have to be defined

⌧ group 6 ⌧ group 12

Counter General interrogation

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ global

⌧ group 1 ⌧ group 2 ⌧ group 3

⌧ group 4

Clock synchronisation
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Clock synchronisation

Notes: – The controlled station does not report the change of hour by
sending a clock synchronisation message (ASDU 103) to the
controlling station.
– When the controlling station send to controlled station a clock
synchronisation and if the system (includes controlled station), isn’t
synchronized by an other source : the clock synchronisation
response is positive.
– When the controlling station send to controlled station a clock
synchronisation and if the system (includes controlled station), is
synchronized by an other source : the clock synchronisation
response is negative.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 29/92

Command transmission
(object -specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Direct command transmission

⌧ Direct set-point command transmission

⌧ Select and execute command

⌧ Select and execute set-point command

⌧ C_SE ACTTERM used

⌧ No additional definition

$ Short pulse duration (duration determined by a system parameter in the outstation)

$ Long pulse duration (duration determined by a system parameter in the outstation)

$ Persistent output

Transmission of integrated totals

(object -specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Mode A : local freeze with spontaneous transmission

$ Mode B : local freeze with counter interrogation

⌧ Mode C : freeze and transmit by counter interrogation commands

$ Mode D : freeze by counter interrogation command, frozen values reported

spontaneously

⌧ Counter read ⌧ General request counter

⌧ Counter freeze without reset ⌧ Request counter group 1

⌧ Counter freeze with reset ⌧ Request counter group 2

⌧ Counter reset ⌧ Request counter group 3

⌧ Request counter group 4

Parameter loading
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ Threshold value

$ Smoothing factor

$ Low limit for transmission of measured value

$ High limit for transmission of measured value

C264/EN CT/B30 Communications

Page 30/92 MiCOM C264/C264C

Parameter activation
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

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

Test procedure
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Test procedure

File transfer
(station-specific parameter), mark ‘X’ if function is used)
File transfert in monitor direction

" Transparent file

$ Transmission of disturbance data of protection equipment

⌧ Transmission of sequences of events

$ Transmission of sequences of recorded analogue values

File transfer in control direction

$ Transparent file

Background scan
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Background scan

Acquisition of transmission delay

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ Acquisition of transmission delay

Management events priorities

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ Digitals Inputs and Analogs Inputs, management events priorities.

See : T101 standard Amendment 2 §7.2.2.2
Communications C264/EN CT/B30

MiCOM C264/C264C Page 31/92

4.1.7 Protocol Requirements

Class 1 data
The following types of information must be configured at the controlled station to be Class 1 :
The following types of information are to be configured at the controlled station to be Class 1:

! Single point information with or without time tag (on change)

! Double point information with or without time tag (on change)
! Step position information with or without time tag (on change)
! Measured value, normalised with or without time tag (on change)
! Measured value, scaled with or without time tag (on change)
! Measured value, floated with or without time tag (on change)
! Integrated totals with or without time tag (on change)
! Integrated totals with or without time tag (on change)
! Time messages
! All command responses (ACT_CONF, and ACT_TERM)

Class 2 data
The following types of information must be configured at the controlled station to be Class 2 :

! Single point information (GI scan, or BackGroundScan cycle)

! Double point information (GI scan, or BackGroundScan cycle)
! Step position information with or without time tag (on change)
! Measured values, normalised (GI scan, or Periodic cycle, or BackGroundScan cycle)
! Measured values, scaled (GI scan, or Periodic cycle, or BackGroundScan cycle)
! Measured values, floated (GI scan, or Periodic cycle, or BackGroundScan cycle)
! Step position values (GI scan, or BackGroundScan cycle)
! Integrated totals (Counter GI scan)

4.1.8 Application Functions

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

Page 32/92 MiCOM C264/C264C

Data Acquisition by Polling

The default for all analogue values shall be reporting as Class 2 data (COT=1,
periodic/cyclic, or COT = 2, BackgroundScan cyclic).
Values returned as Class 2 data do not have a time tag (since they are constantly repeated).
The controlled station may return Class 1 data in response to a Class 2 request if no Class 2
data is available and Class 1 data is awaiting transmission.
At the controlled station, if a request for Class 2 data is received and no data is available a
negative response, data not available, shall be returned to the controlling Station. The
negative response may be a fixed length frame (FC=9), which in this case is treated as a
NACK.
Normal Acquisition of Events
The default for all status changes are reported as Class 1 data (COT=3, spontaneous).
Values returned as Class 1 data shall have a time tag (either CP24Time2a, or CP56Time2a).
Status changes at the controlled station shall cause the ACD bit to be set in the next Class 1
or Class 2 data response. The controlling station shall respond to ACD set by inserting a
scan for Class 1 (spontaneous) data as the next scan.
The response to a Class 1 data request shall also have the ACD bit set if more Class 1 data
is awaiting transmission. In this case a further scan for Class 1 data shall be scheduled by
the controlling station.
Abnormal Acquisition of Events
At the controlled station, if a request for Class 1 data is received and no data is available an
error should be raised and a negative response, data not available, returned to the
controlling Station. The negative response shall be a fixed length frame (FC=9), which in
this case is treated as a NACK.
At the controlling station, if a response to a scan for Class 1 data indicates no data is
available an error shall be raised and scanning returned to Class 2 data requests.
General Interrogation
The GI return the current status information directly from the Computer database.
Time tags are not used for data items returned as part of the GI response.
The GI groups are supported so, these will be set up in the Computer configuration and each
of the (up to 16) groups shall be requested/reported individually.
Clock synchronisation
The System (including the controlled station) may have different synchronisation sources
(IRIG-B, SCADA).
When the controlling station send to controlled station a clock synchronisation and if the
system isn’t synchronized by an other source : the clock synchronisation response is
positive.
When the controlling station send to controlled station a clock synchronisation and if the
system is synchronized by an other source : the clock synchronisation response is negative.
All Class 1 data are time-tagged with :
Either the 3 bytes time-stamp (CP24Time2a), giving minutes and milliseconds within the
hour, or the 7 bytes time-stamp (CP56Time2a), giving minutes, milliseconds, hours, day,
month and year according to the Computer configuration.
The invalid bit in the time-stamp is set when the computer is not synchronised.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 33/92

Command transmission
All control commands shall be Select before Execute, or Direct Execute.
For only the control commands : Activation termination is returned to the controlling station to
signal the end of a control sequence.
The QU field of the Qualifier of Command shall be set to zero (0), no additional definition.
Test procedure
A test command may be issued by the controlling station to ensure the availability of the
communications link and the commands subsystem.
Test commands are received at the controlled station on the active link. The controlled
station mirrors the test command, on the link from which it was received, with a cause of
transmission indicating activation confirmation.
An error response should be sent if the command is incorrect, with a cause of transmission
indicating negative activation confirmation.
4.2 Slave IEC 60870-5-104 Server profile
This companion standard presents sets of parameters and alternatives from which subsets
have to be selected to implement particular telecontrol systems. Certain parameter values,
such as the choice of “structured” or “unstructured” fields of the INFORMATION OBJECT
ADDRESS of ASDU represent mutually exclusive alternatives. This means that only one value
of the defined parameters is admitted per system. Other parameters, such as the listed set of
different process information in command and in monitor direction allow the specification of
the complete set or subsets, as appropriate for given applications. This clause summarises
the parameters of the previous clauses to facilitate a suitable selection for a specific
application. If a system is composed of equipment stemming from different manufacturers it
is necessary that all partners agree on the selected parameters.
Paragraph in grey are those which are not applicable for the IEC 60870-5-104 profile.
The selected parameters should be filled up (# $ !).
NOTE: In addition, the full specification of a system may require individual
selection of certain parameters for certain parts of the system, such as
the individual selection of scaling factors for individually addressable
measured values.
To simplify the PID , we use the following conventions:
# Not supported
! Supported
4.2.1 System or device
# System definition
# Controlling station definition (Master)
! Controlled station definition (Slave)
4.2.2 Network configuration (Network-specific parameter)
# Point-to-point # Multipoint-party line
# Multiple point-to-point # Multipoint-star
C264/EN CT/B30 Communications

Page 34/92 MiCOM C264/C264C

4.2.3 Physical layer (Network-specific parameter)

Transmission speed (control direction):

Unbalanced interchange Unbalanced interchange Balanced interchange

circuit V.24/V.28 circuit V.24/V.28 circuit X.24/X.27, V35
Standard Recommended if >1 200 bit/s
# 100 bit/s # 2 400 bit/s # 2 400 bit/s
# 200 bit/s # 4 800 bit/s # 4 800 bit/s
# 300 bit/s # 9 600 bit/s # 9 600 bit/s
# 600 bit/s # 19 200 bit/s # 19 200 bit/s
# 1 200 bit/s # 38 400 bit/s
# 56 000 bit/s
# 64 000 bit/s

Transmission speed (monitor direction):

Unbalanced interchange Unbalanced interchange Balanced interchange

circuit V.24/V.28 circuit V.24/V.28 circuit X.24/X.27, V35
Standard Recommended if >1 200 bit/s
# 100 bit/s # 2 400 bit/s # 2 400 bit/s
# 200 bit/s # 4 800 bit/s # 4 800 bit/s
# 300 bit/s # 9 600 bit/s # 9 600 bit/s
# 600 bit/s # 19 200 bit/s # 19 200 bit/s
# 1 200 bit/s # 38 400 bit/s
# 56 000 bit/s
# 64 000 bit/s

4.2.4 Link layer (Network-specific parameter)

(Network-specific parameter, all options that are used should be filled up (# $ !). Specify
the maximum frame length. If a non-standard assignment of class 2 messages is
implemented for unbalanced transmission, indicate the type ID and COT of all messages
assigned to class 2.)
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively
in this companion standard.

Link transmission procedure Address field of the link

# Balanced transmission # Not present (balanced transmission only)
# Unbalanced transmission # One octet
# Two octets

# Structured
# Unstructured
Communications C264/EN CT/B30

MiCOM C264/C264C Page 35/92

Frame length
_255_ Maximum length L (number of bytes)
When using an unbalanced link layer, the following ASDU types are returned in class 2
messages (low priority) with the indicated causes of transmission:
# The standard assignment of ASDUs to class 2 messages is used as follows :

Type Identification Cause of transmission

9,11,13,21 <1>

# A special assignment of ASDUs to class 2 messages is used as follows :

Type Identification Cause of transmission

1,3,5 <20> to <41>

NOTE : In response to a class 2 poll, a controlled station prevent the

controlling station with ACD parameter, when there is no class 2 data
available.
4.2.5 Protocol Requirements
4.2.5.1 Event
The following types of information are to be configured at the controlled station to be Event:

! Single point information with or without time tag (on change)

! Double point information with or without time tag (on change)
! Step position information with or without time tag (on change)
! Measured value, normalised with or without time tag (on change)
! Measured value, scaled with or without time tag (on change)
! Measured value, floated with or without time tag (on change)
! Integrated totals with or without time tag (on change)

4.2.5.2 Static
The following types of information are to be configured at the controlled station to be Static :

! Single point information (GI scan, or BackGroundScan cycle)

! Double point information (GI scan, or BackGroundScan cycle)
! Measured values, normalised (GI scan, or Periodic cycle, or BackGroundScan cycle)
! Measured values, scaled (GI scan, or Periodic cycle, or BackGroundScan cycle)
! Measured values, floated (GI scan, or Periodic cycle, or BackGroundScan cycle)
! Step position values (GI scan, or BackGroundScan cycle)
! Integrated totals (Counter GI scan)
C264/EN CT/B30 Communications

Page 36/92 MiCOM C264/C264C

4.2.6 Application layer

Transmission mode for application data
Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used
exclusively in this companion standard.
Common address of ASDU
(System-specific parameter)
The address field of the link and the common address of ASDU could have a different
number of bytes

# One octet ! Two octets

Information object address

(System-specific parameter)

# One octet ! Structured

# Two octets ! Unstructured
! Three octets

Cause of transmission
(System-specific parameter)

# One octet ! Two octets (with originator address)

Length of APDU
(System-specific parameter)
The maximum length of APDU is 253 (default) The maximum length may be reduced by the
system.

Configurable Maximum length of APDU per system

Selection of standard ASDUs

Process information in monitor direction
(Station-specific parameter)

! <1>: = Single-point information M-SP-NA-1

# <2>: = Single-point information with time tag M-SP-TA-1
! <3>: = Double-point information M-DP-NA-1
# <4>: = Double-point information with time tag M-DP-TA-1
! <5>: = Step position information M-ST-NA-1
# <6>: = Step position information with time tag M-ST-TA-1
# <7>: = Bit-string of 32 bit M-BO-NA-1
# <8>: = Bit-string of 32 bit with time tag M-BO-TA-1
! <9>: = Measured value, normalised value M-ME-NA-1
# <10>: = Measured value, normalised value with time tag M-ME-TA-1
! <11>: = Measured value, scaled value M-ME-NB-1
# <12>: = Measured value, scaled value with time tag M-ME-TB-1
! <13>: = Measured value, short floating point value M-ME-NC-1
# <14>: = Measured value, short floating point value with time tag M-ME-TC-1
Communications C264/EN CT/B30

MiCOM C264/C264C Page 37/92

! <15>: = Integrated totals M-IT-NA-1

# <16>: = Integrated totals with time tag M-IT-TA-1
# <17>: = Event of protection equipment with time tag M-EP-TA-1
# <18>: = Packed starts events of protection equipment with time tag M-EP-TB-1
# <19>: = Packed output circuit information of protection equipment M-EP-TC-1
with time tag
# <20>: = Packed single-point information with status change detection M-PS-NA-1
# <21>: = Measured value, normalised value without quality descriptor M-ME-ND-1

Process information in monitor direction with the Extension of time tag

(Station-specific parameter)

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

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

Process information in control direction

(station-specific parameter)

! <45>: = Single command C-SC-NA-1

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

NOTE : Time tag command (ASDU 58 to 63) are managed as standard

command (ASDU 45 to 50), i.e. the time tag is not used.
C264/EN CT/B30 Communications

Page 38/92 MiCOM C264/C264C

System information in monitor direction

(station-specific parameter)

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

System information in control direction

(station-specific parameter)

! <100>: = Interrogation commands C-IC-NA-1

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

Parameter in control direction

(station-specific parameter)

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

# <111>: = Parameter of measured value, scaled value P-ME-NB-1
# <112>: = Parameter of measured value, short floating point value P-ME-NC-1
# <113>: = Parameter activation P-AC-NA-1

File transfer
(station-specific parameter)

! <120>: = File ready F-FR-NA-1

! <121>: = Section ready F-SR-NA-1
! <122>: = Call directory, select file, call file, call section F-SC-NA-1
! <123>: = Last section, last segment F-LS-NA-1
! <124>: = Ack file, ack section F-AF-NA-1
! <125>: = Segment F-SG-NA-1
! <126>: = Directory F-DR-TA-1

File transfer is only implemented in computer gateway.

Special use
(private range)

# <136>: = Data base version M-DB-NA-1

# <137>: = Regulating delay command C-RC-NB-1

Type identifier and cause of transmission assignments

(station-specific parameters)

X Mark type identification/cause of transmission combinations: ‘X’ if used

Shaded boxes are not required
Blank = function or ASDU is not used
. Required in 1995 standard, suppressed in 2000.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 39/92

Type ID Cause of transmission

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41

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

Page 40/92 MiCOM C264/C264C

Type ID Cause of transmission

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41

<51> C_BO_NA_1
<58> C_SC_TA_1 X X X X X X X X
<59> C_DC_TA_1 X X X X X X X X
<60> C_RC_TA_1 X X X X X X X X
<61> C_SE_TA_1 X X X X X X X X
<62> C_SE_TB_1 X X X X X X X X
<63> C_SE_TC_1 X X X X X X X X
<64> C_BO_TA_1
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1
<105> C_RP_NA_1
<106> C_CD_NA_1
<107> C_TS_TA_1 X X X
<110> P_ME_NA_1
<111> P_ME_NB_1
<112> P_ME_NC_1
<113> P_AC_NA_1
<120> F_FR_NA_1 X X
<121> F_SR_NA_1 X X
<122> F_SC_NA_1 X X X
<123> F_LS_NA_1 X X
<124> F_AF_NA_1 X X
<125> F_SG_NA_1 X X
<126> F_DR_TA_1 X X

* COT <45> := Unknown Cause of Transmission

Communications C264/EN CT/B30

MiCOM C264/C264C Page 41/92

5. BASIC APPLICATION FUNCTIONS

Station initialisation
(Station-specific parameter)

# Remote initialisation

(Between Reset User ASDU’s).

Cyclic data transmission
(Station-specific parameter)

! Cyclic data transmission

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

Read procedure
(Station-specific parameter)

# Read procedure

Spontaneous transmission
(Station-specific parameter)

! Spontaneous transmission

Double transmission of information objects with cause of transmission spontaneous

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

# Single point information M_SP_NA_1, M_SP_TA_1, M_SP_TB_1 and

M_PS_NA_1
# Double point information M_DP_NA_1, M_DP_TA_1 and M_DP_TB_1
# Step position information M_ST_NA_1, M_ST_TA_1 and M_ST_TB_1
# Bitstring of 32 bit M_BO_NA_1, M_BO_TA_1 and M_BO_TB_1 (if
defined for a specific project)
# Measured value, normalized value M_ME_NA_1, M_ME_TA_1, M_ME_ND_1 and
M_ME_TD_1
# Measured value, scaled value M_ME_NB_1, M_ME_TB_1 and M_ME_TE_1
# Measured value, short floating point M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1
number
C264/EN CT/B30 Communications

Page 42/92 MiCOM C264/C264C

General interrogation
(System or station-specific parameter)

! Global
! Group 1 ! Group 7 ! Group 13
! Group 2 ! Group 8 ! Group 14
! Group 3 ! Group 9 ! Group 15
! Group 4 ! Group 10 ! Group 16
! Group 5 ! Group 11
! Group 6 ! Group 12 Information Object Addresses
assigned to each group must be
shown in a separate table

Counter General interrogation

(System or station-specific parameter)

! Global
! Group 1 ! Group 3
! Group 2 ! Group 4

Clock synchronisation
(Station-specific parameter)

! Clock synchronisation

Command transmission
(Object-specific parameter)

! Direct command transmission ! Select and execute command

! Direct set point command transmission ! Select and execute set point
command
! C-SE ACTTERM used

! No additional definition
# Short pulse duration (duration determined by a system parameter in the outstation)
# Long pulse duration (duration determined by a system parameter in the outstation)
# Persistent output

Transmission of integrated totals

(Station or object-specific parameter)

! Mode A: local freeze with spontaneous.

# Mode B: local freeze with counter.
! Mode C: freeze and transmit by counter interrogation.
# Mode D: freeze by counter interrogation command, frozen values reported.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 43/92

! Counter read ! General request counter

! Counter freeze without reset ! Request counter group 1
! Counter freeze with reset ! Request counter group 2
! Counter reset ! Request counter group 3
! Request counter group 4

Parameter loading
(Object-specific parameter)

# Threshold value
# Smoothing factor
# Low limit for transmission of measured value
# High limit for transmission of measured value

Parameter activation
(Object-specific parameter)

# Act/Desactivation of persistent cyclic or periodic transmission of the addressed object

Test procedure
(Station-specific parameter)

! Test procedure

File transfer
(Station-specific parameter)
File transfer in monitor direction

# Transparent file
# Transmission of disturbance data of protection equipment
! Transmission of sequences of events
# Transmission of sequences of recorded analogue values

Only in computer gateway

File transfer in control direction

# Transparent file

Background scan
(Station-specific parameter)

! Background scan

Acquisition of transmission delay

(Station-specific parameter)

# Acquisition of transmission delay

Management events priorities

(Station-specific parameter)

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

events priorities.
C264/EN CT/B30 Communications

Page 44/92 MiCOM C264/C264C

Definition of time outs

Parameter Default value Remarks Selected value

t0 30s Time out of connection establishment configurable
t1 15s Time out of send or test APDUs configurable
t2 10s Time out for acknowledges in case of no configurable
data messages t2 < t1
t3 20s Time out for sending test frames in case of configurable
a long idle state

Maximum range of values for all time outs: 1 to 255 s, accuracy 1 s

Maximum number of outstanding I format APDUs k and latest acknowledge

Parameter Default value Remarks Selected value

K 12 APDUs Maximum difference receive sequence configurable
number to send state variable
W 8 APDUs Latest acknowledge after receiving w I- configurable
format APDUs

Maximum range of values k: 1 to 255 APDUs, accuracy 1 APDU

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

Parameter Value Remarks

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

RFC 2200 suite

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

! Ethernet 802.3
# Serial X.21 interface
# Other selection from RFC 2200

5.1 Slave DNP3 (TCP/IP) profile

See Slave DNP3 Profile (chapter 3.2)
Communications C264/EN CT/B30

MiCOM C264/C264C Page 45/92

5.2 Slave Modbus (MODICON) profile

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

Query message from Server Response message from Slave

Function code Function code
Eight-bit Data bytes Eight-bit data bytes
Error check Error check

5.2.1.1 Device address field

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

Page 46/92 MiCOM C264/C264C

5.2.1.4 Error check field

The error-checking field contains a 16-bit value implemented as two 8-bit bytes [low
significant byte first]. The error check value is the result of a Cyclical Redundancy Check
[CRC] calculation performed on the message contents.

The gateway do not reply to corrupted data messages, i.e when the CRC is not
correct or when parity is not correct.

5.2.2 Slave responses

5.2.2.1 When the slave answers
Except for broadcast messages (no response in this case), when a master device sends a
query to a slave device it expects a normal response.
One of four possible events can occur from the master’s query :

• If the slave device receives the query without communication error, and can handle
the query normally, it returns a normal response.

• If the slave does not receive the query due to a communication error, no response is
returned. The master program will process a timeout condition for query.

• If the slave receives the query, but detect a communication error [ bad CRC or framing
error for example ], no response is returned. The master program will process a
timeout condition for query.

• If the slave device receives the query without communication error, but cannot handle
it, the salve will return an exception response informing the master of the nature of the
error.
5.2.2.2 Exception Responses Codes
The exception code is sent as an 8-bit data, the range of valid codes is 1-8 in the protocol.
Supported exception responses codes are :

Code Name Meaning

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

MiCOM C264/C264C Page 47/92

Code Name Meaning

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

5.2.3 Serial transmission mode

When messages are transmitted on standard MODBUS serial networks, each byte is sent
LSB first.
The format for each byte in MODBUS RTU mode is:

• Coding system : 8-bit binary, hexadecimal 0-9, A-F

Two hexadecimal characters contained in each 8-bit field of
the message

• Bits per Byte : 1 start bit8 data bits,

LSB sent first2 stop bits if no parity, or 1 parity bit and 1 stop
bit)

• Error Check Field : Cyclical Redundancy Check (CRC-16)

5.2.4 MODBUS Functions
MODBUS defines 24 functions, valid codes are in the range of 1-24.
C264/EN CT/B30 Communications

Page 48/92 MiCOM C264/C264C

5.2.4.1 Supported functions

Code Function name Supported

01 READ COIL STATUS [ identical to function code 02 ] YES
02 READ INPUT STATUS [ identical to function code 01 ] YES
03 READ HOLDING REGISTERS [ identical to function code 04 ] YES
04 READ INPUT REGISTERS [ identical to function code 03 ] YES
05 FORCE SINGLE COIL YES
06 PRESET SINGLE REGISTER YES
07 READ EXCEPTION STATUS YES
08 DIAGNOSTICS [ only sub function 0 is supported ] YES
09 PROGRAM 484 NO
10 POLL 484 NO
11 FETCH COMM. EVENT CTR. NO
12 FETCH COMM. EVENT LOG NO
13 PROGRAM CONTROLLER NO
14 POLL CONTROLLER NO
15 FORCE MULTIPLE COILS [ identical to function code 05, one point only ] YES
16 PRESET MULTIPLE REGISTERS [ identical to function code 06, one YES
point only ]

17 REPORT SLAVE ID NO
18 PROGRAM 884/M84 NO
19 RESET COMM. LINK NO
20 READ GENERAL REFERENCE NO
21 WRITE GENERAL REFERENCE NO
22 MASK WRITE 4X REGISTER NO
23 READ/WRITE 4X REGISTERS NO
24 READ FIFO QUEUE NO

5.2.4.2 General format of MODBUS functions

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

MiCOM C264/C264C Page 49/92

A response message typically contains some of the following fields :

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

Slave Function Code Starting Starting No. of No. of CRC CRC

Address Address Address
= 01 Points (H) Points (L) (H)
(H) (L) (L)
The query message specifies the starting coil address and the quantity of coils to be read.
C264/EN CT/B30 Communications

Page 50/92 MiCOM C264/C264C

Response :

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

Slave Function Code Starting Starting No. of No. of CRC CRC

Address Address Address
= 03 Points (H) Points (L) (H)
(H) (L) (L)
The query message specifies the starting register and the quantity of registers to be read.
Response :

Slave Function Byte Count Data Data Data Data Data Data CRC CRC
address code = <nbytes>
(H) (L) (H) (L) (H) (L) (L) (H)
= 03 #1 #1 #i #i #nbytes/ 2 #nbytes/
2

The register data in the response message are packed as two bytes per register, with the
binary contents right justified within each byte. For each register, the first byte contains the
high order bits and the second contains the low order bits.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 51/92

Important notes :
1. If the starting address is not a point in configuration, the message will be not be
accepted, and an error exception 2 will be returned.
2. If the starting address is in configuration and if there is some “holes” (addresses not in
configuration) theses holes will be padded with the value 0
5.2.6.1 Signed normalised coding
The signed normalised coding is used to encode the 16 bits-registers. Analogue maximal
value will be coded 7FFFh (decimal value + 32767), and minimal value will be coded 8000h
(decimal value –32768).
For this mode, the gateway may now code the value on 8 to 16 bits [ low part of the register
will be used ]. But, 16 bits is normally the standard to use the full scale conversion.
Example :
in configuration the maximal value for an analogue point is +3000 and minimum value for
this analogue is 0.
That means that when the analogue is received with value 0 from the system, the gateway
will send to the SCADA the register with 8000h value. If this analogue is equal to the
maximal value +3000, the value sent to the SCADA is 7FFFh. Calculation is linear for the
coding between the min and max values.
5.2.6.2 Unsigned normalised coding
The unsigned normalised coding is used to encode the 16 bits-registers. Analogue maximal
value will be coded FFFFh (decimal value + 65535), and minimal value will be coded 0000h
(decimal value 0).
For this mode, the gateway may now code the value on 8 to 16 bits [ low part of the register
will be used ]. But, 16 bits is normally the standard to use the full scale conversion.
Example :
in configuration the maximal value for an analogue point is +3000 and minimum value for
this analogue is 0.
That means that when the analogue is received with value 0 from the system, the gateway
will send to the SCADA the register with 0h value. If this analogue is equal to the maximal
value +3000, the value sent to the SCADA is FFFFh. Calculation is linear for the coding
between the min and max values.
5.2.6.3 Natural coding
The natural coding is used to encode data without any calculation. That’s means that integer
value will be send.
Example :
if the gateway receives the value 10.xxxx, the value 0Ah will be set in the appropriate
register. The gateway receives the value –10,xxxx the value FFF6h will be coded. Sent
values are considered as signed values which are included between –32768 and +32767.
When minimum and maximum values are reached values FFF6h and FFFFh are
respectively sent.
C264/EN CT/B30 Communications

Page 52/92 MiCOM C264/C264C

5.2.7 Function 05: Force Single Coil

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

Slave Function Code Point Point Force Force CRC CRC

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

Slave Function Code Point Point Force Force CRC CRC

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

Slave Function Code Point Point Force Force CRC CRC

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

Slave Function Code Point Point Force Force CRC CRC

Address Address Address Data Data
= 06 (L) (H)
(H) (L) (H) (L)
The normal response is an echo of the query, returned after the register has been preset.
NOTE : Only natural setpoints are managed by this function (no scaling is
done)
Communications C264/EN CT/B30

MiCOM C264/C264C Page 53/92

5.2.9 Function 08: Diagnostic [Sub-function 0 only]

This request function 08 sub-function 0 is used to test the transmission.
Query :

Slave Function Code Sub Function Sub Function Data Data CRC CRC
Address code code
= 08 (H) (L) (L) (H)
(H) (L)
The query message specifies the data that will be echoed.
Response :

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

Page 54/92 MiCOM C264/C264C

6. IED COMMUNICATION
6.1 Overview
Different types of IEDs are connected to a MiCOM C264 through networks using various
legacy protocols:
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 6.2
Specific features to each protocol are specified in subsequent paragraphs.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 55/92

6.2 IED Common functionality

6.2.1 Interface to IEDs
6.2.1.1 Input

Data Note
Digital input Treated
Measurement Treated
Default position Depending on the protocol
Counter Not Treated
Tap position Not Treated
Control acknowledgement Treated
Setpoint acknowledgement Depending on the protocol
Alarm Not Treated
Disturbance record Depending on the protocol
Tunnelling Frame response Depending on the protocol

6.2.1.2 Output

Data Note
Control Treated
Setpoint Depending on the protocol
Alarm acknowledgement Not Treated
Tunnelling Frame question Depending on the protocol
Time synchronisation Treated

6.2.2 Behaviour
6.2.2.1 Network supervision
The number of networks and IEDs is known by configuration.
Each network is managed independently of the other networks.
The management of a network consists of:

• Initialising the serial line

At start-up of the network monitoring, the serial line has to be initialised according to
the configuration.

• Synchronising the IEDs connected to the network.

• Polling the IEDs

This polling allows to connect IEDs, to exchange data with IEDs and to monitor the
connection of IEDs.

• Performing the monitoring of the each IED connected to this network.

Each IED is managed independently of the other IEDs. The state of each IED, i.e.
connected, disconnected, is monitored and every change of state is signalled to the
MiCOM C264 management function.
C264/EN CT/B30 Communications

Page 56/92 MiCOM C264/C264C

6.2.2.2 Time synchronisation

If the network has to be synchronised, the synchronisation is performed in one of two ways:
1. At connection of an IED, a synchronisation frame is sent to this IED.
2. Regularly, a synchronisation frame is broadcasted on the network.
When this is supported by the IEDs, the calculation of the transmission delay is performed.
NOTE: The synchronisation is a network attribute [not an IED attribute]. That
means, that the synchronisation is either sent to all the IEDs, or is not
sent.
6.2.2.3 Polling of IED
Once the line is initialised, the MiCOM C264 has to try to connect IEDs and to manage
exchanges of data with each IEDs.
That’s done by polling: cyclically the MiCOM C264 questions each IED one after the other.
The polling manages the following items:

• Sequencing the questioning of the IEDs

• Connection of an IED [when a disconnected IED responds, it becomes Connected]

• Repetitions [if an IED doesn’t answer to a request, this request will be repeated the
next cycle]

• Disconnection of an IED [after N questions without answer, an IED becomes

Disconnected]

• Maximum time to wait for a response

• Minimum time between two frames on the network

• Sending functional requests to IEDs

Optimisation of polling 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 has important data to transmit [DI], it may be questioned successively
several times

• The maximum time to wait an answer may be configurable

The polling sequencing may be only stopped in the two following cases:

• Time synchronisation
Synchronisation is done periodically by sending a broadcast frame. After the
synchronisation frame has been sent, the polling starts again.

• Remote control to transmit to a slave

Control is a priority request. So, when a control must be sent to an IED, the polling is
stopped, the control is sent and the polling starts again.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 57/92

6.2.2.4 Monitoring of an IED

Each IED is managed according to the following graph:

NOT_
INITIALISED
1
DISCON-
2
NECTED
2
1

CONNECTED
NOT_SYNCHRONISED

12
3 4

IN_SERVICE
5 OUT_OF_
GI
SERVICE
6 7

NORMAL
10 8

11 9 DISTUR-
TUNNELING BANCE

C0109ENa

Description of the possible states of an IED:

• NOT_INITIALISED: That’s the initial state of an IED. The MiCOM C264 polls the IED
every cycle in order to connect it.
If the IED responds, it becomes CONNECTED 2 .
If after some attempts the IED doesn’t respond, it becomes DISCONNECTED 1 .

• DISCONNECTED: The IED is disconnected. The MiCOM C264 polls the IED time to
time in order to connect it.
If the IED responds, it becomes CONNECTED 2 .

• CONNECTED: The IED is connected. This state includes several states. When an IED
becomes Connected, it goes to the NOT_SYNCHRONISED state.

• NOT_SYNCHRONISED: The IED has just became Connected. It must be

synchronised. Once it is synchronised, according to the information given by the IED,
it becomes IN_SERVICE 3 or OUT_OF_SERVICE 4 . (This information isn’t
available for some protocols. In this case, the IED becomes IN_SERVICE by default).

• OUT_OF_SERVICE: The IED is connected and says it is Out of service. The MiCOM
C264 polls the IED time to time waiting for the IED to become IN_SERVICE 5 .

• IN_SERVICE: The IED is connected and it says it is In Service. This state includes
several states. When an IED becomes In Service, it goes to the GI state.

• GI: The IED is In Service and a General Interrogation is going on.

For each information received during the GI, the information becomes available and its
state is transmitted to the application [see below for more information on GI
treatment].
At the end of the GI, the IED goes in the NORMAL state 6 .
C264/EN CT/B30 Communications

Page 58/92 MiCOM C264/C264C

• NORMAL: The IED is In Service and the monitoring of DI, AO and DO are performed.
If a disturbance record becomes present and the MiCOM C264 have enough places to
store the file, the IED goes in the DISTURBANCE state 8 .
If a request to open a tunnel for the IED arrives, it is accepted and the IED goes in the
TUNNELING state 10 .
Time to Time, a GI may be done. In this case the IED goes in the GI state 7 .

• DISTURBANCE: The IED is In Service and a disturbance record is being uploaded.

When the uploading of the disturbance file is finished, the IED goes back in the
NORMAL state 9 .

• TUNNELING: Tunnelling communication is going on.

When the Tunnelling communication is finished, the IED goes back in the NORMAL
state 9 .
That shows that GI, Disturbance uploading and tunnelling are mutually exclusive. That is
done for 2 reasons:

• To limit the overload of the network

• To suppress interaction between Tunnelling access and MiCOM C264 access.

Description of the transitions between states:

• 0 : Initialisation of the transmission.

• 1 : The IED becomes DISCONNECTED.

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

• 2 : The IED becomes CONNECTED.

A synchronisation frame is sent to it and after, the status of the IED is red.

• 3 : The status of the IED is indicates the IED is In Service.

A General Interrogation is activated.

• 4 : The status of the IED is indicates the IED is Out Of Service.

• 5 : see 3

• 6 : The general Interrogation is finished.

• 7 : A general Interrogation is activated [cyclical GI].

• 8 : A disturbance file is available in the IED and there are enough places to store it in
the MiCOM C264.
A disturbance uploading is activated.

• 9 : End of disturbance file upload.

• 10 : A request to open a communication channel throw tunnelling is received.

• 11 : End of tunnelled communication.

• 12 : Request to send a control command to the IED.

The polling is interrupted and the command is sent as soon as possible.
Initialisation procedure
Initially, all data normally received from an IED is marked as unknown. When an IED is first
connected, a general interrogation request is sent. A table is updated with data received in
response to the general interrogation. When the general interrogation is finished, the content
of the table is sent to the processing functions: binary inputs processing and measurement
treatment. Messages received subsequently are checked against the content of the table
and a change of state message is sent when there is a difference.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 59/92

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:

• For each IED, there is an information in the configuration indicating if automatic upload
of Disturbance File has to be done. This indication may be overwritten by a command
from the application.

• When the MiCOM C264 detects that an IED has a Disturbance File ready to be
uploaded and that automatic upload is enabled, it uploads and stores it. When the
upload is finished, an indication is sent to the Upper transmission management to
inform it that a Disturbance file is ready.

• When there isn’t enough places to store a Disturbance File, the oldest file is deleted.

• The upper transmission management can only get Disturbance files stored in the
MiCOM C264. Once the upper transmission management has treated a file it is
deleted.
6.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.
6.2.3.1 Digital inputs
Digital inputs can be received as states or as changes of state. The choice between state
and change of state depends on the IED and on the protocol. This is known by configuration.
Even if digital inputs are received as change of state, it is still possible to request data as
states for general interrogations.
The conversion from digital input to binary input is performed by the binary input processing
function. A digital input can be associated with a single point or a double point.
C264/EN CT/B30 Communications

Page 60/92 MiCOM C264/C264C

6.2.3.2 Measurements
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.
6.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, …).
6.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.
6.2.4.1 Controls
Controls are priority message. The polling sequence must be interrupted in order to send the
control as soon as possible.
Not all IEDs send control acknowledgement. If they do not, an acknowledgement is
simulated and sent to the handling of control sequences function.
When an IED is disconnected [or out of service] a negative acknowledgement is sent.
If the command is a “select before operate” command, the application must send two
commands to the transmission software: the first one for the selection and the second for the
execution.
If the command is a double command, the application send one order, and depending on the
protocol, two cases have to be distinguished:

• The Double command is referenced only once in the IED Mapping. In this case, if an
OPEN (respectively CLOSE) command is received from the application, the master
send an OFF (respectively ON) order to the IED at the corresponding address.

• The double command is referenced by two addresses in the IED Mapping: one refers
to the Open Contact and the other to the Close Contact. In this case, if an OPEN
(respectively CLOSE) command is received from the application, the master sends an
ON order to the IED, at the address corresponding to the Open Contact (respectively
Close Contact).
6.2.4.2 Setpoints
SP controls are priority message. The polling sequence must be interrupted in order to send
the SP control as soon as possible.
Not all IEDs send SP control acknowledgement. If they do not, an acknowledgement is
simulated and sent to the handling of SP control sequences function.
When an IED is disconnected [or out of service] a negative acknowledgement is sent.
If the SP commands are always "direct execute" command (no “select before operate”).
For an IED, only one SP command is possible at a time.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 61/92

6.2.5 Tunnelling
The serial tunnelling enable to connect a lap top computer – which run an IED setting
software – to a serial (RS232) line of the PACiS computer in order to communicate with an
IED connected to a legacy bus of the PACiS computer.

C264
Lap Top IED
Computer

RS232 link Legacy bus

dedicated to (Modbus, T103)
serial tunneling
C0149ENa

All serial RS232 lines of the computer – including the port onto the front panel – can be used
for serial tunnelling.
The choice of the serial line to be used for serial tunnelling is done by the computer
configuration.
The cable dedicated to tunnelling must be disconnected from the front panel when
tunnelling is not used.
6.2.5.1 Interface through the tunnelling serial line
The tunnelling serial line gives access to a user dialog.
This dialog enables an user to give commands to the Tunnelling RS232 software.

Commands are ASCII string terminated by ‘↵’ (code ASCII 13H) and are case sensitive.

A command is executed at the reception of the ‘↵’ character. An ASCII message is sent in
response, and a prompt message may be sent in order to indicate the computer is ready to
treat a new command.
If a command is unknown, an error message “Unknown command !” is sent.
List of the available commands :

• TunRSLines↵: List the legacy lines for which tunnelling is enabled.

Each line of the list corresponds to a legacy line for which tunnelling is enabled and have the
following format :
Line <line Number> : <Protocol>
If there is not any legacy line available for Tunnelling, the response is “No line available for
serial tunnelling.”

• TunRSIed nl↵: List the IED of a legacy line and their state [ln = line number].
The first line of the response gives information on the line :
Line <line Number> : <Protocol>
Each following line of the response corresponds to an IED and have the following format :
IED <Address> : <State>
Where <State> can be “available” or “not available”
If the line isn’t available for Tunnelling, the response is “The line nl is not available for serial
tunnelling.”
C264/EN CT/B30 Communications

Page 62/92 MiCOM C264/C264C

• TunRSStart ln, ad↵: Start a serial tunnelling session with the specified legacy line
[ln = legacy line number; ad = IED address].
The response is either “Serial Tunnelling started” or an error message explaining why the
command can’t be executed.
If the response is “Serial Tunnelling started”, legacy frames are awaited on the serial
Tunnelling link.

• TunRSStop↵: Stop the current serial tunnelling session.

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

• Connect a LapTop to the computer with a RS232 serial cable

(On the computer, the cable is connected to the serial line dedicated to the tunnelling)

• Launch Hyperterminal on the LapTop

• Enter the serial tunnelling starting command [“TunRSStart”]

The computer answers “Serial Tunnelling started”.

• Quit Hyperterminal (be sure to close the connection)

• Launch an IED setting Software [e.g. : MiCOM S1] on the LapTop

• Execute settings actions with the setting Software (that implies exchange of legacy
frames between the setting software and the IED through the computer)

• Quit the setting Software

• Launch Hyperterminal on the LapTop

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

The computer answers “Serial Tunnelling stopped”.

• Quit Hyperterminal (be sure to close the connection)

6.2.5.4 End of a serial tunnelling session
As described above, a serial tunnelling session may be ended by the “TunRSStop”
command.
If the user forgets to end the tunnelling session with the “TunRSStop” command, the session
will be automatically ended after expiry of a deadline - of about 2 minutes - without
exchange.
6.2.5.5 Fault case behaviours

• If the questioned IED does not answer, no frame of answer is returned to the setting
Software.

• If the setting software sends a new question frame [or repeats the last frame] whereas
the computer is still awaiting the answer from the IED, this new frame is ignored.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 63/92

6.2.5.6 Serial tunnelling through a modem

Modem Lap Top

C264
Modem IED
Computer

Specialised
or RTC line RS232 link
Legacy bus
dedicated to serial
(Modbus,
tunneling
T103)

C0150ENa

If modems are well configured, this operating mode is transparent for the computer and no
specific management is needed in the software.
6.2.5.7 Tunnelling limits and Performances
The legacy protocols supported [protocols for which serial tunnelling is available] are the
following :

• MODBUS

• T103
The line to be used for serial tunnelling can be set through computer configuration.
If The serial tunnelling line is “frontal RS232”, it’s automatically configured :
19200Bd, 8 bits data, no parity, 1 stop bit.
For the other ports (COM1 to COM4), it follows the configuration parameters.
Only RS232 mode is supported.
6.2.6 Limits and Performances

• The number of serial links available limits the number of legacy network that can be
managed simultaneously by a MiCOM C264.

• The maximum number of IED that can be managed for a network is 16.

• Performance depends on the protocol used and on the number of IEDs connected to
each Network.
C264/EN CT/B30 Communications

Page 64/92 MiCOM C264/C264C

6.3 MODBUS communication

6.3.1 Finality
MODBUS is a legacy bus master/slave protocol that is used by many devices such as
relays, MiCOM C264s or monitoring devices. The aim of this chapter is not to describe the
protocol itself and its mechanisms (other documents and norms are there for that) but to give
the specificity of the functions that will be implemented in the MiCOM C264. These are the
MODBUS function numbers that will be used, the way in which each type of data will be
internally or externally updated, the general mechanisms used for the time synchronisation
and the configuration needs.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master Modbus” in the MiCOM C264.
6.3.2 Interface to IEDs
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

6.3.3 Behaviour
6.3.3.1 Polling
During a polling procedure, each slave is polled one after the other. This means that the
master waits for the answer to a request sent to a device before sending a new request to
the same or an other device.
There will be 2 types of polling:

• the polling performed by the application for the measurements and the digital inputs

• a low level polling used for detecting if a device is present or not.

If an IED does not correctly answer after a defined timeout (configured), the request is resent
by the MiCOM C264. If the IED do not correctly answer after a defined number of retries
(configured) it is considered as disconnected. Then it is polled regularly (not too often) to
eventually be reconnected to the network.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 65/92

6.3.4 Data received from IEDs

6.3.4.1 Measurements
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.
6.3.4.2 Digital Inputs
The processing applied to the DIs depends on the IEDs. Each change of a DI is dated, either
in the MiCOM C264 or in the IED, depending on the IED type.
We define a block of DIs as a set of DIs that have been configured at consecutive
addresses. As a result, to improve the polling performance, all the DIs of a block will be read
thanks to just one exchange having regard to the number of DIs to be read.
Processing for generic IEDs
By default, the DI blocks are regularly polled by the application. Then the application
compares the state of each DI with the previous state. So the MiCOM C264 itself performs
the time stamping of a change of state.
Processing for Areva IEDs
The status byte-taking place in an Areva IED contains the information indicating that events
(DI changes) are present. As a result, the status byte is regularly polled by the link layer
through a low level polling and compared with the previous one. If a change is detected, the
master reads the event queue inside the IED, checks which data have changed, checks if
they have been configured and then reads the information itself. Notice that in this case, the
DI changes are dated in the IED and the MiCOM C264 downloads their date and time.
6.3.4.3 Disturbance files
Disturbance files are only treated for devices that conform to the MODBUS Areva rules and,
if needed for other devices (specific developments).
6.3.5 Data sent to IEDs
6.3.5.1 Connection check
Generic IEDs
Each device on the network is regularly polled with a specific frame to know if it is connected
or not. This frame could be the status byte polling frame if it exists, the measurement polling
frame if it exists, the BI polling frame if it exists, the mirror frame if it has been implemented
in the device or a user defined frame. This choice is performed through the configuration
options.
Areva IEDs
The “Read status byte” frame is used for checking the connection of the device.
C264/EN CT/B30 Communications

Page 66/92 MiCOM C264/C264C

6.3.5.2 Time synchronisation

Preliminary remark: All the devices connected to a given network must have
the same synchronisation procedure (address and time
and date format) because the synchronisation is
performed through a broadcast frame.
There will be 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.
6.3.5.3 Commands
Commands are sent to the IED and have the highest priority level. They come from the
application and have to be transmitted to the destination device as fast as possible. An
acknowledge (which is the answer from the IED to the MiCOM C264 in the MODBUS
exchange) is waited by the application. If the acknowledge is not received after a defined
timeout, you consider that the command has not been taken into account.
6.3.6 Error management
The MODBUS protocol handles a mechanism of exception answer. This means that an IED
could answer with an exception frame if it does not understand the request. There are
different exception codes:

Exception
Meaning Processing performed by the master
code
01 Illegal function Send a “Configuration error” message to the
application and continue
02 Illegal data address Send a “Configuration error” message to the
application and continue
03 Illegal data value Send a “Configuration error” message to the
application and continue
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

6.3.7 Limits and Performances

The performances depend a lot on the number of devices connected on the network. It is
advised to connect devices that have similar performance level on a given network, i.e. the
same reply time for instance.
Each device on a MODBUS network must have the same synchronisation mode.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 67/92

6.4 DNP 3.0 Communication

6.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.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master DNP3” in the MiCOM C264.
Here are described:

• Specific behaviours attached to the protocol DNP3

• Restriction and enhancement

• Part of the DNP3 protocol used and not used

6.4.2 Interface to IEDs
6.4.2.1 Input

Object Variation Data GI Polling Function

01 0 Static BI ♦ [1] READ
02 0 BI Event ♦ [1] READ
20 0 Static Counter ♦ [1] READ
22 0 Counter Event ♦ [1] READ
30 0 Static Measurement ♦ [1] READ
32 0 Measurement Event ♦ [1] READ
60 01 Class 0 ♦ [1] READ
60 02, 03, 04 Class 1,2,3 ♦ [1] READ

NOTE: BI, Measurement and Counter are polled with the variation 0. That
means that all variations are required.
All other DNP3 objects are not treated.
6.4.2.2 Output

Object Variation Data Function Note

12 01 Command: Control [3] SELECT Treated
Relay Output Block
[4] OPERATE Treated
[5] DIRECT OPERATE Treated
[4] OPERATE Treated
[5] DIRECT OPERATE Treated
50 01 Time and Date [2] WRITE Treated

The DNP3 Master manages both direct control Command and Select before Operate for
digital control only.
When operate command is received from application, the Master checks in database to
know if the command is:
1. An execute command, which belongs to a SBO Control: OPERATE function is used in
this case.
2. A direct control: DIRECT OPERATE function is used is this case
C264/EN CT/B30 Communications

Page 68/92 MiCOM C264/C264C

6.4.3 Behaviour

• Synchronisation:

− The “Master DNP3” is always synchronised by the MiCOM C264. No calculation of

the transmission delay is performed.

− The DNP3 object used to synchronise IEDs is “Write Date and Time Request
(Object 50, Variation 01).

− Synchronisation is performed first at connection of an IED.

− Then, synchronisation is sent cyclically to all the IEDs.

• Initialisation:

− To connect an IED, a “Reset CU” (function 0) frame is sent to the IED.

− When the response is OK, the Master DNP3 send a message to the application to
tell that connection step is passed.

− Next step is General Interrogation

• General Interrogation:

− When the IED is connected, the MiCOM C264 ask for static data state and value with
a sequence of:

− Read BI,

− Read Measurement,

− Read TPI,

− Read Counter

− This Sequence is the General Interrogation. Next step is Polling

• Polling:

− The polling cycle depends on the configuration:

− Poll BI, Poll Measurement, Poll counter, Poll BI ….

− Poll C1, Poll C2, Poll C3, Poll C1 …

− The polling cycle must be interrupted at minimum in the two following case:

− Clock Synchronisation

− Remote control

• Event acquisition:

− Event occurs spontaneously. The slave device waits for being polled by the master.

• IED monitoring:

− A General Interrogation may be done after connection of an IED

Communications C264/EN CT/B30

MiCOM C264/C264C Page 69/92

6.4.4 Data received from IEDs

• 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
6.4.5 Data sent to IEDs

• 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
C264/EN CT/B30 Communications

Page 70/92 MiCOM C264/C264C

6.5 Master DNP3.0 Profile

DNP V3.00 Device Profile

Vendor Name: AREVA T&D

Device Name: PACIS Computer
Highest DNP Level Supported : Device Function :
For Requests Level 3 # Master " Slave
For Responses Level 3
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels
supported :
_______________________________________________________________________________
_______________________________________________________________________________
Maximum Data Link Frame Size (octets) : Maximum Application Fragment Size (octets):
Transmitted: 292 Transmitted 2048
(configurable: 15 to 2048 octects)
Received: (must be 292) Received 2048
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
None # None
Fixed at _________________________ Configurable, range ____ to _____
# Configurable, range 1 to 10 (Fixed is not permitted)
Requires Data Link Layer Confirmation:
Never
# Always
Sometimes If ’Sometimes’, when?
__________________________________________
Configurable If ’Configurable’, how?
User option to set Data Link Confirmation to:
• Always – device will always request Data Link Confirmations.
• Multi-packet only – the device will request Data Link Confirmations when
sending multi-packet responses.
• Never – the device will never request Data Link Confirmations.
Requires Application Layer Confirmation:
# Never
Always (not recommended)
When reporting Event Data (Slave devices only)
When sending multi-fragment responses (Slave devices only)
Sometimes _________ If 'Sometimes', when?

Configurable If 'Configurable', how? ______________________________________________

Communications C264/EN CT/B30

MiCOM C264/C264C Page 71/92

DNP V3.00 Device Profile

Timeouts while waiting for:

Data Link Confirm None Fixed at ___ Variable # Configurable
Complete Appl. Fragment None Fixed at ___ # Variable Configurable
Application Confirm # None Fixed at ___ Variable Configurable
Complete Appl. Response None Fixed at ___ # Variable Configurable

Others
_______________________________________________________________________________
Attach explanation if 'Variable' or 'Configurable' was checked for any timeout
Sends/Executes Control Operations:
WRITE Binary Outputs # Never Always Sometimes Configurable
SELECT/OPERATE Never Always Sometimes # Configurable
DIRECT OPERATE Never Always Sometimes # Configurable
DIRECT OPERATE - NO ACK # Never Always Sometimes Configurable

Count > 1 # Never Always Sometimes Configurable

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

Queue # Never Always Sometimes Configurable

Clear Queue # Never Always Sometimes Configurable
• Select timeout : configurable

FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICES ONLY:

Reports Binary Input Change Events when no Reports time-tagged Binary Input Change
Events
Specific variation requested: when no specific variation requested:

Never Never
Only time-tagged Binary Input Change With Time
Only non-time-tagged Binary Input Change With Relative Time
Configurable to send both, one or the Configurable (attach explanation)
other (explanation below)

User option to have all Binary Input

Change Events returned as either:
• time-tagged OR
• non-time-tagged
C264/EN CT/B30 Communications

Page 72/92 MiCOM C264/C264C

DNP V3.00 Device Profile

Sends Unsolicited Responses: Sends Static Data in Unsolicited Responses:

Never Never
Configurable (attach explanation) When Device Restarts
Only certain objects When Status Flags Change
Sometimes (attach explanation)
ENABLE/DISABLE UNSOLICITED No other options are permitted.
Function codes supported
Default Counter Object/Variation: Counters Roll Over at:
No Counters Reported # No Counters Reported
# Configurable (explanation below) Configurable (explanation below)
Default Object _____20_______ 16 Bits
Default Variation _____02_______ 32 Bits
Point-by-point list attached Other Value _____________
Point-by-point list attached
User option to return all static counters in User option to select roll over:
one of the following variations: • 32 bit counters roll over at 2^32.
• 32-Bit Binary Counter • 16 bit counters roll over at 2^16
• 32-Bit Binary Counter Without Flag
• 16-Bit Binary Counter
• 16-Bit Binary Counter Without Flag
Sends Multi-Fragment Responses: # Yes No
Communications C264/EN CT/B30

MiCOM C264/C264C Page 73/92

7. DNP.3 LEVEL 3 IMPLEMENTATION TABLE

Underlined information in grey are not implemented

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes
(dec) (hex)
(dec) (hex)
1 0 Binary Input – All Variations 1, 22 00,01,06
1 1 Binary Input 1 00,01,06 129,130 00,01
1 2 Binary Input with Status 1 00,01,06 129,130 00,01
2 0 Binary Input Change - All Variations 1 06,07,08
2 1 Binary Input Change without Time 1 06,07,08 129,130 17,28
2 2 Binary Input Change with Time 1 06,07,08 129,130 17,28
2 3 Binary Input Change with Relative Time 1 06,07,08 129,130 17,28
10 0 Binary Output - All Variations 1 00,01,06
10 1 Binary Output
10 2 Binary Output Status 1 00,01,06 129,130 00,01
12 0 Control Block - All Variations (1)
12 1 Control Relay Output Block (1) 3,4,5,6 17,28 129 Request echo
12 2 Pattern Control Block 5,6 17,28 129 Request echo
12 3 Pattern Mask 5,6 00,01 129 Request echo
20 0 Binary Counter - All Variations 1,7,8,9,10,2 00,01,06
2
20 1 32-Bit Binary Counter 1 00,01,06 129,130 00,01
20 2 16-Bit Binary Counter 1 00,01,06 129,130 00,01
20 3 32-Bit Delta Counter 1 00,01,06 129,130 00,01
20 4 16-Bit Delta Counter 1 00,01,06 129,130 00,01
20 5 32-Bit Binary Counter without Flag 1 00,01,06 129,130 00,01
20 6 16-Bit Binary Counter without Flag 1 00,01,06 129,130 00,01
20 7 32-Bit Delta Counter without Flag 1 00,01,06 129,130 00,01
20 8 16-Bit Delta Counter without Flag 1 00,01,06 129,130 00,01

1. Commands must be selected/executed on one point

C264/EN CT/B30 Communications

Page 74/92 MiCOM C264/C264C

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes
(dec) (hex)
(dec) (hex)
21 0 Frozen Counter - All Variations 1 00,01,06
21 1 32-Bit Frozen Counter 1 00,01,06 129,130 00,01
21 2 16-Bit Frozen Counter 1 00,01,06 129,130 00,01
21 3 32-Bit Frozen Delta Counter 1 00,01,06 129,130 00,01
21 4 16-Bit Frozen Delta Counter 1 00,01,06 129,130 00,01
21 5 32-Bit Frozen Counter with Time of 1 00,01,06 129,130 00,01
Freeze
21 6 16-Bit Frozen Counter with Time of 1 00,01,06 129,130 00,01
Freeze
21 7 32-Bit Frozen Delta Counter with Time of
Freeze
21 8 16-Bit Frozen Delta Counter with Time of
Freeze
21 9 32-Bit Frozen Counter without Flag 1 00,01,06 129,130 00,01
21 10 16-Bit Frozen Counter without Flag 1 00,01,06 129,130 00,01
21 11 32-Bit Frozen Delta Counter without Flag
21 12 16-Bit Frozen Delta Counter without Flag
22 0 Counter Change Event - All Variations 1 06,07,08
22 1 32-Bit Counter Change Event without 1 06,07,08 129,130 17,18
Time
22 2 16-Bit Counter Change Event without 1 06,07,08 129,130 17,18
Time
22 3 32-Bit Delta Counter Change Event 1 06,07,08 129,130 17,18
without Time
22 4 16-Bit Delta Counter Change Event 1 06,07,08 129,130 17,18
without Time
22 5 32-Bit Counter Change Event with Time 1 06,07,08 129,130 17,18
22 6 16-Bit Counter Change Event with Time 1 06,07,08 129,130 17,18
22 7 32-Bit Delta Counter Change Event with
Time
22 8 16-Bit Delta Counter Change Event with
Time
Remarks:
Frozen counters (type21) are uploaded during general interrogation, but never polled after this.
Communications C264/EN CT/B30

MiCOM C264/C264C Page 75/92

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes
(dec) (hex)
(dec) (hex)
23 0 Frozen Counter Event - All Variations 1 06,07,08
23 1 32-Bit Frozen Counter Event without Time 1 06,07,08 129,130 17,18
23 2 16-Bit Frozen Counter Event without Time 1 06,07,08 129,130 17,18
23 3 32-Bit Frozen Delta Counter Event 1 06,07,08 129,130 17,18
without Time
23 4 16-Bit Frozen Delta Counter Event 1 06,07,08 129,130 17,18
without Time
23 5 32-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17,18
23 6 16-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17,18
23 7 32-Bit Frozen Delta Counter Event with
Time
23 8 16-Bit Frozen Delta Counter Event with
Time
30 0 Analogue Input - All Variations 1 00,01,06
30 1 32-Bit Analogue Input 1 00,01,06 129,130 00,01
30 2 16-Bit Analogue Input 1 00,01,06 129,130 00,01
30 3 32-Bit Analogue Input without Flag 1 00,01,06 129,130 00,01
30 4 16-Bit Analogue Input without Flag 1 00,01,06 129,130 00,01
31 0 Frozen Analogue Input - All Variations
31 1 32-Bit Frozen Analogue Input
31 2 16-Bit Frozen Analogue Input
31 3 32-Bit Frozen Analogue Input with Time
of Freeze
31 4 16-Bit Frozen Analogue Input with Time
of Freeze
31 5 32-Bit Frozen Analogue Input without
Flag
31 6 16-Bit Frozen Analogue Input without
Flag
32 0 Analogue Change Event - All Variations 1 06,07,08
32 1 32-Bit Analogue Change Event without 1 06,07,08 129,130 17,18
Time
32 2 16-Bit Analogue Change Event without 1 06,07,08 129,130 17,18
Time
32 3 32-Bit Analogue Change Event with Time 1 06,07,08 129,130 17,18
32 4 16-Bit Analogue Change Event with Time 1 06,07,08 129,130 17,18
33 0 0 Frozen Analogue Event - All Variations
33 1 32-Bit Frozen Analogue Event without
Time
33 2 16-Bit Frozen Analogue Event without
Time
33 3 32-Bit Frozen Analogue Event with Time
33 4 16-Bit Frozen Analogue Event with Time
40 0 Analogue Output Status - All Variations 1 00,01,06
40 1 32-Bit Analogue Output Status 1 00,01,06 129,130 00,01
40 2 16-Bit Analogue Output Status 1 00,01,06 129,130 00,01
41 0 Analogue Output Block - All Variations 3,4,5,6 17,28 129 Request echo
41 1 32-Bit Analogue Output Block 5,6 17,28 129 Request echo
C264/EN CT/B30 Communications

Page 76/92 MiCOM C264/C264C

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes
(dec) (hex)
(dec) (hex)
41 2 16-Bit Analogue Output Block 5,6 17,28 129 Request echo
50 0 Time and Date - All Variations
50 1 Time and Date 2 07 (quantity=1)
50 2 Time and Date with Interval
51 0 Time and Date CTO - All Variations
51 1 Time and Date CTO 129,130 07
(quantity=1)
51 2 Unsynchronized Time and Date CTO 129,130 07
(quantity=1)
52 0 Time Delay - All Variations
52 1 Time Delay Coarse 129,130 07
(quantity=1)
52 2 Time Delay Fine 129,130 07
(quantity=1)
60 0
60 1 Class 0 Data 1 06,07,08
60 2 Class 1 Data 1 06,07,08
20,21,22 06
60 3 Class 2 Data 1 06,07,08
20,21,22 06
60 4 Class 3 Data 1 06,07,08
20,21,22 06

70 1 File Identifier
80 1 Internal Indications 2 00 (index=7 ou
index=4)
1 00,01
81 1 Storage Object
82 1 Device Profile
83 1 Private Registration Object
83 2 Private Registration Object Descriptor
90 1 Application Identifier
100 1 Short Floating Point
100 2 Long Floating Point
100 3 Extended Floating Point
101 1 Small Packed Binary-Coded Decimal
101 2 Medium Packed Binary-Coded Decimal
101 3 Large Packed Binary-Coded Decimal
No Object (Cold Restart)

No Object (Warm Restart)

No Object (Delay Measurement

Communications C264/EN CT/B30

MiCOM C264/C264C Page 77/92

7.1 IEC 60870-5-103 Communication

7.1.1 Finality
The purpose of this chapter is not to describe the T103 but to specify the use of the T103
protocol on a legacy bus of the MiCOM C264.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master T103” in the MiCOM C264.
Here are described:

• Specific behaviours attached to the protocol T103

• Restrictions and enhancements

• Part of the T103 protocol used and not used

• Specific behaviours attached to implementation of Private Range of T103

7.1.2 Interface to IEDs
7.1.2.1 Input

ASDU Data Note

1 Dated Digital input (absolute dating) Treated
Control acknowledgement
2 Dated Digital input (relative dating) Treated
3 Measurement Treated
4 Measurement : Default position Treated
5 Identification Not treated
6 Time synchronisation acknowledgement Treated
8 End of GI Treated
9 Measurement Treated
10 General Data Not treated
11 General Identification Not treated
17 Measurement Reg D only
23 … 31 Disturbance file management Treated
45 Ack of Single Command Px3x only
46 Ack of Double Command Px3x only
49 Analog protection signal Px3x only
Only adress 0 which is DVICE: Device type
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
71 BitString 32 Bit without time tag – Px3x only
couple FUN/TYP computed :
F8h / 70h : State of the IED
F8h / 74h : Request Station Interlock
72 BitString 32 Bit with time tag – see ASDU Px3x only
71
73 Measurement, Normalised value Px3x only
77 Measurement Px2x only
C264/EN CT/B30 Communications

Page 78/92 MiCOM C264/C264C

7.1.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
140 Read protection parameter Px3x only
Only adress 0 which is DVICE: Device
type
144 Setpoint Reg D only

7.1.3 Behaviour
7.1.3.1 Synchronisation
The “Master T103” link is always synchronised by the MiCOM C264. No calculation of the
transmission delay is performed.
7.1.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.
7.1.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
7.1.3.4 Tunnelling mode
During tunnelling mode, only polling C2 may be done by the MiCOM C264 [Normally, if
“priority information” is present, the remote Master may send a “polling C1 frame”].
The MiCOM C264 must spy the tunnelling exchange in order not to loose information [DI and
AI change]
For security raison, at the end of a tunnelling session, a GI is done
Communications C264/EN CT/B30

MiCOM C264/C264C Page 79/92

7.1.3.5 Station Interlocking

This functionality is only available on P139 in private T103 range (Alstom D protocol variant)
After GI, and only if IED is Px3x, we send a read on Px3x parameter adress 0 which
corresponds to Device Type. If Px3x responds with analog parameter set to 139, we activate
Station Interlocking Management.
Case of local control (front panel of the P139) with Station interlock :
As soon as a user will try to control a switchgear by the front panel, the P139 will send an
ASDU 72 with FUN/TYP = F8h/74h in order to request to PACiS system the station interlock
conditions. PACiS system should check if the command is allowed (specific treatment done
by CONDUITE of the computer) and respond to the P139.
Case of remote control (from PACiS system) with Station interlock :
As soon as a user will try to control a device managed by P139 by PACiS system through
T103 communication, the P139 will send an ASDU 72 with FUN/TYP = F8h/74h in order to
request to PACiS system the station interlock conditions. PACiS system should respond to
the P139 with a positive acknowledgement (checks have already been done before)
If station Interlock is de-activated on P139, the control of a switchgear on P139 by PACiS
system through T103 communication is done by an EXECUTE ORDER (selection will be
refused by P139)
7.1.3.6 REG D
The Reg D equipment manages 2 ASDU (144 and 17), for control of setpoints (144) and
setpoint value feedback (17), which is treated as a measurement in the computer. Setpoints
managed by the Reg D are "Direct Execute" only, there is no SBO management. The Reg D
setpoint command sequence is like the command sequence (ASDU20). The computer sends
the setpoint (ASDU 144), with the setpoint value, the Reg D sends its acknowledge
(ASDU1), if the acknowledge is OK, the Reg D sends the setpoint value feedback
(ASDU17).
7.1.4 Data received from IEDs
7.1.4.1 Digital inputs
An ASDU number [(1,2) in public Range],[(66,67,68,69) in private Range]
A DI is identified by a couple (Function Type, Information Number).
Digital inputs are received as changes of state.
Special DI may be managed:

− DI 20: Lock of the communication. A GI must be done when the communication is

unlocked

− DI 23 to 26: Change of configuration number

− DI which are not transmitted during a GI. For these DI, the IED signals only
change of state from OFF to ON. The MiCOM C264 must generate by itself the
change from ON to OFF.
7.1.4.2 Measurements
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

C264/EN CT/B30 Communications

Page 80/92 MiCOM C264/C264C

7.1.4.3 Bitstring 32-bits :

The state of the IED is identify by the ASDU 71 or 72 with couple FUN / TYP = F8h / 70h.
This ASDU describes the status of the IED (Station Interlocking active or not …)
A request to check station interlocking is identify by the ASDU 71 or 72 with couple FUN /
TYP = F8h / 74h. In this request, the couple FUN/TYP of the command to spend is defined.
7.1.4.4 Analog protection signal (ASDU 49) :
Only for Px3x, an analogue protection signal is received after GI
Only address 0 is managed. It is used to recognise P139 in order to activate station
interlocking management.
7.1.5 Data sent to IEDs
7.1.5.1 Controls
An ASDU Number and a couple (Function Type, Information Number) identify a control.
The acknowledgement of a control is to be waited as:

• A DI with the same (Function Type, Information Number) as the control and with a
‘Cause Of Transmission’ equals to ‘positive return’ or ‘negative return’ in public range

• A ASDU 45 or 46 with a ‘Cause Of Transmission’ equals to ‘end of activation OK’ or

‘en of activation KO’, or ‘deactivation OK’, or ‘deactivation KO’ in private range
7.1.5.2 Setpoints Controls :
A setpoint control is identified by an ASDU Number plus a couple (Function Type,
Information Number). In the case of the Reg D equipment the ASDU is 144.
The acknowledgement of a setpoint control is to be waited as :

• A DI (ASDU 1) with the same (Function Type, Information Number) as the control and
with a ‘Cause Of Transmission’ equals to ‘positive return’ or ‘negative return’ in public
range.

• An ASDU 17 with a ‘Cause Of Transmission’ equals to ‘Local Operation’ in public

range. The ASDU is a measurement which contains the setpoint feedback value.
7.1.5.3 Read protection parameter :
Only for Px3x, a read of protection parameter (ASDU 140) address 0 (Device Type) is sent
to IED
The IED responds with ASDU 49 in which Device Type is set (139 if IED is a P139 for
example).
Communications C264/EN CT/B30

MiCOM C264/C264C Page 81/92

7.2 IEC 60870-5-101 Communication

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

$ Function or ASDU is not used

⌧ Function or ASDU is used as standardised (default)

R Function or ASDU is used in reverse mode

B Function or ASDU is used in standard and reverse mode

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

$ Controlling station definition (Master)

⌧ Controlled station definition (Slave)

7.2.4 Network configuration

(network-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ Point-to-point ⌧ Multipoint-party line

⌧ Multiple point-to-point ⌧ Multipoint-star

C264/EN CT/B30 Communications

Page 82/92 MiCOM C264/C264C

7.2.5 Physical layer

(network-specific parameter, all interfaces and data rates that are used are to be marked ‘X’)
Transmission speed (control direction)

Unbalanced interchange
CIRCUIT V24/V28 Balanced interchange
Circuit X24/X27
Standard Recommended if > 1200 bits/s

⌧ 100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s " 56000 bits/s

⌧ 200 bits/s ⌧ 4800 bits/s ⌧ 4800 bits/s " 64000 bits/s

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

⌧ 600 bits/s ⌧ 19200 bits/s ⌧ 19200 bits/s

⌧ 1200 bits/s ⌧ 38400 bits/s

Transmission speed (monitor direction)

Unbalanced interchange
CIRCUIT V24/V28 Balanced interchange
Circuit X24/X27
Standard Recommended if > 1200 bits/s

⌧ 100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s " 56000 bits/s

⌧ 200 bits/s ⌧ 4800 bits/s ⌧ 4800 bits/s " 64000 bits/s

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

⌧ 600 bits/s ⌧ 19200 bits/s ⌧ 19200 bits/s

⌧ 1200 bits/s ⌧ 38400 bits/s

7.2.6 Link layer

(network-specific parameter, all options that are used are to be marked ‘X’. Specify the
maximum frame length).
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively
in this companion standard.
Link transmission procedure Address field of the link

⌧ Balanced transmission " Not present (balanced transmission only)

⌧ Unbalanced transmission ⌧ One octet

⌧ Two octets

⌧ Structured

⌧ Unstructured

Frame length (number of bytes)

255 Maximum length L in control direction

up to 255 Maximum length L in monitor direction – configurable

Communications C264/EN CT/B30

MiCOM C264/C264C Page 83/92

7.2.7 Application layer

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

⌧ One octet ⌧ Two octets

Information object address

(system-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ One octet ⌧ Structured

⌧ Two octets ⌧ Unstructured

⌧ Three octets

Cause of transmission
(system-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ One octet ⌧ Two octets (with originator address)

Set to zero in case of no originator address.
Selection of standard ASDUs
Process information in monitor direction
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <1> := Single-point information M_SP_NA_1

⌧ <2> := Single-point information with time tag M_SP_TA_1

⌧ <3> := Double-point information M_DP_NA_1

⌧ <4> := Double-point information with time tag M_DP_TA_1

⌧ <5> := Step-position information M_ST_NA_1

⌧ <6> := Step-position information with time tag M_ST_TA_1

$ <7> := BitString of 32 bit M_BO_NA_1

$ <8> := BitString of 32 bit with time tag M_BO_TA_1

⌧ <9> := Measured value, normalized value M_ME_NA_1

⌧ <10> := Measured value, normalized value with time tag M_ME_TA_1

⌧ <11> := Measured value, scaled value M_ME_NB_1

⌧ <12> := Measured value, scaled value with time tag M_ME_TB_1

⌧ <13> := Measured value, short floating point value M_ME_NC_1

⌧ <14> := Measured value, short floating point value with time tag M_ME_TC_1

⌧ <15> := Integrated totals M_IT_NA_1

C264/EN CT/B30 Communications

Page 84/92 MiCOM C264/C264C

⌧ <16> := Integrated totals with time tag M_IT_TA_1

$ <17> := Event of protection equipment with time tag M_EP_TA_1

$ <18> := Packed start events of protection equipment with time tag M_EP_TB_1

$ <19> := Packed output circuit transmission of protection equipment with time tag M_EP_TC_1

$ <20> := Packed single-point information with status change detection M_PS_NA_1

⌧ <21> := Measured value, normalized value without quality descriptor M_ME_ND_1

⌧ <30> := Single-point information with time tag CP56Time2a M_SP_TB_1

⌧ <31> := Double-point information with time tag CP56Time2a M_DP_TB_1

⌧ <32> := Step-position information with time tag CP56Time2a M_ST_TB_1

$ <33> := Bistring of 32 bits with with time tag CP56Time2a M_BO_TB_1

⌧ <34> := Measured value, normalized with time tag CP56Time2a M_ME_TD_1

⌧ <35> := Measured value, scaled with time tag CP56Time2a M_ME_TE_1

⌧ <36> := Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1

⌧ <37> := Integrated totals with time tag CP56Time2a M_IT_TB_1

$ <38> := Event of protection equipment with time tag CP56Time2a M_EP_TD_1

$ <39> := Packed start events of protection equipment with time tag CP56Time2a M_EP_TE_1

$ <40> := Packed output circuit information of protection equipment with time tag CP56Time2a M_EP_TF_1

Process information in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <45> := Single command C_SC_NA_1

⌧ <46> := Double command C_DC_NA_1

⌧ <47> := Regulating step command C_RC_NA_1

⌧ <48> := Set point command, normalized value C_SE_NA_1

⌧ <49> := Set point command, scaled value C_SE_NB_1

⌧ <50> := Set point command, short floating point value C_SE_NC_1

$ <51> := BitString of 32 bits C_BO_NA_1

System information in monitor direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <70> := End of initialisation M_EI_NA_1

Communications C264/EN CT/B30

MiCOM C264/C264C Page 85/92

System information in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <100> := Interrogation command C_IC_NA_1

⌧ <101> := Counter Interrogation Command C_CI_NA_1

$ <102> := Read command C_RD_NA_1

⌧ <103> := Clock synchronisation command C_CS_NA_1

⌧ <104> := Test command C_TS_NB_1

$ <105> := Reset process command C_RP_NC_1

$ <106> := Delay acquisition command C_CD_NA_1

Parameter in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ <110> := Parameter of measured value, normalized value P_ME_NA_1

$ <111> := Parameter of measured value, scaled value P_ME_NB_1

$ <112> := Parameter of measured value, short floating point value P_ME_NC_1

$ <113> := Parameter activation P_AC_NA_1

File transfer
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <120> := File ready F_FR_NA_1

⌧ <121> := Section ready F_SR_NA_1

⌧ <122> := Call directory, select file, call file, call section F_SC_NA_1

⌧ <123> := Last section, last segment F_LS_NA_1

⌧ <124> := Ack file, ack section F_AF_NA_1

⌧ <125> := Segment F_SG_NA_1

⌧ <126> := Directory F_DR_TA_1

Special use
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)
None
C264/EN CT/B30 Communications

Page 86/92 MiCOM C264/C264C

Type identifier and cause of transmission assignments

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

Type ID Cause of transmission

20 to 37 to
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45 46 47
36 41
<1> M_SP_NA_1 X X X X X
<2> M_SP_TA_1 X X X

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

MiCOM C264/C264C Page 87/92

Type ID Cause of transmission

20 to 37 to
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45 46 47
36 41
<47> C_RC_NA_1 X X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X X
<51> C_BO_NA_1
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X
<101> C_CI_NA_1 X X X
<102> C_RD_NA_1
<103> C_CS_NA_1 X X
<104> C_TS_NA_1 X X
<105> C_RP_NA_1
<106> C_CD_NA_1

<110> P_ME_NA_1
<111> P_ME_NB_1
<112> P_ME_NC_1
<113> P_AC_NA_1
<120> F_FR_NA_1 X
<121> F_SR_NA_1 X
<122> F_SC_NA_1 X
<123> F_LS_NA_1 X
<124> F_AF_NA_1 X
<125> F_SG_NA_1 X
<126> F_DR_TA_1 X X

7.2.8 Basic application functions

Station initialisation
(station-specific parameter, mark ‘X’ if function is used)

" Remote initialisation

Cyclic data transmission

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Cyclic data transmission

Read procedure
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ Read procedure

Spontaneous transmission
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Spontaneous transmission
C264/EN CT/B30 Communications

Page 88/92 MiCOM C264/C264C

Link state between Controlling and Controlled Station

⌧ Management of the COM lost (Problem detecting on the link)

⌧ Management of the COM recovering (Problem not detecting on the link)

General interrogation
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Global

$ Group 1 $ Group 7 $ Group 13

$ Group 2 $ Group 8 $ Group 14

$ Group 3 $ Group 9 $ Group 15

$ Group 4 $ Group 10 $ Group 16

$ Group 5 $ Group 11 Addresses per group have to be defined

$ Group 6 $ Group 12

Counter General interrogation

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Global

$ Group 1 $ Group 2 $ Group 3

$ Group 4

Clock synchronisation
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Clock synchronisation
Notes:

The controlled station reports the change of hour by sending a clock synchronisation message (ASDU 103) to the
controlling station.

Command transmission
(object -specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Direct command transmission

⌧ Direct set-point command transmission

⌧ Select and execute command

⌧ Select and execute set-point command

⌧ C_SE_ACTTERM used

⌧ No additional definition

$ Short pulse duration (duration determined by a system parameter in the outstation)

Communications C264/EN CT/B30

MiCOM C264/C264C Page 89/92

$ Long pulse duration (duration determined by a system parameter in the outstation)

$ Persistent output

Transmission of integrated totals

(object -specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ Mode A : local freeze with spontaneous transmission

$ Mode B : local freeze with counter interrogation

$ Mode C : freeze and transmit by counter interrogation commands

$ Mode D : freeze by counter interrogation command, frozen values reported

spontaneously

⌧ Counter read ⌧ General request counter

$ Counter freeze without reset $ Request counter group 1

$ Counter freeze with reset $ Request counter group 2

$ Counter reset $ Request counter group 3

$ Request counter group 4

Parameter loading
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ Threshold value

$ Smoothing factor

$ Low limit for transmission of measured value

$ High limit for transmission of measured value

Parameter activation
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

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

Test procedure
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Test procedure
C264/EN CT/B30 Communications

Page 90/92 MiCOM C264/C264C

File transfer
(station-specific parameter), mark ‘X’ if function is used)
File transfert in monitor direction

⌧ Transparent file

⌧ Transmission of disturbance data of protection equipment

⌧ Transmission of sequences of events

Transmission of sequences of recorded analogue values

File transfer in control direction

$ Transparent file

Background scan
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Background scan

Acquisition of transmission delay

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ Acquisition of transmission delay

Management events priorities

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

$ Digitals Inputs and Analogs Inputs, management events priorities.

See : T101 standard Amendment 2 §7.2.2.2

7.2.9 Application Functions

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

MiCOM C264/C264C Page 91/92

Data Acquisition by Polling

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

Page 92/92 MiCOM C264/C264C

In case of using relative time-Tag (CP24Time2a), the controlled station reports :

• the change of hour

• any time correction

• by sending a clock synchronisation message (ASDU 103) to the controlling station, as

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

MiCOM C264/C264C

COMMISSIONING
Commissioning C264/EN CM/B30

MiCOM C264/C264C Page 1/14

CONTENT

1. SCOPE OF THE DOCUMENT 3

1.1 Introduction 3
1.2 Definition 3
1.3 Commissioning the product 3
1.4 Responsibility 3
1.5 Setting familiarisation 4

2. REQUIREMENTS 5

3. COMMISSIONING TESTS WITH GHU200 OR GHU201( WITH LCD) 6

3.1 Preparation 6
3.2 Check version & number 7
3.3 Faults 8
3.4 Check the boards status 8
3.5 Checking the binary signal inputs 9
3.6 Checking the output relays 10
3.7 Testing the communication with external devices 11
3.8 Testing the control functions 12
3.9 Switching from local to remote control 12
3.9.1 Local control 12
3.9.2 Remote control 12

4. COMMISSIONING TESTS WITH GHU210 OR GHU211(WITHOUT LCD) 13

C264/EN CM/B30 Commissioning

Page 2/14 MiCOM C264/C264C

BLANK PAGE
Commissioning C264/EN CM/B30

MiCOM C264/C264C Page 3/14

1. SCOPE OF THE DOCUMENT

This document is a chapter of MiCOM C264/C264C documentation binders. It describes the
commissioning of the product and should not be confused with application commissioning.
This chapter follows the C264/EN IN (Installation) chapter.
1.1 Introduction
To commission MiCOM C264/C264C, it is necessary to verify that the hardware is
functioning correctly and that the application-specific software settings have been applied to
the MiCOM C264/C264C.
To verify that the MiCOM C264/C264C is operating correctly, a database has to be loaded
into the computer. Once the database has been loaded, tests should be performed on each
a single MiCOM C264/C264C element.
As the MiCOM C264/C264C ’s menu language is user-selectable, it is acceptable for the
Commissioning Engineer to change it to allow accurate testing as long as the menu is
restored to the customer’s preferred language on completion.
Before carrying out any work on the equipment, the user should be familiar with the contents
of the chapter C264/EN SA (Safety) 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 Front Panel when MiCOM C264/C264C is powered up.

• The starting point is the delivery form that describes all of the delivered hardware
components that constitute the MiCOM C264/C264C.
1.4 Responsibility
Most commissioning activities involve a power supply that can damage the installation or
cause injury to the operator. The chapter C264/EN SA (Safety) should be read carefully
before any handling.
Before starting commissioning, the contractual and human responsibilities should be clearly
defined.
Only qualified and competent persons should carry out commissioning and the validation
tests.
C264/EN CM/B30 Commissioning

Page 4/14 MiCOM C264/C264C

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).
Commissioning C264/EN CM/B30

MiCOM C264/C264C Page 5/14

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.
C264/EN CM/B30 Commissioning

Page 6/14 MiCOM C264/C264C

3. COMMISSIONING TESTS WITH GHU200 OR GHU201( WITH LCD)

3.1 Preparation
After the MiCOM C264 has been installed and connected as described in Chapters
C264/EN IN and C264/EN CO, the commissioning procedure can begin.
Before turning on the power supply voltage, the following items must be checked:

• Is the device connected to the protective ground at the specified location?

• Does the nominal (and measured) voltage of the battery agree with the nominal
auxiliary voltage of the device?

• Are the current and voltage transformer (if used) connections, grounding, and phase
sequences correct?
After the wiring work is completed, check the system to make sure it is properly isolated.
Once all checks have been made, the power supply voltage may be turned on.
After the voltage has been applied, the MiCOM C264 starts up.
During start-up, various tests are carried out (see section entitled ‘Diagnose level1’ in
Chapter C264/EN MF (Maintenance)).
The LED indicator labelled ‘HEALTHY’ (Fourth LED) will light up.
After approximately 30 s, the MiCOM C264 is ready for operation.
In initial, factory-set condition or after a cold restart, the front panel displays a message
“AREVA”.
After the settings have been made, the following checks should be carried out before any
interlocks or isolation is cancelled:

• Is the software and database versions compatible with the hardware?

• Are all boards correctly assigned within the MiCOM C264?

• Are all IOs correctly configured and recognised by the C264?

• Are all communications (S-BUS, T-BUS and L-BUS) correctly configured and
recognised?

• Are the control functions fully operational?

• Is the automation running?

The following chapters describe the checks to be performed to answer these questions and
ensure that the MiCOM C264 is fully operational in its application.
Commissioning C264/EN CM/B30

MiCOM C264/C264C Page 7/14

3.2 Check version & number

In the commissioning process this panel is the first to check. The MiCOM C264 serial
number tells if the C264 is the ordered one, and indirectly gives the hardware version.
The software version from the VC document gives features and limitation of the MiCOM
C264/C264C.
The database version is given by PACiS SCE database version and describes all the
settings on the MiCOM C264/C264C.
The operational mode indicates whether the device is in a maintenance or operational mode.

S E R V I C E <time>

S E R I A L N B :

S O F T W A R E V E R S I O N :

D B 1 V E R S I O N S T A T E :

D B 2 V E R S I O N S T A T E :

O P E R A T I N G H O U R S :

O P E R A T I N G M O D E :

R E D U N D A N C Y M O D E :
C264/EN CM/B30 Commissioning

Page 8/14 MiCOM C264/C264C

3.3 Faults
If the first LED is alight, this means that there is something wrong inside the C264.
The FAULT panel gives information about the problem

F A U L T <time>

<Description of the problem>

3.4 Check the boards status

MiCOM C264 front panel gives access to C264 boards status (refer to chapter C264/EN HI).
Board labels are defined during the configuration phase. They are based on short names
and are indexed automatically. The default configuration model is:

• GHU Graphical Human Unit

• BIU Basic Interface Unit (power supply)

• CCU Circuit breaker Control Unit (SBO board)

• DIU Digital Input Unit

• DOU Digital Output Unit

• AIU Analogue Input Unit (DC current and voltage input)

• TMU Transducerless Measurements Unit (CT/VT board)

The product checks whether the number of installed boards matches with the number of
boards configured, the following messages are generated depending on the results:

• PresConf Board configured present and operational

• Failure Board configured present and faulty

• ConfButMissing Board configured not present

• Too Many Board not configured but present (spare)

Commissioning C264/EN CM/B30

MiCOM C264/C264C Page 9/14

B O A R D <time>
<Board Label><Number>
<Board Status>
<Board Label><Number>
<Board Status>
<Board Label><Number>
<Board Status>
<Board Label><Number>
<Board Status>
<Board Label><Number>
<Board Status>
<Board Label><Number>
<Board Status>
N°page/Number of Pages

3.5 Checking the binary signal inputs

MiCOM C264 front panel gives access to input status for all DI boards (DIU200, DIU210 or
CCU200).
For DIU200 and DIU210 boards:

D I <time>
DIU <Number>

DI 0 <status> DI 8 <status>
DI 1 <status> DI 9 <status>
DI 2 <status> DI 10 <status>
DI 3 <status> DI 11 <status>
DI 4 <status> DI 12 <status>
DI 5 <status> DI 13 <status>
DI 6 <status> DI 14 <status>
DI 7 <status> DI 15 <status>

N°page/Number of Pages
C264/EN CM/B30 Commissioning

Page 10/14 MiCOM C264/C264C

For CCU200 boards:

D I <time>
CCU <Number>

DI 0 <status>
DI 1 <status>
DI 2 <status>
DI 3 <status>
DI 4 <status>
DI 5 <status>
DI 6 <status>
DI 7 <status>

N°page/Number of Pages

3.6 Checking the output relays

MiCOM C264 front panel gives access to output relays status for all DO boards (DOU200 or
CCU200).
For DOU200 boards:

D O <time>
DOU <Number>

DO 0 <status> DO 8 <status>
DO 1 <status> DO 9 <status>
DO 2 <status>
DO 3 <status>
DO 4 <status>
DO 5 <status>
DO 6 <status>
DO 7 <status>

N°page/Number of Pages
Commissioning C264/EN CM/B30

MiCOM C264/C264C Page 11/14

For CCU200 boards:

D O <time>
CCU <Number>

DO 0 <status>
DO 1 <status>
DO 2 <status>
DO 3 <status>

N°page/Number of Pages

3.7 Testing the communication with external devices

The IED panel gives access to the connection state with external devices on Ethernet
protocol or serial links:

I E D <time>

IP CLIENT NB:

IP SERVER : <protocol>
<Server 1 Name>
<Server 1 IP address> <connection state>
<Server 2 Name>
<Server 2 IP address> <connection state>
…
LEGACY DEVICE : <protocol>
<IED 1 name>
<IED 1 address> <connection state>
<IED 1 name>
<IED 1 address> <connection state>
…
N°page/Number of Pages
C264/EN CM/B30 Commissioning

Page 12/14 MiCOM C264/C264C

3.8 Testing the control functions

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

MiCOM C264/C264C Page 13/14

4. COMMISSIONING TESTS WITH GHU210 OR GHU211(WITHOUT LCD)

After the MiCOM C264 has been installed and connected as described in Chapters C264/EN
IN and C264/EN CO, the commissioning procedure can begin.
Before turning on the power supply voltage, the following items must be checked:

• Is the device connected to the protective ground at the specified location?

• Does the nominal (and measured) voltage of the battery agree with the nominal
auxiliary voltage of the device?

• Are the current and voltage transformer (if used) connections, grounding, and phase
sequences correct?
After the wiring work is completed, check the system to make sure it is properly isolated.
Once all checks have been made, the power supply voltage may be turned on.
After the voltage has been applied, the MiCOM C264 starts up.
During start-up, various tests are carried out (see section entitled ‘Diagnose level1’ in
Chapter C264/EN MF (Maintenance)).
The LED indicator labelled ‘HEALTHY’ (Fourth LED) will light up.
After approximately 30 s, the MiCOM C264 is ready for operation.
After the settings have been made, it is necessary to check that the software and the
database versions are compatible with the hardware.
The following chapters describe the checks to be performed with CMT to answer these
questions and ensure that the MiCOM C264 is fully operational in its application.
The CMT is fully described in IN chapter.
With the CMT, the “Computer version” button gives access to the current C264 software
version, the active database and the computer operational mode.
For a normal behaviour, the computer mode is “ACTIVE”
C264/EN CM/B30 Commissioning

Page 14/14 MiCOM C264/C264C

BLANK PAGE
Record Sheet C264/EN RS/B30

MiCOM C264/C264C

RECORD SHEET
Record Sheet C264/EN RS/B30

MiCOM C264/C264C Page 1/6

CONTENT

1. SCOPE OF THE DOCUMENT 3

2. COMMISSIONING RECORD 4

3. MAINTENANCE RECORD SHEET 5

C264/EN RS/B30 Record Sheet

Page 2/6 MiCOM C264/C264C

BLANK PAGE
Record Sheet C264/EN RS/B30

MiCOM C264/C264C Page 3/6

1. SCOPE OF THE DOCUMENT

This document is a chapter of MiCOM C264 documentation binders. It describes the
Commissioning record sheet (RS) and the Maintenance Record of this computer.
The purpose of this chapter is to follow the history of the MiCOM C264 hardware
replacement.
C264/EN RS/B30 Record Sheet

Page 4/6 MiCOM C264/C264C

2. COMMISSIONING RECORD
Commissioning Date :
Engineer :
Station Name :
Circuit Name:
Front Plate Information
Under the top access cover, there is the following type of label:

Cortec number

C264M11I2B00012530000111S1 Serial number

S.A 110 à 125 Vdc N˚ série 117268

Serial n˚
Nominal wetting
Voltage digital inputs 110 / 125 Vdc

Nominal wetting
Nominal Power voltage for digital
supply Input inputs
Voltage C0151ENa

Fill in the following array according to the label under the top access cover:

Serial number
Cortec number
Auxiliary voltage for power supply
Nominal wetting voltage for digital inputs

*Delete as appropriate
Have all relevant safety instructions been followed? Yes/No*

Product checks
Visual inspection with the computer de-energized

Relay damaged? Yes/No*

Rating information correct for installation? Yes/No*
Case earth installed? Yes/No*
Record Sheet C264/EN RS/B30

MiCOM C264/C264C Page 5/6

3. MAINTENANCE RECORD SHEET

Product Serial number

Slot letter in
the rack Previous board New board
DATE Engineer Board type
(between A Serial number Serial number
and Q)
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
C264/EN RS/B30 Record Sheet

Page 6/6 MiCOM C264/C264C

BLANK PAGE
Maintenance C264/EN MF/B30

MiCOM C264/C264C

MAINTENANCE
Maintenance C264/EN MF/B30

MiCOM C264/C264C Page 1/14

CONTENT

1. SCOPE OF THE DOCUMENT 3

2. STANDARD MAINTENANCE OPERATION 4

2.1 Level 1 diagnosis facilities 4
2.1.1 Front panel LED indications 4
2.1.2 Front panel LCD indications 6
2.2 Maintenance period 7
2.3 Method of repair 7
2.3.1 Replacing the complete MiCOM C264/C264C 7
2.3.2 Replacing a board 9
2.4 Cleaning 13

3. ENGINEERING MAINTENANCE OPERATION 14

C264/EN MF/B30 Maintenance

Page 2/14 MiCOM C264/C264C

BLANK PAGE
Maintenance C264/EN MF/B30

MiCOM C264/C264C Page 3/14

1. SCOPE OF THE DOCUMENT

This document is a chapter of MiCOM C264/C264C documentation binders. It describes the
Maintenance and FaultFinding procedures of the MiCOM C264/C264C. Reading of
C264/EN SA chapter is mandatory.
C264/EN MF/B30 Maintenance

Page 4/14 MiCOM C264/C264C

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 his own experience besides this manual. It is also
recommended to extract the logbook history in order to be informed of the intervention
conditions.
At a first level the product provides several methods to check the context of the fault. The
main ones are:

• LEDs

• LCD (Liquid Crystal Display)

2.1.1 Front panel LED indications
Maintenance C264/EN MF/B30

MiCOM C264/C264C Page 5/14

The first 5 LEDs indicate the MiCOM C264/C264C status information. With reference to the
C264/EN HI (Human Interface) chapter, the LEDs indicate from top to down:

LED id Colour LED on LED slow LED fast blinking LED off
blinking
1 Red There is at least one There is at least Not used There is
major fault one minor fault no fault
(hardware, database) (I/O board,
communication to
IEDs, …)
2 yellow All the alarms are All alarms There is at least There is
acknowledged, but displayed in the one not no alarm.
there is at least one alarm panel are acknowledged
alarm still active. inactive and alarm displayed in
acknowledged the alarm panel
NOTE: When the
alarm disappears, the
LED returns
automatically to OFF
3 yellow Computer in service Computer in Computer in test Computer
maintenance in reboot
4 Green Power up is present Not used Not used Power up
is out
5 (Fixed Red All bays managed by Bays managed by Not used All bays
only for the computer are in the computer are managed
without LOCAL mode not in the same by the
LCD panel: control mode computer
GHU2x1) are in
REMOTE
C264/EN MF/B30 Maintenance

Page 6/14 MiCOM C264/C264C

A minor fault is a fault causing only the non-availability of a part of the functionality

Phenomenon LED status Possible reason Way to solve

Functions like All LEDs are OFF The cable between CPU Verify the connection
communication, and GHU2xx, or between CPU or
automation, printing GHU2xx itself is not GHU2xx.
are well operating operational
If connection is OK and
and the watch dog on
the problem is not
BIU (see chapter
already solved then
C264/EN CO) is
change the GHU2xx
SET.
board.
The supply is ON and All LEDs are OFF Problem with BIU board Replace BIU board or
the watch dog on BIU or CPU board CPU board.
(see chapter
C264/EN CO) is
RESET.
C264 is not running LED1 ON Incoherent database Download a coherent
or not fully database
operational
Hardware fault Go in Fault panel and
Board panel to
determine the faulty
board and change it.
C264 is not fully LED1 is blinking A IED is disconnected Go into IED panel to
operational determine the
disconnected IED and
verify the cable, the BIU
configuration, the
communication
parameters inside the
PACiS configurator, the
communication
parameters inside the
relay.
The printer is Go into Fault panel and
disconnected verify that paper is
available, the printer is
switch ON, the printer
cable.
A problem about clock Go into Fault panel and
synchronisation verify that the external
clock is switch ON, the
external clock is
connected to the
antenna, the external
clock is connected to the
C264.
A problem about PLC Go into Fault panel and
(ISaGRAF) connect the ISaGRAF
workbench to the C264.
Verify the behaviour of
the PLC.

2.1.2 Front panel LCD indications

GHU200 or GHU210 board gives access to the status of the boards, the state of digital
inputs, the state of digital outputs, the connection state with external devices. The CM
chapter describes this.
Maintenance C264/EN MF/B30

MiCOM C264/C264C Page 7/14

2.2 Maintenance period

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

• the operating environment

• the accessibility of the site

• the amount of available manpower

• the importance of the installation in the power system

• the consequences of failure

2.3 Method of repair
If the MiCOM C264/C264C should develop a fault whilst in service, depending on the nature
of the fault, the watchdog contacts will change state and an alarm condition will be flagged.
Due to the extensive use of surface-mount components (SMC) faulty boards should be
replaced, as it is not possible to perform repairs on damaged circuits with SMC technology.
Thus either the complete MiCOM C264/C264C or just the faulty board, identified by the in-
built diagnostic software, can be replaced.
The preferred method is to replace the complete MiCOM C264/C264C as it ensures that the
internal circuitry is protected against electrostatic discharge and physical damage at all times
and overcomes the risk of incoherency with the new boards. In some cases, it may be
difficult to remove an installed MiCOM C264/C264C due to limited access in the back of the
cubicle and rigidity of the scheme wiring then only the faulty elements will be replaced.
Replacing boards can reduce transport costs but requires clean, dry on site conditions and
higher skills from the person performing the repair. If an unauthorised service centre
performs the repair, the warranty will be invalidated.
WARNING: BEFORE CARRYING OUT ANY WORK ON THE EQUIPMENT, THE USER
SHOULD BE FAMILIAR WITH THE CONTENTS OF THE SAFETY AND
TECHNICAL DATA CHAPTERS AND THE RATINGS ON THE
EQUIPMENT'S RATING LABEL. THIS SHOULD AVOID INCORRECT
HANDLING OF THE ELECTRONIC COMPONENTS AND DAMAGE.
2.3.1 Replacing the complete MiCOM C264/C264C
The case and rear terminal blocks have been designed to facilitate removal of the complete
MiCOM C264/C264C.
Before working at the rear of the MiCOM C264/C264C, isolate all the voltages and currents
conected to the MiCOM C264/C264C.
NOTE: The MiCOM C264/C264C have current transformer shorting switches
which close when terminal block is removed.
C264/EN MF/B30 Maintenance

Page 8/14 MiCOM C264/C264C

2.3.1.1 Replacing the complete MiCOM C264/C264C

Before any disconnection, check the labels correctly define the connectors and match with
the wishing description you have. Otherwise, note the current wiring in order to prepare the
new C264 installation.
1. Disconnect the power supply connector
2. Disconect the MiCOM C264/C264C IRIG-B, fibre optic, Ethernet RJ45 and serial links
connected on CPU board.
3. Disconnect the input/output connectors
4. Disconnect earth connection
There are two types of terminal block used on the MiCOM C264/C264C:

1 2 1

3 4 Connector
CT/VT fixation screw
Earthing
connection 5 6

7 8

9 10

11 12

13 14

15 16

17 18

19 20

21 22

23 24
Connector
fixation screw
25 26

27 28
24

C0112ENa

FIGURE 1 : LOCATION OF SECURING SCREWS FOR TERMINAL BLOCKS

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

IF THE TOP AND BOTTOM ACCESS COVERS HAVE BEEN REMOVED,

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

MiCOM C264/C264C Page 9/14

2.3.1.2 Installation of new C264

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

DO NOT REMOVE THE SCREWS WITH THE LARGER DIAMETER

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

CAUTION SHOULD BE OBSERVED AT THIS STAGE BECAUSE A CABLE

CONNECTS THE FRONT PANEL TO THE REST OF THE MICOM
C264/C264C CIRCUITRY.
Additionally, from here on, the internal circuitry of the MiCOM C264/C264C is exposed and
not protected against electrostatic discharges, dust ingress, etc. Therefore ESD precautions
and clean working conditions should be maintained at all times.
C264/EN MF/B30 Maintenance

Page 10/14 MiCOM C264/C264C

FIGURE 2 : MiCOM C264C WITH TMU200 BOARD

FIGURE 3 : MiCOM C264C WITHOUT TMU200 BOARD

Maintenance C264/EN MF/B30

MiCOM C264/C264C Page 11/14

FIGURE 4 : MiCOM C264 WITH TMU200 BOARD

FIGURE 5 : MiCOM C264 WITHOUT TMU200 BOARD

The boards within the MiCOM C264/C264C are now accessible. Figures above show the
board locations for the MiCOM C264/C264Cs in size 40TE (C264C) and size 80TE (C264)
cases respectively.
Looking to the front of the MiCOM C264/C264C with the front panel off, you can have access
to a printed circuit that connects all the boards together: this is the backplane board.
C264/EN MF/B30 Maintenance

Page 12/14 MiCOM C264/C264C

To remove a card you need to:

• Pull the backplane board (FBP280 for C264 or FBP242 for C264C) out by holding it by
the two extremities.

• remove the screws and the maintain bar at the bottom of the case.
NOTE: To ensure compatibility, always replace a faulty board with one of an
identical part number and set jumpers in identical position.
All the boards are shown and described in HW chapter.
2.3.2.1 Replacement of the Binary Input Unit (BIU241)
The BIU is the power supply board located on the extreme left-hand side (slot A) of MiCOM
C264/C264C.
Pull the power supply module forward, away from the rear terminal blocks and out of the
case. A reasonable amount of force will be required to achieve this due to the friction
between the contacts of the two medium duty terminal blocks. It is then recommended to use
the special tool for extracting board (internal reference is 2070860).
Do not forget to set the jumpers on the new board in the same position as the previous one.
2.3.2.2 Replacement of the main processor board (CPU260)
Depending on the model of the MiCOM C264/C264C the processor board carried out the
IRIG-B functionality’s so if you identify an IRIG-B connection problem you will have to
replace the processor board.
After replacement of the main processor board, all the settings required for the application
will need to be re-entered.
The CPU board is located next to the BIU board (slot B).
Do not forget to disconnect the rear cables (RJ45 Ethernet, optical fibres, IRIG-B connector
and serial links) before replacing the board and to reconnect them after.
Do not forget to set the jumpers on the new board in the same position as the previous one.
2.3.2.3 Replacement of the Ethernet switch boards (SWU200 or SWR200)
The Ethernet switch board is located on slot C.
Do not forget to disconnect the rear cables (RJ45 Ethernet and optical fibres) before
replacing the board and to reconnect them after.
Do not forget to set the jumpers on the new board in the same position as the previous one.
2.3.2.4 Replacement of the I/O boards (DIU200, DIU210, DOU200, CCU200, AIU201, AIU210)
The I/O boards can be located in any slot from C to Q.
Do not forget to set the jumpers on the new board in the same position as the previous one.
2.3.2.5 Replacement of the Transducerless Measurements Unit (TMU)
The measurement unit is on the extreme right-hand side of MiCOM C264/C264C.
Maintenance C264/EN MF/B30

MiCOM C264/C264C Page 13/14

2.3.2.6 Refit the MiCOM C264/C264C

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

Page 14/14 MiCOM C264/C264C

3. ENGINEERING MAINTENANCE OPERATION

The CMT software is able to:

• Upgrade the C264 software

• Download and switch the databases

• Download the software key

These functions are needed for customising the C264. Please report to the IN chapter.
The CMT user guide is also completely described inside the CMT online help.
Lexical C264/EN LX/B30

MiCOM C264/C264C

LEXICAL
Lexical C264/EN LX/B30

MiCOM C264/C264C Page 1/12

CONTENT

1. SCOPE OF THE DOCUMENT 3

2. LEXICAL 4
C264/EN LX/B30 Lexical

Page 2/12 MiCOM C264/C264C

BLANK PAGE
Lexical C264/EN LX/B30

MiCOM C264/C264C Page 3/12

1. SCOPE OF THE DOCUMENT

This document is a chapter of MiCOM C264 documentation binders. It is the lexical.
C264/EN LX/B30 Lexical

Page 4/12 MiCOM C264/C264C

2. LEXICAL
AC Alternating Current
ADC Analogue to Digital Converter
AI Analogue Input (Measurement Value including state attribute)
Commonly Voltage or current DC signals delivered by transducers,
and representing an external value (refer to CT/VT for AC).
AIS Air Insulated Substation
AIU Analogue Input Unit
Computer C264 Board name for DC Analogue Input
Alarm An alarm is any event tagged as an alarm during configuration phase
AO Analogue Output
Value corresponding to a desired output current applied to a DAC.
API Application Programming Interfaces
ASCII American Standard Code for Information Interchange
ASDU Application Specific Data Unit
Name given in OSI protocol for applicative data (T103, T101..)
ATCC Automatic Tap Change Control
Same as AVR, automation charged to regulate secondary voltage
AVR Automatic Voltage Regulator
Automatism used to regulate secondary voltage by automatic tap
changer control (see ATCC). Set of features can be added, see
chapter C264 FD
Bay Set of LV, MV or HV plants (switchgears and transformers) and
devices (Protective, Measurement…) usually around a Circuit
Breaker and controlled by a bay computer.
BCD Binary Coded Decimal
One C264 supported coding on a set of Digital Input, that determine a
Digital Measurement, then Measurement value (with specific invalid
code when coding is not valid). Each decimal digit is coded by 4
binary 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,
redundancy I/O
B-Watch Monitoring and control device for GIS substation.
CAD Computer Aided Design
Computer application dedicated to design like wiring, protective
setting…
CAS CASe
Computer C264 rack
CB Circuit Breaker
Specific dipole switch with capability to make line current and break
fault current. Some have isolation capability (nominal-earth at each
side)
Lexical C264/EN LX/B30

MiCOM C264/C264C Page 5/12

CCU Circuit breaker Control Unit

Computer C264 Board dedicated to switch control with 8DI, 4 DO
CDM Conceptual Data Modelling
Is the modelisation of system/devices data using a hierarchy of
structured data (called object of class) with their attributes, method or
properties and the relations between themselves.
It maps common data to devices or components of devices, with
guaranty of interoperability.
CPU Central Processing Unit
Computer C264 main Board based on PowerPC
CRC Cyclic Redundancy Check
Coding result send with packet of transmitted data to guarantee their
integrity. Usually result of a division of transmitted data by polynomial.
CSV Character Separate Values
ASCII values separated by predefined character or string like in Excel
or ASCII Comtrade.
CT Current Transformer
Basically the electric device connected to process and extracting a
current measurement. By extension part of a device (C264) that
receives AC values and convert it to numerical measurement value.
CT/VT Current and Voltage transformers
(Conventional) By extension, it is the C264 TMU board.
CT/VT Current and Voltage transformers
(Non-Conventional or New generation of captor based for example on light diffraction under
intelligent) electric field, without transformer, that give s directly numerical
measurement of voltage and current like communicating IED.
DAC Digital to Analogue Converter
Used to generate analogue signals (usually DC) from a digital value.
DB DataBase
Tool or set of data that define all configuration of a system or specific
device like computer. Opposed to setting or parameter DB has a
structure that can not be modified on line. DB are always versioned.
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 transmission
LF transmitter located at Mainflingen, Germany, about 25 km south-
east of Frankfurt/Main, broadcasting legal time on a 77.5 kHz
standard frequency.
DCP Device Control Point
Located at device level (electric device or IED). It should have its own
Remote/Local switch.
DCS Digital Control System
Generic name of system based on numeric communication and
devices, to be opposed to traditional electrically wired control.
DCT Double CounTer
Counter based on 2 DI with complementary states (counting
switchgear manoeuvre for example)
C264/EN LX/B30 Lexical

Page 6/12 MiCOM C264/C264C

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 DC Input Unit
Computer C264 Board name for Digital Input
DM Digital Measurement
Is a measurement value which acquisition is done by DI and a
specific coding BCD, Gray, 1 among N…
DO Digital Output
Used to apply a voltage to an external device via a relay, in order to
execute single or dual, transient or permanent commands.
DOU Digital Output Unit
Computer C264 Board name for Digital Output
DP Double Point
Information/control derived from 2 digital inputs/output; usually used
for position indication of switching devices (OPEN, CLOSE).
DPS Double Point Status
Position indication of switching devices (OPEN, CLOSE).
ECU Extended Communication Unit.
External module connected to the CPU board. This module converts
non-insulated RS232 into optical signal or insulated RS485/RS422.
EH90 Transmission protocol dedicated to time synchronisation and
standardised by EDF. Specification document: D.652/90-26c, March
1991.
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 transferring 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.
GHU Graphic Human interface Unit
Computer C264 Front Panel digital part (LCD, buttons, Front RS)
GHU Graphical Human Unit
Front panel of C264 with LCD and buttons
GIS Gas Insulated Substation
GMT Greenwich Mean Time
Absolute time reference
GPS Global Positioning System
Based on triangulation from satellite signal, that transmit also
absolute GMT time used to synchronise a master clock
Group Logical combination of BI (i.e. SP, DP, SI or other groups).
Lexical C264/EN LX/B30

MiCOM C264/C264C Page 7/12

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 formatting 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 analogue
signal.
JAMMED Invalid state of a Double Point:
Occurs when the two associated digital inputs are still in state 0 after
an user-selectable delay (i.e. when the transient state “ motion ” is
considered as ended).
Kbus Term used for the protocol Courier on K-Bus network (kind of
(Kbus Courier) RS422).
L-BUS Legacy Bus
Generic name of Legacy or field networks and protocols used to
communicate between C264 (Legacy Gateway function) and IED on
field bus. Networks are based on (RS232,) 422, 485. Protocols are
IEC 60850-5-103 (T103 or VDEW), Modbus AREVA or MODICON
LCD Liquid Crystal Display
Local Control Display
On C264
LD Ladder Diagram
One of the IEC1131-3 programming languages (language used to
define configurable automation).
LED Light Emitting Diode
LF Low Frequency
LOC Local Operator Console
Dedicated to maintenance operation
Local / Remote When set to local for a given control point it means that the
Control Mode commands can be issued from this point, else in remote control are
issue for upper devices.
LV Low Voltage
MAFS Marketing And Functional Specification
MC Modular Computer
Measurements Values issued from digital inputs or analogue inputs (with value, state
and time tag).
Metering Values computed depending on the values of digital or analogue
(non-tariff) inputs during variable periods of time (time integration).
C264/EN LX/B30 Lexical

Page 8/12 MiCOM C264/C264C

Metering Values computed depending on the values of digital or analogue

(tariff) inputs during variable periods and dedicated to the energy
tariffication. These values are provided by dedicated “ tariff
computer ” which are external to the MiCOM Systems.
MIDOS AREVA Connector
Used for CT/VT acquisition
MMC Medium Modular Computer
ModBus Communication protocol used on secondary networks with IED or
with SCADA RCP. 2 versions exist with standard MODICON or
AREVA one.
Module Word reserved in PACIS SCE for all electric HV devices. It groups all
switch-gears, transformer, motors, generators, capacitors, …
MOTION Transient state of a Double Point
Occurs when the two associated digital inputs are momentarily in
state 0 (e.g. position indication when an electrical device is
switching). The concept of “ momentarily” depends on a
user-selectable delay.
MPC Protection Module for Computer
MV Medium Voltage
NBB Numerical Busbar Protection
NC Normally Closed (for a relay)
NO Normally Open (for a relay)
OBS One Box Solution
Computer that provides protection and control functions with local
HMI. The prime application of this device is intended for use in
substations up to distribution voltage levels, although it may also be
used as backup protection in transmission substations. Likewise, the
OBS may be applied to the MV part of a HV substation that is being
controlled by the same substation control system.
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 under carrying
energy, e.g. circuit breaker is in Close state and the current is
unequal 0 A.
OSI Open System Interconnection
Split and define communication in 7 layers : physical, link, network,
transport, session, presentation, application
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 Probes of temperatures providing analogue signals.
Lexical C264/EN LX/B30

MiCOM C264/C264C Page 9/12

RCC Remote Control Centre

Is a computer or system that is not part of MiCOM system. RCC
communicates with and supervises MiCOM system using a protocol.
RCP Remote Control Point
Name given to the device or part used to control remotely several bay
or sub-station. Usually associate with Remote/Local sub-station
control. It is a SCADA interface managed by the MiCOM system
through Telecontrol BUS. Several RCP’s can be managed with
different protocols.
Remote Control Mode When set for a given control point it means that the commands are
issued from an upper level and are not allowed from this point.
Remote HMI Remote HMI is a client of the substation HMI server. The client may
provide all or part of functions handled by the substation HMI.
RI Read Inhibit
This output indicates the availability of an analogue output (e.g.
during DAC converting time)
RRC Rapid ReClosure
RSVC Relocatabled Static Var Compensator
RTU Remote Terminal Unit
Stand alone computer that acquires data and transmit them to RCP
or SCADA. Typically it is the C964. RTU link is the TBUS.
SAT Site Acceptance Test
Validation procedures executed with the customer on the site.
SBMC Site Based Maintenance Control mode
A bay in SBMC mode does not take into account the commands
issued from RCP; moreover, some of its digital points and
measurements (defined during the configuration phase) are not sent
anymore to the RCP (they are “ automatically ” suppressed).
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
SCADA Supervisory Control And Data Acquisition
Equivalent to RCC
SCP Substation Control Point
Name given to the device or part used to control locally several bays
or sub-station. Usually associate with Remote/Local sub-station
control. It is commonly PACIS Operator Interface.
SCS Substation Control System
SCT Single Counter
Setpoints (analogue) Analogue setpoints are analogue outputs delivered as current loops.
Analogue setpoints are used to send instruction values to the process
or to auxiliary devices.
Setpoints (digital) Digital values sent on multiple parallel wired outputs Each wired
output represent a bit of the value. Digital setpoints are used to send
instruction values to the electrical process or to auxiliary devices.
C264/EN LX/B30 Lexical

Page 10/12 MiCOM C264/C264C

SFC Sequential Function Chart

One of the IEC1131-3 programming languages (language used to
define configurable automation).
SI System Indication
Binary information that do not come from external interface. It is
related to an internal state of the computer (time status, hardware
faults…). It is the result of all inner function (AR, …), PSL, or
ISaGRAF automation.
SICU 4 Switchgear Intelligent Control Unit
Control unit of an intelligent circuit breaker (fourth generation)
SOE Sequence Of Events
Other term for the event list.
SP Single Point
SPS Single Point Status
SPC Single Point Control
ST Structured Text
One of the IEC1131-3 programming languages (language used to
define configurable automation).
Substation computer Bay computer used at substation level.
Suppression A binary information belonging to a bay in SBMC mode will be
(Automatic) automatically suppressed for the remote control. However changes of
state will be signalled locally, at SCP.
Suppression (Manual) A binary information can be suppressed by an order issued from an
operator. No subsequent change of state on a “ suppressed
information ” can trigger any action such as display, alarm and
transmission.
SWR Switch Redundant
Computer C264 board Ethernet switch with redundant Ethernet
SWU Switch Unit
Computer C264 board Ethernet switch
T101 Term used for IEC60870-5-101 protocol
T103 Term used for IEC60870-5-103 protocol
T104 Term used for IEC60870-5-104 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
TMU Transducerless Measurement Unit
Topological Interlocking algorithm, based on evaluation of topological information
interlocking of the switchgear arrangement in the HV network, the switchgear kind
and position, and defined rules for controlling this kind of switch (e.g.
continuity of power supply)
TPI Tap Position Indication (for transformers).
Frequently acquired via a Digital Measurement
TVU Transformer Voltage Unit
Computer C264 CT/VT Board : Voltage acquisition
Lexical C264/EN LX/B30

MiCOM C264/C264C Page 11/12

UCA Utility Communications Architecture

Communication standard (mainly US) used for PACIS SBUS
communication
UPI Unit Per Impulse
Parameter of counter to convert number of pulse to Measurement
value. Both data (integer and scaled float) are in common class
UCA2 Accumulator.
UTC Universal Time Co-ordinates (or Universal Time Code)
Naming that replace GMT (but it is the same)
VDEW Term used for IEC60870-5-103 protocol
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.
C264/EN LX/B30 Lexical

Page 12/12 MiCOM C264/C264C

BLANK PAGE
Publication: C264/EN T/B30

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/