c264 en Op c40 Global

MiCOM
C264/C264C
Bay Computer
Operation Guide
C264/EN O/C40
Operation Guide C264/EN O/C40
MiCOM C264/C264C Page 1/2
MiCOM C264/C264C
BAY COMPUTER
CONTENT
Safety & Handling C264/EN SA/C40
Introduction C264/EN IT/C40
Technical Data C264/EN TD/C40
Functionnal Description C264/EN FT/C40
Hardware Description C264/EN HW/C40
Connection C264/EN CO/C40
Human Machine Interface C264/EN HI/C40
Application C264/EN AP/C40
Lexical C264/EN LX/C40

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

CONTENT
1. INTRODUCTION 3
2. HEALTH AND SAFETY 4

2.1 Health and Safety 4
2.2 Installing, Commissioning and Servicing 4
3. DECOMMISSIONING AND DISPOSAL 6
4. TECHNICAL SPECIFICATIONS FOR SAFETY 7
5. HANDLING OF ELECTRONIC EQUIPMENTS 8
6. PACKING AND UNPACKING 9
7. GUARANTEES 10
8. COPYRIGHTS & TRADEMARKS 11

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

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

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

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

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

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

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

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

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

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

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

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

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

AREVA T&D EAI products are not designed with components and testing for a level of
reliability suitable for use in connection with surgical implants or as critical components in
any life support systems whose failure to perform can reasonably be expected to cause
significant injuries to a human.
In any application, including the above reliability of operation of the software products can be
impaired by adverse factors, including - but not limited - to fluctuations in electrical power
supply, computer hardware malfunctions, computer operating system, software fitness,
fitness of compilers and development software used to develop an application, installation
errors, software and hardware compatibility problems, malfunctions or failures of electronic
monitoring or control devices, transient failures of electronic systems (hardware and/or
software), unanticipated uses or misuses, or errors from the user or applications designer
(adverse factors such as these are collectively termed "System failures").
Any application where a system failure would create a risk of harm to property or persons
(including the risk of bodily injuries and death) should not be reliant solely upon one form of
electronic system due to the risk of system failure to avoid damage, injury or death, the user
or application designer must take reasonably steps to protect against system failure,
including - but not limited - to back-up or shut-down mechanisms, not because end-user
system is customised and differs from AREVA T&D EAI testing platforms but also a user or
application designer may use AREVA T&D EAI products in combination with other products.
These actions cannot be evaluated or contemplated by AREVA T&D EAI; Thus, the user or
application designer is ultimately responsible for verifying and validating the suitability of
AREVA T&D EAI products whenever they are incorporated in a system or application, even
without limitation of the appropriate design, process and safety levels of such system or
application.
MiCOM C264/C264C
INTRODUCTION
CONTENT
1. INTRODUCTION TO MiCOM 3
2. INTRODUCTION TO MiCOM GUIDES 4

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

3.1 MiCOM Computers 6
3.2 Applications and Scope 6
C264/EN IT/C40 Introduction
BLANK PAGE
1. INTRODUCTION TO MiCOM
MiCOM is a comprehensive solution capable of meeting all electricity supply requirements. It
comprises a range of components, systems and services from AREVA T&D Energy
Automation & Information.
Central to the MiCOM concept is flexibility.
MiCOM provides the ability to define an application solution and, through extensive
communication capabilities, to integrate it with your power supply control system.
The components within MiCOM are:
• P range protection relays;
• C range control products;
• M range measurement products for accurate metering and monitoring;
• S range versatile PC support and substation control packages.
• A range industrial PC
MiCOM products include extensive facilities for recording information on the state and
behaviour of the power system using disturbance and fault records. They can also provide
measurements of the system at regular intervals to a control centre enabling remote
monitoring and control to take place.
The MiCOM range will continue to be expanded. The general features of MiCOM will also be
enhanced, as we are able to adopt new technology solutions.
For up-to-date information on any MiCOM product, visit our website: www.areva-td.com
2. INTRODUCTION TO MiCOM GUIDES

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

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

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

SCADA Interface
DNP3 & IEC 60870-5-101
& IEC 60870-5-104
Master clock
(GPS)
Operator
Interface
HV FEEDER BAY
Fast Ethernet
IEC 61850
C264
C264C
Main protection
EHV FEEDER BAY
I/Os
C264
I/Os
MV FEEDER BAYS
COMMON BAY
Cubicle/ Switchboard MV FEEDER BAYS

TRANSFORMER BAY integration
C0001ENc
FIGURE 1 : TYPICAL USE OF A MiCOM C264 – BAY CONTROLLER
PSTN or Remote
SCADA Interface
dedicated HMI
DNP3 & IEC 60870-5-101
line
& IEC 60870-5-104
Px30
Px40
NP3,
DBUS,
M720 IE 0-5-103,
I 870-5-101
Px20
Px30
PLC
BC
I/Os
I/Os
C0002ENb
FIGURE 2 : TYPICAL USE OF A MiCOM C264 – RTU, DATA CONCENTRATOR APPLICATION

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

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

This document is a chapter of MiCOM C264 documentation binders, describing the
Technical data of this computer.
2. CONFORMITY
(Per Article 10 of EC Directive 73/23/EEC).
The product designated “MiCOM C264/C264C computer” has been designed and
manufactured in conformance with the standard IEC 60255-27:2005 and is compliant with
the European Commission Low Voltage Directive 73/23/EEC.
3. GENERAL DATA
3.1 Design
Surface-mounted case suitable for wall installation or flush-mounted case for 19” cabinets
and for control panels.
3.2 Installation Position
Vertical ±15°
3.3 Degree of Protection
Per DIN VDE 0470 and EN 60255-27:2006 or IEC 60255-27:2005.
IP52 for the front panel with LCD or Leds.
IP10 for the “blind” front panel (GHU220,GHU221).
IP50 for the body case of MiCOM C264C.
IP20 for the rack of MiCOM C264.
IP20 for rear panels of C264/C264C, except reduced to IP10 when the black MiDOS 28 way
terminal block is mounted (for TMU200 ,TMU210 and TMU220 boards).
3.4 Weight
Case 40 TE: approx. 4 kg
Case 80 TE: approx. 8 kg
3.5 Dimensions and Connections
See dimensional drawings (Hardware description section – C264_EN_HW) and terminal
connection diagrams (C264_EN_CO).
3.6 Terminals
PC Interface:
DIN 41652 connector, type female D-Sub, 9-pin on the front panel.
A direct wired cable is required.
Ethernet LAN (in the rear panel through the CPU260 board):
RJ-45 female connector, 8-pin for the 10/100Base-T self-negotiation.
ST female connector for the 100Base-F.
IRIG-B Input (optional, in the rear panel through the CPU260 board):
BNC plug.
Conventional communication links:
M3 threaded terminal ends, self-centring with wire protection for conductor cross sections
from 0.2 to 2.5 mm² for BIU241 board.
DIN 41652 connector; type D-Sub, 9-pin on the CPU260 board in the rear panel.
Optical fibres trough ECU200 (external RS232/optical converter): optical plastic fibre
connection per IEC 874-2 or DIN 47258 or ST ® glass fibre optic connection (ST ® is a
registered trademark of AT&T Lightguide Cable Connectors).
Inputs /Outputs or power supply modules:
from 0.2 to 2.5 mm² for DIU200, DIU210, DIU220, DOU200, CCU200, AIU201, AIU210,
AIU211 and BIU241 boards.
The I/O boards and BIU241 are equipped with a 24-way 5.08 mm pitch male connector.
Current-measuring and Voltage-measuring inputs:

between 2.5 and 4 mm² for TMU200 Transducerless (4CT+4VT) board.
The TMU200 (4CT+4VT) board is equipped with a “MiCOM: ASSEMBLY CONNECTEUR
BLOCKL GJ104” connector.
3.7 Creepage Distances and Clearances
Per IEC 60255-27:2005 and IEC 664-1:1992.
Pollution degree 2, working voltage 250 V.
Overvoltage category III, impulse test voltage 5 kV.
4. RATINGS
4.1 Auxiliary Voltage
MiCOM C264/C264C computers are available in four auxiliary voltage versions, specified in
the table below:
Version Nominal ranges Operative DC range Operative AC range

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

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

A01 24 VDC if V >10.1 VDC Input status is set
if V < 5 VDC Input status is reset
A02 48 to 60 VDC if V >17.4 VDC Input status is set
if V < 13.5 VDC Input status is reset
A03 110 to 125 VDC if V > 50 VDC Input status is set
if V< 34.4 VDC Input status is reset
A04 220 VDC if V > 108 VDC Input status is set
if V< 63 VDC Input status is reset
The DIU200 board is designed to allow 2 inputs serially connected. This answers to the
following need:
Un
IN1 IN2
C264
0 VDC C0124ENa
If R is open then IN1 and IN2 are set.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

5.4.2 DIU210
Nominal voltage Current at Un (mA)

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

Power consumption per input:
Un = 24VDC to 110V DC: 0,5W ± 30% per input
Un > 110VDC: 5mA ± 30%
From 48Vdc to 220Vdc voltage, a high current consumption is created on binary inputs
during a short period and circulates through external binary contacts to clean them. See the
peak current response curve.
WARNING: FOR THE 24V VOLTAGE, THERE IS NO SHORT PEAK CURRENT

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

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

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

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

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

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

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

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

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

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

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

Free Fall Test IEC 60068-2-31 (1969) 2 falls of 5 cm (Computer not powered)
+ A1 (1982)
Free Fall Packaging
Test IEC 60068-2-32 (1975)
+A1 (1982) + A2 25 falls of 50 cm (Packaging computer)
(1990)
Vibration Response – IEC 60255-21-1 (1988) Class 2:
Powered On
Acceleration: 1g from 10 to 150Hz
Vibration Response – IEC 60255-21-1 (1988) Class 2:
Not Powered On
Vibration Endurance – IEC 60068-2-6 (1995) Class 2:
Not Powered On
Shocks – Not Powered IEC 60255-21-2 (1988) Class 1:
On
15g, 11 ms
Shocks – Powered On IEC 60255-21-2 (1988) Class 2:
10g, 11 ms
Bump Test – Not IEC 60255-21-2 (1988) Class 1:
Powered On
10g, 16ms, 2000/axis
Seismic Test – Powered IEC 60255-21-3 (1993) Class 2:
On
Acceleration: 2g
Displacement: 7.5mm upon axe H
Acceleration: 1g
Displacement: 3.5mm upon axe V
7.3 Atmospheric Test

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

Operating (1993)
Dry Heat Test – Storage IEC 60068-2-1 (1990) Test Bd:

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

Inrush current (start-up) DICOT HN 46-R01-4 T < 1.5 ms / I < 20 A
(1993)
1.5ms < T < 150 ms / I < 10 A
T > 500 ms / I < 1.2 In
Supply variation IEC 60255-6 (1988) Vn ± 20%
Vn+30% & Vn-25% for information
Overvoltage (peak IEC 60255-6 (1988) 1.32 Vn max
withstand)
2 Vn during 10 ms (for information)
Ramp down to zero N/A From Vn down to 0 within 1 minute
From Vn down to 0 within 100 minutes
Ramp up from zero N/A From 0 up to Vn within 1 minute
From 0 up to Vn within 100 minutes
Supply interruption IEC 60255-11 (1979) From 2.5 ms to 1 s at 0.8 Vn
50 ms at Vn, no malfunction
Reverse polarity N/A Polarity – for the lower potential of the
supply
Polarity + for the lower potential of the
supply
Ripple (frequency IEC 60255-11 (1979) 12% Vn at f=100Hz or 120Hz
fluctuations)
12% Vn at f=200Hz for information
7.5 “AC” Auxiliary Supply Test

Supply variations IEC 60255-6 (1988) Vn ± 20%
AC Voltage dips & short EN 61000-4-11 (1994) 2ms to 20ms & 50ms to 1s
interruptions
50 ms at Vn, no malfunction
Frequency fluctuations IEC 60255-6 (1988) 50 Hz: from 47 to 54 Hz
60 Hz: from 57 to 63 Hz
Voltage withstand N/A 2 Vn during 10 ms (for information)
7.6 EMC

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

IEC 61000-4-2 (1995) + 8kV contact / 15 kV air
A1 (1998) + A2 (2001)
Radiated Immunity IEC 60255-22-3 (2000) Class 3:
IEC 61000-4-3 (2002) + 10 V/m – 80 to 1000 MHz
A1 (2002)
IEEE C37.90.2 (1987) & spot tests
35 V/m – 25 to 1000 MHz
Fast Transient Burst IEC 60255-22-4 (2002) Class 4: 4kV – 2.5kHz (CM)
IEC 61000-4-4 (1995) + Class 4: 2.5kV – 2.5kHz (DM) on DI/DO
A1 (2001)
IEEE C37.90.1 (1989)
Surge immunity IEC 61000-4-5 (1995) + Class 4:
A1 (2001)
4kV (CM) – 2kV (DM)
High frequency IEC 61000-4-6 (2003) Class 3:
conducted immunity
10 V, 0.15 – 80 MHz
Harmonics Immunity IEC 61000-4-7 (2002) 5% & 10% de H2 à H17
Power Frequency IEC 61000-4-8 (1993) Class 5:
Magnetic Field Immunity
100A/m for 1mn
1000A/m for 3s
Pulse magnetic field IEC 61000-4-9 (1993) Class 5:
immunity
6.4 / 16 µs
1000A/m for 3s
Damped oscillatory IEC 61000-4-10 (1993) Class 5:
magnetic field immunity + A1 (2001)
100 kHz & 1 MHz – 100A/m
Power Frequency IEC 61000-4-16 (1998) CM 500 V / DM 250 V via 0.1 µF

Conducted emission EN 55022 (1998) + A1 Gr. I, class A: from 0.15 to 30 MHz
(2000) + A2 (2003)
Radiated emission EN 55022(1998) + A1 Gr. I, class A: from 30 to 1000 MHz
(2000) + A2 (2003)
Functional Description C264/EN FT/C40
MiCOM C264/C264C
FUNCTIONAL DESCRIPTION
TABLE OF CONTENTS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

This mode is entered in case of an anomaly. In this mode the general working of the
computer is not very disturbed because it involves the degradation of only few functions. The
watchdog relay is activated.
The downgraded mode depends on the hardware configuration of the computer. But we can
define the different kinds of downgraded modes that can happen:
• Operation without DO on a board
• Operation without DI on a board
• Operation without AI on a board
• Operation without communication with some relays
• Operation without communication with some station devices
• A combination of two, or more, of these previous items

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

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

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

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

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

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

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

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

2.2 Database management

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

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

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

This function answers to a request of DB switching coming from the station bus. This
request specifies the Version of the standby DB (Vdbs) to become current. After
a DB switch the computer automatically reboots and goes into active Mode if the DB is
coherent with the software.
SWITCH
T0 T0 + T1
CURRENT STANDBY CURRENT STANDBY
Vdbs n.m Vdbs x.y Vdbs x.y Vdbs n.m
DB1 DB2 DB2 DB1
T0 + T1 MAINTENANCE
MAINTENANCE
T0 + T1 CURRENT STAND-BY
Vdbs x.y Vdbs n.m
DB2 DB1
OPERATIONAL
C0309ENa
FIGURE 4: DATABASES SWITCHING

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

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

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

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

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

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

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

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

synchronises through SCADA bus
SystemMaster
Clock
Which synchronises Operator

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

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

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

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

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

C0125ENb
FIGURE 6: REDUNDANCY MANAGEMENT

The two computers exchange information using:
• The Station Bus, to give their internal status (IS)
• 2 couples of DI/DO of the BIU board:
− DI1/DO1 to indicate the Active Status: DO1 is closed if the computer is Active
− DI2/DO2 to indicate a Station Bus failure: DO2 is open in case of failure

A value is given to each type of computer failure: the computer IS is calculated by
summing all failure values. The healthiest computer is the one with the minimal
internal status. The healthiest computer is active.
Computer failure Value

DOU board failure 0x20
CCU board failure 0x10
CT/VT board failure 0x08
DIU board failure 0x04
BIU board failure 0x02
AIU board failure 0x01
The algorithm to elect the Active computer is described in the table below.
The initial state is “Initialisation” (state 0) and the “DI1≠1” event is generated.
“L_IS” is the internal status of the computer, “R_IS” is the internal status of the redundant
one.
The “confirmed DI2 ≠ 1” event is a detection of a Station Bus failure on the other computer
(DI2 = 0) confirmed during 20 seconds.
T1 is the timer of Active status confirmation during the computer initialisation (default value:
5 seconds for the Main computer, marked in configuration, 30 seconds for the Backup one).
T2 is the timer of master election (default value: 5 seconds).
The switching time is less than 30 seconds.
State 0: State 1: State 2: State 3: State 4: State 5:

Initialisation Waiting end of Standby Standby / T2 Active Standby mode
initialisation / T1 timer on- on-going
timer on going going
DI1≠1 ≠ T1 timer / ≠ close DO1 ≠ stop T2 timer / /
launching ≠ go to state 4 ≠ go to state 4
≠ go to state 1
DI1=1 go to state 2 ≠ stop T1 timer / ≠ open DO1 go to state 5 /
≠ go to state 2 ≠ stop T2 timer
≠ go to state 2
“confirmed” / / ≠ T2 timer / / /
DI2≠1 launching
≠ close DO1
≠ go to state 3
Remore IS / / If (L_IS<R_IS) If (L_IS>R_IS) / /

then then
≠ T2 timer ≠ stop T2 timer
launching ≠ open DO1
≠ close DO1 ≠ go to state 2
≠ go to state 3
End of T1 / If DI1≠1 / not possible not possible /
timer
then:
≠ T2 timer
launching
≠ close DO1
≠ go to state 3
else:
≠ go to state 2
End of T2 / / / go to state 4 / /
timer
End of / not possible not possible not possible not possible open DO1 if
standby mode conditions to enter
going-on standby mode are
not true anymore
then
≠ T2 timer
launching
≠ go to state 3
else
≠ go to state 2
3. COMMUNICATIONS
MiCOM C264/C264C computer ensures up to three different types of communications:
• Telecontrol Bus (T-Bus),
• Station Bus (S-Bus),
• Legacy Bus (L-Bus).

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

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

Link layer: Ethernet 10 or 100 Mb/s
Physical support:
• Copper twisted pair (RJ45 connector)
• Optical fibber (multimode or monomode)

The optical port is optional. To increase the number of Ethernet port, two Ethernet switch
boards are available:
• SWU with 4 RJ45 ports and up 2 optical ports (multimode or monomode)
• SWR with 4 RJ45 ports and 2 optical ports for a redundant ring (multimode or
monomode)
3.3.1 Exchanges
MiCOM C264/C264C computer acquires and sends data on IEC-61850 network using two
mechanisms:
• REPORT
• GOOSE
The REPORT is specific between a server and one client, it provides:
• data value
• data state or quality attribute (validity and several kind of invalid state)
• time tag of last data value change
• time tag quality attribute (server synchronised or not when event has occured)
Data quality defines if data is valid or several kind of invalidity: unknown when disconnected,
Saturated, Undefined… REPORTS are sent/received with their RFI (Reason For Inclusion):
periodic, spontaneous state/value change or following control.
The GOOSE is a short message ( data value and quality) sent in multicast to all SBUS
equipment, this is quicker than Report.
3.3.2 Supported Common Data Classes
MiCOM C264/C264C computer exchanges data using Common Data Classes. The following
list gives implemented ones:
Kind of information IEC 61850 Common Data Classes

Status Information Single Point Status (SPS)
Double Point Status (DPS)
Integer Status (INS)
Protection Activation Information (ACT)
Directional Protection Activation Information (ACD)
Binary Counter Reading (BCR)
Measurand Information Measured Value (MV)
WYE
Delta (DEL)
Controllable Status Information Controllable Single Point (SPC)
Controllable Double Point (DPC)
Controllable Integer Status (INC)
Binary Controlled Step Position Information (BSC)
Controllable Analogue Information Controllable Analogue Setpoint Information (APC)
TABLEAU 1: DATA MANAGEMENT

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

Several kinds of boards can be used in MiCOM C264/C264C. Digital Input & Outputs,
Measurement acquisitions are checked to validate information/action and time tagged on any
change of state or value.
The MiCOM C264/C264C computer acquires digital and analogue inputs, counters, digital
measurements, and analogue measurements from CT/VT. Configuration parameters,
filtering and triggering are applied to these inputs and depend on their type.
4.1 Input check

Input data coming from the physical MiCOM C264/C264C boards or from the different
communication networks are periodically checked. Invalidity status of these data is internally
fixed for:
• Self-test (DI, AI, board self test failure)
• Unknown (DI, AI, communication failure to remote acquisition like IED)
• Toggling (DI, X change of state in given time)
• Over-range (AI, saturation of its transducer, or Counter value reaching limits)
• Open Circuit (AI kind 4-20mA with current value under 4mA)
• Undefined (Digital Measurement or Counter with invalid DI coding)
4.2 Output check

Output boards are periodically checked at their logical level. In the event of a logical circuit
test fails the board is set faulty. Controls on this board or upon disconnected IEDs are
refused.
4.3 Time tagging
All physical input data are time tagged with a 1ms accuracy. All internal logic data are time
stamped with a 1ms accuracy.
Analogue acquisition time tagging is done but driven by periodic polling of this kind of board.
Periods are based on multiple of 100ms.
Information coming from IED is time tagged by IED itself if it has this facility otherwise it is
performed at computer level when receiving the data.
4.4 Digital input acquisition (DI)
4.4.1 Acquisition
Acquisition of binary information is done via DIU200/DIU210 (16 DIs) or CCU200 (8 DIs + 4
DOs) boards:
Digital Input (DI) can take one among two values: 1 or 0. The value 1 is associated with the
presence of an external voltage; the value 0 is associated with the absence of the voltage.
The values, 1 or 0 are written by the hardware when the external voltage is above (or below
a threshold). The value of the threshold is given in the hardware specification document.
A transition from 0 to 1 or 1 to 0 is generally followed by a succession of transitions
(bounces) before the value stabilises. It is necessary that the software filters these bounces.
Each change of state of a digital input is time stamped with a resolution better than 1 ms.
Debouncing & Toggle

Filtering for BI Filtering for To BI
BI treatment
Hardware Software Time Debouncing & Special

acquisition acquisition stamping Filtering for treatment To measurements
DM for DM treatment
Debouncing & Special

Filtering for treatment To counters
counters for treatment
counters
C0126ENa
FIGURE 8: DIGITAL INPUT PROCESSING
4.4.2 Debouncing and filtering

A filtering is applied on digital inputs as follow:
Filtering time
Debouncing
time
t0 t1 t2
C0127ENa
FIGURE 9: DIGITAL INPUT FILTERING AND DEBOUNCING
t0 is the instant of detection of the first transition. t1 is the instant of validation of the change of
state. t2 is the end of the filtering. (the signal has remained stable from t1 to t2). The change of
state is time stamped at t0 .
A value of 0 means that no filter is applied: a change of state is validated as soon as it is
detected.
Three couple of delays (debouncing / filtering) are defined:
• one for all DI which will be used as BI
• one for all DI which will be used as DM
• one for all DI which will be used as counters

4.4.3 Toggling
A digital input is said to be toggling if its state has changed more than N times in a given
period of time T1.
A toggling DI returns in the normal state if its state has not changed within another period of
time T2.
N, T1 and T2 are parameters determined at configuration time on a per system basis (same
parameters for all MiCOM C264/C264C computers of a system).
The toggle filtering applies only on DI that will be used as BI (there is no toggle filtering on DI
that will be used for counters or DM).
4.5 Counters acquisition (CT)

The counters are acquired on the same boards as the DIs. There are two types of counters
SCT (Single counter) and DCT (Double counters).
This interface allows acquisitions of pulses delivered from energy metering devices
corresponding to a calibrated quantity of energy.
Each valid pulse increments the value of an accumulator used to compute the quantity of
energy delivered during a given period.
Counter values are stored in static memory (secured with a capacitor, > 48h autonomy);
Counters are kept for more than 48H when the C264 power supply is off.
The pulse frequency should be 20 Hz as a maximum. So, the debouncing and filtering
values must be chosen in consequence.
4.5.1 Single counter (SCT)
A SCT is acquired on a single contact.
The value of the accumulator is incremented after a low to high transition, confirmed after a
filtering time (Tcount). Tcount is defined for the whole system, with a step of 5ms: the chosen
value must be coherent with the pulse frequency (i.e. all counters of a system use the same
Tcount).
A subsequent pulse can be taken into account only after a high to low transition.
Tcount Tcount
Transition validated,
Low to high transition
counter is incremented
Transition discarded
Low to high transition
C0128ENa
FIGURE 10: SINGLE COUNTER CHRONOGRAM

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

TC
CC
Low to high transition Low to high transition, but no

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

confirmed, counter is invalid
Transition validated,
counter is incremented Detection of non-complementarity
C0129ENa
FIGURE 11: DOUBLE COUNTER CHRONOGRAM
4.6 Digital measurement (DM)

The digital measurements (DM) are derived from the Digital Inputs. They are acquired on the
same boards as the DIs.
This interface, allowing acquisitions of a digital measurement, is a digital value coded on N
wired inputs. Each wired input represents a bit of the value, and can take only one of two
values: low or high. The maximum number of digital inputs can be used for a digital
measurement is 64.
DM are used to process measurements and tap position indications.
A DM can be associated to a Read Inhibit (RI) signal. The acquisition process is different
depending on the presence of this RI signal.
4.6.1 Acquisition without Read Inhibit signal
The DM is calculated at each change of state of one of its inputs.
A stability processing is applied at each calculation to confirm the value.
If the difference between the current value and the previous confirmed value is less or equal
than Vstab (value defined in configuration), then the current value is confirmed.
If the difference is greater than Vstab, then the Tstab delay is launched (value defined in
configuration, from 0 to 60s, with a 10 ms step). If a Tstab delay is already launched, this one
is cancelled. At the end of the delay, the DM value is confirmed.
Confirmed Confirmed Confirmed

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

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

new calculation new calculation new calculation
∆>V stab => Tstab ∆>V stab => Tstab ∆>V stab => Tstab
launched re-launched re-launched
C0131ENa
FIGURE 13: DM UNDEFINED
If Vstab is equal to 0, there is no stability processing: all DM values are sent at each
calculation.
4.6.2 Acquisition with Read Inhibit signal
When the RI signal changes to set state, the Tinh delay is launched. If the signal is always set
at the end of the delay, the DM is declared UNDEFINED. Otherwise, if the RI signal changes
to reset state before the end of the delay, the current DM value is transmitted.
Tinh Tinh
RI
DM value transmitted DM UNDEFINED

C0132ENa
FIGURE 14: ACQUISITION WITH RI
If the RI signal is invalid, the DM will be invalid.

4.6.3 Encoding
The following codes are allowed for DM:
CODE Number of bits ( max. 64) Range of value

BCD 4 (1 BCD decade) 0 to 9
8 (2 BCD decades) 0 to 99
12 (3 BCD decades) 0 to 999
16 (4 BCD decades) 0 to 9,999
32 (8 BCD decades) 0 to 99,999,999
64 (16 BCD decades) 0 to 9,999,999,999,999,999
Binary n 0 to 2n-1
Gray n 0 to 2n-1
Decimal 16 0 to 69
(1 bit among 6 for the tens,
1 among 10 for the units)
32 0 to 4999
(1 bit among 4 for the thousands,
1 bit among 9 for the hundreds,
1 bit among 9 for the tens,
1 bit among 10 for the units)
64 0 to 9,999,999
(1 bit among 9 for the millions,
1 bit among 9 for the hundreds of thousands,
1 bit among 9 for the tens of thousands,
1 bit among 9 for the thousands,
1 among N n 0 to n
One supplementary bit can be used for the sign (0 indicates a positive value, 1 indicates a
negative value).
Capability extension for the Tap Position Indication only:
CODE Number of bits Range of value

1 among N 2 to 64 0 to 2
to 0 to 64
4.7 Analogue input acquisition (AI)

Acquisition of AC voltages and currents coming from the electrical network is done via
TMU200 (4CT + 4 VT) board.
Acquisition of DC voltages or currents signals is done via AIU201 (4 AIs) or AIU210 (8 AIs)
boards. For those AI an input range and an acquisition cycle are defined in configuration.
4.7.1 Input ranges
The different input ranges are:
For voltage inputs (AIU201 only):± 10 V, ± 5 V, ± 2.5 V, ± 1.25 V
For current inputs: 0 - 1 mA, ± 1 mA, 0 - 5 mA, ± 5 mA, 0 - 10 mA, ± 10 mA, 4 - 20 mA,
0 - 20 mA, ± 20 mA
The saturation value depends on the selected range.
4.7.2 Acquisition cycle

The analogue inputs are acquired on a periodical basis (short or long cycle, defined in
configuration).
4.8 Digital outputs (DO)

Digital outputs are used to apply a switching voltage to an external device in order to execute
single or dual, transient or permanent commands. The applied voltage is fed from an
external power supply. The external voltage is connected to the controlled device by a relay,
thus isolating the logic part of the board from the external power supply.
Two types of Digital Outputs are available into MiCOM C264/C264C:
• CCU200 boards for controls (8 DIs+4 normal open DOs), this board allows double
pole switching controls.
• DOU200 boards for alarms (8 normal open DOs + 2 normal open/normal close DOs).
4.9 Digital Setpoints

Digital setpoints are digital values coded on multiple outputs. Each output represents a bit of
the value. Digital setpoints are used to send instruction values to the process or to auxiliary
devices. The maximum number of outputs that can be used for a digital setpoint is 48.
Digital Setpoints are processed on the same boards as the Digital Outputs. The Digital
Outputs characteristics described above apply on Digital Setpoints. Nevertheless, only
standard DO boards with single pole N/O relays can be used.
4.9.1 Encoding
The following codes are allowed:
CODE Number of bits ( max. 48) Range of value

BCD 4 ( 1 BCD decade) 0 to 9
8 ( 2 BCD decades) 0 to 99
32 ( 8 BCD decades) 0 to 99,999,999
48 ( 12 BCD decades) 0 to 999,999,999,999
Binary n 0 to 2n-1
Gray n 0 to 2n-1
Decimal 16 0 to 69
( 1 bit among 6 for the tens,
1 among 10 for the units)
32 0 to 4999
(1 bit among 4 for the thousands,
48 0 to 299,999
(bit among 2 for the tens of thousands,
1 bit among 9 for the tens of thousands,
1 bit among 9 for the thousands,
1 among N n 0 to n
Moreover a supplementary bit can be used for the sign ( 0 indicates a positive value, 1
indicates a negative value).
4.9.2 Read Inhibit
A dedicated binary output can be used to allow or forbid the reading of the value by the
external device.
There is one (or none) Read Inhibit (RI) output per value.
If the RI output is a logical one (external polarity applied), the reading is allowed.
The procedure used to output a value with a RI output is:
• Reset the RI output to a logical 0: read forbidden.
• Wait for N ms
• Output the value
• Wait for N ms
• Set the RI output to a logical 1: reading is allowed.
The 0 to 1 transition on the RI output can be used by the external device as a trigger,
indicating that a new value is available.
5. DATA PROCESSING
MiCOM C264/C264C treatment entries can be Binary Inputs or Analogue Inputs. They are
issued from
• IOs boards
• MiCOM C264/C264C internal information (System Input, automation)
• Communication acquisition (IED or other computer from LBUS or SBUS)
5.1 Binary Input processing
5.1.1 Binary Input definition

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

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

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

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

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

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

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

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

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

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

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

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

0 0 Below motion delay, the state is valid motion. For
REPORT no transmission of the transitory state.
After Motion filtering, state is invalid JAMMED
0 1 OPEN
1 0 CLOSE
1 1 UNDEFINED after a permanent filtering
Preliminary treatment (filtering) for some DPs is applied to filter the MOTION state during a
certain period of time. This avoids the transmission of this (normally) transient state.
This treatment is called motion filtering.
• Mode 1: the valid state (OPEN or CLOSE) is stamped with the time of the beginning of
the MOTION state
• Mode 2: the valid state (OPEN or CLOSE) is stamped with the time of this valid
transition
This time stamping can be superseded if a persistence filtering applies.
If the MOTION state is confirmed, it is always stamped with the time of the beginning of the
MOTION state. Furthermore, the BI takes the state JAMMED (in case of confirmed
MOTION00 state) or UNDEFINED (in case of confirmed MOTION11 state). In this case, the
following valid state (OPEN or CLOSE) is always time-stamped with the time of this valid
transition (depending on the persistence filtering feature).
5.1.3.1 Motion filtering

For some DP, the MOTION state must be filtered during a certain period of time in order to
avoid the transmission of this (normally) transient state.
Two time-out values can be associated with each DP:
• T00: delay for the MOTION00 state filtering
• T11: delay for the MOTION11 state filtering

applied.
• Mode 1: the valid state (OPEN or CLOSE) is stamped with the time of the beginning of
the MOTION state
• Mode 2: the valid state (OPEN or CLOSE) is stamped with the time of this valid
transition
This time stamping can be superseded if a persistence filtering applies.
If the MOTION state is confirmed, it is always stamped with the time of the beginning of the
MOTION state. Furthermore, the BI takes the state JAMMED (in case of confirmed
MOTION00 state) or UNDEFINED (in case of confirmed MOTION11 state). In this case, the
following valid state (OPEN or CLOSE) is always time-stamped with the time of this valid
transition (depending on the persistence filtering feature).
OPEN
T00 T00 T11 T11
CLOSE
t0 t1 t2 t3 t4 t5 t6 t7 t8
• t0 : MOTION00 transition
• t1 : MOTION00 state not confirmed, CLOSE state time-stamped t0 if mode 1, t1 if mode 2
(if no persistence filtering applies)
• t3 : MOTION00 state confirmed, state JAMMED time-stamped t2
• t4 : OPEN transition, time-stamped t4 whatever was the mode (if no persistence filtering applies)
• t6 : MOTION11 state not confirmed
• t8 : MOTION11 state confirmed, state UNDEFINED time-stamped t8 C0311ENa
FIGURE 18: MOTION FILTERING

5.1.3.2 DP persistence filtering

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

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

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

The DP resulting states are:
States (report) Goose

JAMMED 11
MOTION 00
OPEN 10
CLOSE 01
UNDEFINED 11
TOGGLING 11
SELFCHECK FAULTY 11
UNKNOWN 11
SUPPRESSED 11
FORCED JAMMED 11
FORCED OPEN 10
FORCED CLOSED 01
SUBSTITUTED JAMMED 11
SUBSTITUTED OPEN 10
SUBSTITUTED CLOSED 01
5.1.3.3 DI/DO association for DP

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

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

5.1.4.1 Multiple Point resulting states

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

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

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

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

acquisition through DI or through serial communication) but which must be managed
by the MiCOM computer: the status of these information are saved in non-volatile
memory.
A SI is of SP, DP or MP type and can belong to any type of group.
The processing of a SI is given in the SP / DP / MP data flow.
5.1.6 IED inputs

These inputs are acquired from IEDs or protective relays via serial links.
If they are not time tagged by the IED, they are by the computer at the time of reception. This
must be configured for each IED.
An IED input is of SP, DP or MP type.
Double inputs can be processed in IEDs. If they are not, the computer must receive each
individual input and perform the DP processing. This must be configured for each IED.
The processing of an IED input is given in the SP / DP / MP data flow.
5.1.7 Group processing
A group is a logical OR, AND, NOR or NAND combination of Binary Inputs (BIs) or groups.
A group component can be a SP, DP (direct or via IED), SI, Group. A component can belong
to several groups.
A group is processed as a SP. It is time stamped with the date / time of the last data-point
which has modified the group status.
A group is calculated with filtered BIs (persistent filtering or motion filtering if configured).
Other computer BIs coming from reports.
The binary inputs states are taken into account as follows:
Single Point Status treated in a group as

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

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

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

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

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

acquisition Scaling
management suppression
from digital Threshold

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

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

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

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

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

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

5.2.4 Thresholds detection
Six thresholds can be defined for each measurement: 3 upper thresholds and 3 lower
thresholds.
A hysteresis value configured on a per measurement basis is associated to the threshold
management. This value is a percentage of the full scale value of the measurement.
upper
HYST
t3 t4
t1 t2
HYST
lower
t1 : upper threshold violation

t2 : end of upper threshold violation
t3 : lower threshold violation
t4 : end of lower threshold violation C0313ENa
FIGURE 24: THRESHOLDS DETECTION

5.2.5 Manual suppression

A measurement can be assigned to the SUPPRESSED state by an order issued from an
operator. No subsequent change of value or state on a "SUPPRESSED" measurement can
trigger any action e.g. display, alarm, transmission. The measurement takes the
SUPPRESSED state. When the operator "un-suppresses" the measurement, this one takes
its actual state.
5.2.6 Substitution
The value of a measurement can be substituted by an operator (state “SUBSTITUTED”,
value defined by the operator). The measurement stays in this state until he un-substitutes it.
When a measurement is substituted, no change of value nor state is transmitted, and
computations are made with the substituted state. When the measurement is un-substituted,
the actual state and value are transmitted to higher control levels and subsequent changes
of state and value are transmitted again.
5.2.7 Forcing an invalid measurement

When a measurement is invalid (i.e. SELFCHECK FAULTY, UNDEFINED, OPEN CIRCUIT,
SATURATED or UNKNOWN), it can be manually forced by a user (state “FORCED”, value
defined by the operator). This feature is similar to the substitution but the information is
automatically updated when valid information is available again.
The forcing could also be automatic: in this case, the invalid information takes automatically
the FORCED state and the value defined in configuration.
The forced/substituted data are saved in SRAM (kept for minimum 48h without C264 power
supply).
The modified states are not reset by a C264 reboot.
A database switch (or evolution) reset the forced/substituted data.
5.2.8 Measurement resulting states
The Measurement resulting states, following the various filters, which can be applied, are:
State Meaning
VALID Not in one of the following states
SELFCHECK FAULTY AI, DI board fault
SUBSTITUTED Operator action set MV value as valid state
FORCED Automatic valid state and configured value when AI is invalid
SUPPRESSED Operator set MV in this invalid state
UNKNOWN MV is acquired via a transmission link, and the link is
disconnected
SATURATED MV is beyond its nominal input range
UNDEFINED MV is Digital Measurement with invalid coding or computation on
analogue leads to error
OPEN CIRCUIT MV is DC 4-20 mA with input value under 4mA
OVERSHOOT[1..3] One of the 3 overshoot values has been crossed
UNDERSHOOT[1..3] One of the 3 undershoot values has been crossed
5.2.9 Transmission
The measurement value and state are transmitted on a client-server basis on the Ethernet
IEC-61850 network, using two modes:
• Report based mode: the measurement is transmitted to the subscribers with its
value, its status, its time stamping and the reason for change.
• GOOSE based mode (only on IEC61850 network): the measurement is transmitted

in multicast to the configured receivers.
During a loss of communication between a client and a server, all server measurements are
set to UNKNOWN on the client.
The measurement information transmitted in a report are:
• the real value (i.e. after scaling)
• the resulting state (mapped on the quality field on IEC-61850)
• the time stamping (in GMT time) and time quality
• the reason for change, which could be one of the below values:
− change of quality (set if the measurement resulting state has changed)
− cyclic change (set if the measurement value has changed, without modification of
the resulting state)
A Measurement value can be transmitted periodically or upon variation (% of nominal), and
anyway on state change.
5.2.9.1 Periodic Transmission

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

Each measurement is associated to one of the two periods. All measurements of one period
are transmitted at the beginning of each cycle.
All measurements values transmitted within one transmission cycle are the latest acquired
values.
5.2.9.2 Transmission upon variation
Measurements can be transmitted upon variation: a value is sent if the acquired value (Vacq)
is different from more than a specified amount ∆V from the previously transmitted value (Vt) (
i.e |Vacq-Vt| > ∆V).
∆V is computed either from the last transmitted value (mode 1) or from the full scale value
(mode 2):
∆V = (p/1000) * |Vt| where p is a value in the range 0 .. 255 and Vt is the last transmitted
value.
or
∆V = (p/1000) * |Vmax| where p is a value in the range 0 .. 255 and Vmax is the full scale
value.
5.2.9.3 Transmission upon trigger

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

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

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

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

1
3
Im( direct ) = × (Im( A) + Im(B ) + Im(C ) )
1
3
Check synchronising
The check synchronising mode is the default synchronising mode.
It is performed if the ∆F value is less than a user configured value (generally less than 0.1
Hz). If so, the CT-VT module computes ∆V and ∆ϕ. If these values are less than a user
configured threshold, the system closes the breaker. In the other hand, the CT-VT module
prevents the closure of the breaker if the system synchronising has not been activated and
one of the previous conditions is not achieved.
System synchronising
In opposite to the check synchronising, the system synchronising mode is entered when a
close control is received by the CT-VT module and if the ∆F value is under a user defined
threshold.
The system synchronising should have a predictive role. This means that the CT-VT module
should calculate the time to wait before the authorisation of the closure by taking into
account the complete command line, including the mechanical characteristics of the circuit
breaker. This time should be user configured.
Notice that CT-VT module should exit the system synchronising mode after a user defined
tmporisation.
Synchrocheck calculation
Whatever the synchronising mode ∆V, ∆ϕ and ∆F have to be calculated. These values are
available through the measurement module.
∆V is calculated through the RMS value of the voltages on both bus bar and line side.
The value of ∆F is assumed to be constant across the period. As a result, knowing ∆ϕ

(through measurement), we know when the synchrocheck conditions are achieved (this will
easily include the reaction time of the breaker aso).
time_synchro = 2 * pi *∆F / ∆ϕ
5.2.10.4 Limits and performances

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

5.2.11 Digital Measurement Processing

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

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

5.3 Tap Position Indication processing

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

A TPI can be suppressed by an order issued from an operator. No subsequent change of
value or state on a suppressed TPI can trigger any action e.g. display, alarm, transmission.
The TPI takes the “SUPPRESSED” state. When the operator unsuppresses the TPI, this one
takes its actual state.
5.3.4 Substitution
The value of a TPI can be substitute by an operator (state “SUBSTITUTED”, value defined
by the operator). The TPI stays in this state until he unsubstitutes it.
When a TPI is substituted, no changesof value nor state is transmitted, and computations,
for instance groupings, are made with the substituted state. When the TPI is unsubstituted,
the actual state and value are transmitted to higher control levels and subsequent changes
of state and value are transmitted again.
5.3.5 Forcing an invalid TPI
When a TPI is invalid (i.e. SELFCHECK FAULTY, UNDEFINED or UNKNOWN), it can be
manually forced by a user (state “FORCED”, value defined by the operator). This feature is
similar to the substitution but the information is automatically updated when valid information
is available again.
The automatic forcing function is not provided for TPI.
5.3.6 TPI resulting states

The state of a tap position can be:
State Comment
VALID not in one of the below states
SELFCHECK FAULTY Due to an AI board fault or a DI board fault
SUBSTITUTED See § 4.4
FORCED
SUPPRESSED
UNKNOWN If the tap position is acquired via a transmission link, the
information is unknown when the link is disconnected.
UNDEFINED Due to a wrong encoding for a digital acquisition, or a saturation,
an open-circuit or an out-of-range value for an analogue
acquisition
OVERSHOOT[1..3] It exists 3 “Overshoot” states, one for each upper threshold
violation. Only one could be set at one time
UNDERSHOOT[1..3] It exists 3 “Undershoot” states, one for each lower threshold
violation. Only one could be set at one time
5.3.7 Transmission
The TPI are transmitted on a client-server basis on the IEC-61850 network using the report
mechanism.
During a loss of communication between a client and a server, all server TPI are set to
UNKNOWN on the client.
The TPI is transmitted as soon as a value change or a status change is detected. The TPI
information transmitted in a report are:
• the TPI value
• the resulting state (mapped on the quality field on IEC 61850)
• the reason for change, which could be one of the below values:
− change of data (set if the value has changed)
− change of quality (set if the quality has changed)
− change due to control (set if the state or quality change is due to a control)
The TPI information transmitted in a GOOSE is the same than in a report, except for the
"reason for change" and the time-stamping.
5.4 Accumulator Input Processing
The accumulator stores its current value in a static memory volatile memory (secured with a
capacitor, >48h autonomy). At configured sample an accumulated value is extracted for
inner computation and transmission (Common Data Class BCR on IEC 61850).
Digital Inputs are used to count pulses. There is Single counter (SCT) based on one DI and
Double Counter (DCT) based on two DIs which count complementary states.
At processing level special persistent and complementary filters eliminate non-stable pulses.
The integer counter (also transmitted) can be scaled (among of energy of valid pulse).
5.5 Energy counting

The energy counting function aims to calculate exported and imported active energy
(in kWh) and exported and imported reactive energy (in kVarh) from active and reactive
power issued from CT/VT calculation, digital, analogue boards measurements or IEDs
measurements..
Calculation of the energy is done periodically. The period is defined either by an external
pulsed applied on a digital input, or by the internal clock of the computer. The choice of the
origin of the periodic signal is defined during the configuration phase on a per computer
basis.
Whatever is the origin of an integrated measurement, the integration is done after scaling
with a step of one second.
The integration method used is the trapezium one:
E = ∑ Ei
⎛ ( M i + M i −1 ) (ti − ti −1 ) ⎞
Ei = S f * ⎜ * ⎟
⎝ 2 3600 ⎠
With:
E = total Energy counter value (continuous register)
Ei = Integration result at time ti
Sf = Scaling Factor (defined during the configuration phase)
Mi = absolute value of the Measurement at time ti
ti – ti-1 = 1 second
For a given measurement, the integration can be done only after receiving two consecutive
valid values with the same sign of the measurement. The integration result (Ei) is added to
the associated export or import counter according to the sign of the measurement.
The integration is stopped as soon as the power measurement becomes invalid or changes
of sign. The integration is restarted as soon as two consecutive valid measurement values
with the same sign are received.
Current values of energy counters are stored in secured memory ( 48h autonomy when
power supply is off). Current values of energy counters can be modified by an operator.
Values of energy counters are transmitted on a client-server basis on the IEC-61850 network
using mechanism through the LN MMTR.
During a loss of communication between a client and a server, all server energy counters are
set to UNKNOWN state on the client.
WARNING: THE ENERGY COUNTER VALUES ARE NOT TO BE USED FOR BILLING
APPLICATION.
5.6 Basic Data Manipulation

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

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

5.6.3 Controls management from PSL
A control issued from a PSL (or an DI/DO association) will be accepted even if an other
control is already on-going on the same output. In this case, the previous control is stopped
and the new control is launched (except if the new one is the same order than the previous
one: in this case, the new control is refused).
It exists 3 cases to manage (PSL means PSL or DI/DO association – Operator means from
IEC61850 / ISAGRAF / local HMI):
• Control 1 from PSL and Control 2 from Operator
• Control 1 from Operator and Control 2 from PSL
• Control 1 from PSL and Control 2 from PSL

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

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

PSL Operator Control 2 ignored Ack “Control in progress”
Operator PSL Control 2 ignored n/a (no ack managed in PSL)
PSL PSL Control 2 ignored n/a (no ack managed in PSL)
Operator Operator Control 2 ignored Ack “Control in progress”
6. CONTROL SEQUENCES
6.1 Generic description

A Control Sequence is a basic built-in function on a module (switch, relay, and function). It
receives control order, sending back acknowledgement. After checks, control sequence
sends control (protocol or DO), and check correct execution with feed back from protocol or
from DI.
6.1.1 Generalities
The MiCOM C264/C264C allows the following functions:
• Control of switching devices (circuit breaker, switch, …)
• Control of transformers
• Control of secondary devices
• Locking of switching devices
• Control of IEDs
• Control of automatisms
The following control types are allowed:
• Select control request
• Execute control request
• Unselect control request
• Cancel control request

Upon reception of one of these requests, the computer behaviour is different according to:
• The configuration of the device control,
• The type of the device,
• The computer operating mode.

6.1.1.1 Device control configuration
By configuration, at SCE level, a control may be executed in one of the following modes:
• “Direct Execute” mode: usually for ancillary devices a control may be performed
directly without the selection phase.
• “Select Before Operate once” mode” (SBO once): usually for circuits breakers and
disconnectors. The device must be selected before allowing the execution. In that
case the device is managed in two phases: selection and execution. Device
unselection is done automatically by the computer.
• “Select Before Operate many” (SBO many): usually for transformers. The device
must be selected before execute one or more controls before reaching the expected
position (low/raise). In that case the device is managed in three phases: selection,
execution and unselection. The execution phase is repeated for every new control. To
end the controls sequence, the initiator of the request must send an “unselection”
request.
6.1.1.2 Types of devices

Every control sequence may be different according to the type of the device to control. The
complexity of the control sequence may be more or less important depending on the device:
• Synchronised or not synchronised circuit breakers, disconnectors and earthing
switches: They are managed in “Direct execute” mode or “SBO once” mode with
optional hardware selection of the device in SBO mode.
• Transformers: They are managed in the three modes: “Direct Execute”, “SBO
once” and “SBO many” mode with optional hardware selection of the device in SBO
mode.
• Ancillary devices: they are usually managed in “Direct Execute” mode but can be
managed also in “SBO once” mode.
• System Controls: System outputs are used to activate or inactivate automatic

functions on the computer (e.g. Auto-recloser ON/OFF), change operating modes etc.
• Controls via Setpoints: are managed in “Direct Execute” mode and in “SBO once”
mode.
6.1.2 Control sequence phase management

According to the configuration of the device control, a control sequence is performed in one,
two, or three phases. Each phase of a control sequence (selection, execution and
unselection) may have a normal or abnormal termination and positive or negative
acknowledgement is sent to the IEC-61850 clients subscribed during the configuration
process.
• one phase – “Direct Execute” mode:

1. execution phase: If the execution phase ends normally the computer generates
a positive acknowledgement and the control sequence ends. In case of abnormal
termination, the control sequence is aborted and the computer generates a
negative acknowledgement. The hardware selection of the device in “Direct
Execute” mode is not allowed.
• two phases – “SBO once” mode:

1. selection phase: In the selection phase for a normal termination the computer
generates a positive acknowledgement and proceeds to the next phase of the
sequence (execution phase).
a positive acknowledgement and the control sequence ends. In case of abnormal
termination, the control sequence is aborted and the computer generates a
negative acknowledgement.
• three phases – “SBO many” mode:

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

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

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

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

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

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

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

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

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

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

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

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

After the end of this delay if the execution or the cancel request is not sent, the device is
automatically unselected and a negative acknowledgement is sent. The selection delay is
defined during the configuration step.
Note that only one selection is allowed at a time for a device. When a device is already
selected any other selection is not taken into account (none acknowledgement is sent)
whichever of the initiator.
The following diagram shows the selection phase of a device configured in SBO once mode.
Unselected
device
Selection request
no
Device selectable ?
yes
Device Already
selected
Perform Selection
no checks
All checks OK
Device selection
no
Device selection OK
Set “device selected”
send positive
acknowledge
Selection Time-out
launching
Wait new request

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

6.1.4.2 Execution phase in “SBO once” mode

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

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

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

6.1.5 SBO many mode

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

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

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

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

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

6.1.5.3 Unselection phase in SBO many mode

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

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

Checks performed during the selection phase are:
• Inter-control delay
• Computer mode
• Substation and bay mode states
• Interlock and topological interlocking states
• Automation running control
• Device selectable
• Locked device state
• Status of the device
• Uniqueness
In case of fail, the initiator of the request may bypass the following checks:
• Uniqueness
Next diagram schematises controls and bypass according the description of the device.
Selection checks for SBO device Unselected device
Inter-control delay Not configured

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

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

6.1.6.1 Inter-control delay

A user-selectable delay can be defined in which a new order to the same device is forbidden.
If this delay is configured and not expired since the last order the request is refused with
6.1.6.2 Computer mode

Control requests are accepted or not depending on the operating mode of the computer.
• Maintenance mode: control requests are not accepted if the computer is in
maintenance mode except system controls concerning control mode or database
management.
• Faulty mode: no control is accepted when the computer is in this mode.
• Changing mode:
− From “operational” mode to “test” mode: the specific control “test” mode is
refused if at least one control is in progress.
− From “test” mode to “operational” mode: the specific control “test” mode is
refused if at least one control is in progress.
− From “operational” mode to “maintenance” mode: all device controls in

progress are aborted and no acknowledgement is sent.
6.1.6.3 Substation and bay mode control

A device control may be dependant or not to the substation mode and bay mode. For every
device control the configuration gives the dependency or not to the following modes:
• Substation mode dependency (local/remote)
• SBMC mode dependency (bay in maintenance or not)
• Bay mode dependency (local/remote)

Bay mode is checked by the computer managing the device if the bay mode dependency is
configured for this device.
Substation and SBMC modes are checked by the computer having slave protocols and only
for controls coming from SCADA and if substation mode dependency is configured for this
device.
If the request is refused the selection sequence is aborted with negative acknowledgement.
6.1.6.4 Interlock control

The configuration process allows to assign or not a logical equation to each order (close and
open) of the device. If configured by the user, its state (true/false) may affect the control
sequence. If is false, the selection is refused, excepted if bypass is set.
In case of fail the sequence is aborted with a negative acknowledgement.
6.1.6.5 Automation running control

Each device may be locked by the presence of an input information (digital input, IED input
etc) assigned during configuration. A “system input information” giving automatism state
(active/inactive) can be used to prevent manually control execution in case an automatism is
active for device monitoring (e.g. ATCC).
In this case the sequence is aborted with a negative acknowledgement, except if the user
asks to bypass this check.
6.1.6.6 Device selectable

A device is selectable if during configuration step its control is described to be managed in
“SBO once” or “SBO many” mode and is not already selected. Otherwise the selection
request is refused with negative acknowledgement.
6.1.6.7 Locked device control

The user may lock a device in order to avoid any wrong move. If the selection concerns a
locked device the request is refused, except if the user force to bypass this control in the
selection request.
In case the device is locked the sequence is aborted with a negative acknowledgement.
6.1.6.8 Current status of the device

The status check of the device is optional. It is given by a binary input or computed using
more than one binary input (case of circuit breakers). Its behaviour can be chosen ( during
the configuration step) among one of the four following cases:It is given by a binary input or
computed using more than one binary input (case of circuit breakers).
• the request is accepted whatever the status of the device ( no check)
• the request is accepted only if the device is in the opposite state and valid
• the request is accepted only if the device is in the opposite state, jammed or undefined
• the request is refused only if the device is in the same state and valid
− In any case, if the request is refused, a negative acknowledgement is sent back
6.1.6.9 Uniqueness
It is possible by configuration to prevent to have more than one control at a time.
• For the whole substation
• Inside a bay
The following figure describes the algorithm used between computers.
A
Uniqueness does not be checked for
this device or uniqueness is bypass
Uniqueness must be checked for this
device and there is no bypass
→ Goose is sent to other bays

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

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

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

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

C0322ENa
FIGURE 33: CHECK OF UNIQUENESS

If a device is under control and another control is sent on this device, the second one is
ignored.
In case of uniqueness of the command at least to one of these levels the selection is
refused, with negative acknowledgement. The user may bypass this control during selection
request.
6.1.7 Selection behaviour

In SBO once mode and SBO many mode, the configuration process allows to describe
optionally, a device selection to control the device.
The following configurations must be considered:
• Configuration 1: device with a control for selection and its associated selection
position information.
• Configuration 2: device with a control for selection (without input selection

information).
Whatever the request control (select open/select close, select raise/select low) the selection
of the device is performed as follow:
• Configuration 1:
The computer
1. verifies the selection position information, it must be open: if it is close, it is an
abnormal situation, the selection sequence is stopped with a negative
acknowledgement.
2. sends a “close” order of the selection control (via I/O boards or IED) and waits the
selection position information in a given delay (by configuration).
If the selection control has been normally executed, and the selection position
information of the device become “set” in the given delay, the selection sequence
ends sending a positive acknowledgement. The computer starts its execution
sequence. In case of fail of the execution of the selection control or if the selection
position information remains open in the given delay the selection sequence ends
abnormally sending a negative acknowledgement.
• Configuration 2:
For this configuration, in which only the output control of the selection is configured,
the computer: sends a “close” order of the selection control (via I/O boards or IED). If
the selection control has been normally executed, the selection sequence ends by
sending a positive acknowledgement and the computer start its execution sequence.
In case of fail of the execution of the selection control, the sequence ends abnormally
by sending a negative acknowledgement.
6.1.8 Generic execution checks

During the execution phase, whatever the execution mode (SBO once, SBO many or Direct
Execute) the computer, before proceeding to the execution of the request, performs the
following checks:
• Inter-control delay
• Computer mode
• Device selectable (SBO mode only)
• Current status of the device
• Uniqueness
Execution checks and bypasses are identical to those of the selection phase. Moreover, in
case of ”SBO once” mode or ”SBO many” mode the computer verifies that the device was
previously selected.
The checks of the execution phase in “SBO many” mode are identical as above but they
are repeated for every execution request (low/raise).
In “Direct Execute” mode the device selection is not verified because it is not allowed.
6.1.9 Execution behaviour

On this stage the control request is executed via:
• I/O boards
• IED communication
• System supervisor of the computer for system outputs

The execution via I/O boards is performed only if the computer is in “operational” mode. If
the computer is in “test” mode, the output relay is not set. In this case the computer
simulates a positive acknowledgement of hardware execution. It allows to perform control
sequence safety in order to test Automatisms configuration, control sequence configuration
etc. Controls to IEDs are sent if the computer is in “operational” mode or “test” mode.
6.1.9.1 Execution via I/O boards

According to the devices features the execution of the control via I/O boards may be
performed using:
• Single Points Control
• Double Control Points
• Digital Setpoints
Single Point Control and Double Point Control
However, the execution control sequence depends on the activation mode of the xPC. By
configuration, this activation mode of SPC and DPC may be “transient”, “permanent” or
“permanent until feedbackuntil feedback”.
• Transient: the contact is closed and then re-opened automatically after a delay
(defined during the configuration of the xPC). For a DPC, configuration gives two
delays need to be configured, one for open and one for close.
• Permanent: For this type of output control, the contact is held in the requested
position state until the a reverse order is received.
• Permanent until feedback: The contact is held in the requested position state until
confirmation of the position of the device or after timeout awaiting the new position of
the device. In this case, the input information of the device status must be configured.
Digital Setpoints
A control sequence via Digital Setpoints has particular treatments during the control request
6.1.9.2 Execution via IED communication

When an execution request is performed via IED communication, the requested order is
converted to a message to be sent to the intelligent devices, according the communication
protocol.
6.1.9.3 System controls execution

For systems outputs the computer activate/deactivate the associated function (ATCC,
computer mode, etc) and if a specific system input (SPS or DPS) is configured for this
control, it takes the requested state and it stored in non-volatile memory.
6.1.10 Controls time sequencing

Time sequencing of control is dependent of its configuration:
• Control mode: Direct Execute, SBO once, SBO many
• Device features: selection control wired/not wired, selection position wired/not wired,
device position wired/not wired etc.
• Output control type: permanent , pulse
• Destination: I/O board, IED
• Time-out delays: selection phase time-out, selection Feedback delays, open/close

Feedback delay etc.
6.1.10.1 Direct execute time sequencing

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

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

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

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

6.2.1 Non synchronised circuit breakers features
The following table gives inputs and outputs circuit breaker’s features controlled by the
computer:
THREE PHASED CIRCUIT BREAKERS ONE PHASED CIRCUIT BREAKERS

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

Circuit breakers devices are managed in “SBO once” mode only. The following paragraph
describes the specific features of synchronised circuit breakers whether are synchronised by
an external or internal synchrocheck module.
6.3.1 Circuit breakers features
THREE PHASED CIRCUIT BREAKERS ONE PHASED CB

OUTPUTS OUTPUTS CB INPUTS CB OUTPUTS OUTPUTS INPUTS ALL
CB TYPE A TYPE B (6) ALL TYPES (6) TYPE A TYPE B TYPES
DEVICE DPC control SPC control SPS/DPS DPC control SPC/DPC SPS/DPS
CONTROL for for open of physical for control for physical
open/close device position of the open/close open phase position of
of device device (1 of device A phase A
SPC control
phase)
SPC/DPC for close of SPC/DPC SPC/DPC SPS/DPS
control for device SPS (optional) control for control for physical
close with phase not close with open phase position of
SPC/DPC
synchrocheck together synchrocheck B phase B
control for
(5) information (5)
close with SPC/DPC SPS/DPS
synchrocheck system DPS control for physical
(5) optional): the open phase position of
feedback of C phase C
the control (1)
SPC/DPC system
control for SPS/DPS
close of phase not
device together
information (2)
SPC control
for close with system DPS:
synchrocheck the feedback
of the control
(3)
DEVICE SPC SPC (optional) SPS (optional) SPC SPC SPS (optional)
SELECTION (optional) control of device (optional) (optional) device
control of device selection control of control of selection
device selection position device device position
selection information selection selection information
SYNCHROCHEC SPC/DPC SPC/DPC SPS/DPS SPC/DPC SPC/DPC SPS/DPS
K SET ON/SET (optional) (optional) (optional) (optional) (optional) /DPS(optional)
OFF (4) control of control of ON/OFF control of control of ON/OFF
ON/OFF ON/OFF synchrocheck ON/OFF ON/OFF synchrocheck
synchrocheck synchrocheck information synchrocheck synchrocheck information
(1) The computed double signal is equal to the physical status if the phase not together
(2) The computed “phases not together” is equal to “false” if all phases are in the same
(3) The computed signal is equal to the phase A status if the phase not together status is
(4) Wired SPC and SPS for external synchrocheck and system SPC and SPS for internal
synchrocheck. If is not configured the external synchrocheck module or the
synchrocheck automatism is considered always “set on”. DPC and DPS are used only
for manual synchrocheck.
(5) For external synchrocheck only.
“Open” control sequence of synchronised circuit breakers remains identical to the non-
synchronised circuit breakers.
“Close” control sequence is different according to the configuration the synchrocheck type:
• External synchrocheck: The closure of the device is assumed by an external
synchrocheck module
• Internal synchrocheck: The closure of the device is assumed by an internal

synchrocheck automatism
A Close control sequence can be configured with:
• Manual set on of the external synchrocheck module or internal synchrocheck

automatism
• Automatic set on of the external synchrocheck module or internal synchrocheck

automatism
Furthermore, waiting closes the CB by the external module the initiator of the request may:
• Cancel the request
• Close the device by forcing request
6.3.2 Circuit breakers with external synchrocheck
6.3.2.1 Close CB by external synchrocheck with automatic set on

The following scheme shows a “close” control for a device in which the external
synchrocheck module is set on automatically by the computer.
SPC close with SPC Select device

synchrocheck C26X
CIRCUIT
SPC/DPC ON/OFF BREAKER
(1) synchrocheck Synchro
(2) Check
(3) Module
OI SPC Close with

synchrocheck
or SPC/DPC
MES/MHS
GATE synchrocheck
WAY
DPC open/Close
device
select close
Execute close (x) sequences order
force close
C0328ENa
FIGURE 39: CLOSE CB BY EXTERNAL SYNCHROCHECK WITH AUTOMATIC SET ON

The “close” control sequence performed on the MiCOM C264/C264C is done as follows:
Selection phase:
1. Set on synchrocheck module (if the control is configured)
2. Verify synchrocheck on/off information associated to the output (if is configured)
3. Close device selection output to select the device (if is configured)
4. Verify selection device input information associated to the output (if is configured)
5. Wait the execution request or timeout selection
In case of fail to one of these operations the controls sequence is stopped with a negative
acknowledgement
Execution phase:
6. Close the device using synchrocheck output control
7. Verify the device position become close in the given delay.
8. Set off synchrocheck module if it previously set on
9. Deselect the device if it previously selected
The following chronogram shows a successful control sequence ”close with synchrocheck”.
SPC ON/OFFt Sync
SPS ON/OFF Sync
SPC select
SPS select
SPC sync close
DPC open/close
device
DPS open
close
Feedback Feedback Feedback for DO

Delay Delay Selection timeOut sync close
0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5
1 selection request 3 execution request 5 End of control

C0329ENa
FIGURE 40: CHRONOGRAM OF A SUCCESSFUL "CLOSE WITH SYNCHROCHECK"

The following chronogram shows an abnormal termination of control sequence ”close with
synchrocheck”. The device has not taken the expected position “close” in the given delay.
The control sequence is aborted with negative acknowledgement, deselecting previously
synchrocheck and device.
SPC ON/OFF Sync
SPS ON/OFF Sync
SPC select
SPS select
SPC sync close
DPC open/close
device
DPS open
close

0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5

C0330ENa
FIGURE 41: ABNORMAL TERMINATION OF "CLOSE WITH SYNCHROCHECK"

6.3.2.2 Close CB by external synchrocheck with manual set on

By configuration the “close” control of the device may be done in two or three control
sequences:
Two sequences:
1. a “Direct Execute” sequence to put in service the external synchrocheck module
2. a SBO once sequence to close the CB by the synchrocheck module and put out of
service the synchrocheck module
Three sequences:
1. a “Direct Execute” sequence to put in service the external synchrocheck module
2. a SBO once sequence to close the CB by the synchrocheck module
3. a “direct execute” sequence to put out service the external synchrocheck module
The following scheme shows a close control request in which the external synchrocheck
module is managed manually from the OI or gateway.
DPC open/close
device SPC Select device
C26X
CIRCUIT
(2) SPC/DPC ON/OFF BREAKER
(3) synchrocheck
(4) Synchro
Check
(1)
Module
OI SPC/DPC “SET SPC/DPC Close
or ON” synchrocheck with synchrocheck
GATE
WAY
(5)
SPC/DPC “SET
OFF”synchrocheck
(optional)
DPC open/Close
device
Direct execute The external synchrocheck module is set off automatically at the
end of the SBO sequence (if it is configured)
select close
Execute close
(x) sequences order
force close
C0331ENa
FIGURE 42: CLOSE CONTROL REQUEST

First sequence (DIRECT EXECUTE): Set on the external synchrocheck module:
1. close “set on/setoff” output control of the synchrocheck module
2. verify that the synchrocheck module is set (if on/off synchrocheck input information is
configured)
In case of fail to one of these operation the sequence ends with a negative
acknowledgement
Second sequence (SBO ONCE): close the device with synchrocheck”
Selection phase:
2. Verify selection device input information associated to the output (if is
configured)
4. In case of fail to one of these operations the controls sequence is stopped with
a negative acknowledgement
Execution phase:
5. Close the device via the “close with synchrocheck” control
6. Verify the device position become close in the given delay
7. Set off the synchrocheck module if is configured to be set off automatically
Third sequence (DIRECT EXECUTE): set off the external synchrocheck module
This sequence takes place only if the setting off of the synchrocheck module is
configured “manual”
1. open “set on/setoff” output control of the synchrocheck module
2. verify that the synchrocheck module is set on (if on/off synchrocheck input
information is configured)
The following chronogram shows a successful control sequence ”close with synchrocheck”
performed in three sequences. In case of automatic “setting off” of the synchrocheck module
the chronogram remain identical. It is performed at the end of the SBO sequence.
SPC ON/OFF Sync
SPS ON/OFF Sync
SPC select
device
SPS select device
SPC sync close
DPC open/close
device
DPS open
close

0-1 s 0-5 s 0-10mn 0-60mn

3
1 2 4 5 6
1 DE request set on 3 selection request : 4 execution request 5 DE request set 6 End of control
synchrocheck close the device off synchrocheck
C0332ENa
FIGURE 43: SUCCESSFUL CLOSE WITH SYNCHROCHECK

NOTE: During SBO sequence after step 5 the initiator of the request may
force the closing of the device.
6.3.2.3 Close synchronised circuit breakers with forcing

The following chronogram shows controls sequence ”close with synchrocheck” with “forcing
close request”. The SBO sequence is performed in the same way whether the synchrocheck
module is set on manually or automatically.
Awaiting the device be closed by the external synchrocheck module, the initiator of the
request force to “close without synchrocheck”
SPC select Sync

(optional)
SPS select Sync

(optional)
SPC select
(optional)
SPS select
(optional)
SPC sync close
Forcing on DPC
close : DPC close
is set
SPS open
close
Feedback Delay Feedback Selection Timeout Feedback for DO sync close Feedback
Delay Delay
0-1 s 0-5 s 0-10mn 0-60mn 0-20s

1 2 3 4 5 6
3 execution request 4 synchrocheck bypass 5 End of control

1 selection request C0333ENa
FIGURE 44: ”CLOSE WITH SYNCHROCHECK” WITH “FORCING CLOSE REQUEST”
6.3.2.4 Cancel Close CB with external synchrocheck

Awaiting close the device (0 to 60 a MN) by the external synchrocheck module, the initiator
of the close request may cancel this one by a “cancel request”.
The following chronogram shows a cancel close request awaiting close the device by the
external synchrocheck module.
SPC select Sync
SPS select Sync
SPC select
SPS select
SPC sync close
DPS open
close
Feedback Feedback FeedBack Delay

Delay Delay Selection timeOut
0-1 s 0-5 s 0-10mn 0-60mn

3 4 5 6
1 2

4 Operator « CANCEL »
C0334ENa
FIGURE 45: CANCEL CLOSE REQUEST

6.3.3 Circuit breakers with internal synchrocheck

On this configuration synchrocheck is assumed by an internal computer automatism, which
proceeds to the synchrocheck voltage calculations and gives or not the authorisation to close
the device.
The controls sequence remains similar with the external synchrocheck instead of the setting
on/off of the synchrocheck and close with synchrocheck output control which are not exist on
this configuration
6.3.3.1 Close CB with internal synchrocheck with automatic set on
The following sequence describes a “close” request of circuit breaker with internal
synchrocheck in “SBO once” mode. Synchrocheck automatism is set on automatically.
In “Direct Execute” mode the processing remain similar without selection of the device.
SPC/DPC system
ON/OFF fonction
synchorcheck
SPC/DPC close
with synchrocheck SPC Select device
C26X
CIRCUIT
(1) BREAKER
(2) Fonction
(3) Synchro
Check
OI
or SPC/ DPC system
GATE Close with
WAY synchorcheck
DPC open/Close
device
select close
(x) sequences order
Execute close
force close
C0335ENa
Selection phase:
2. Verify selection device input information associated to the output (if is configured)
3. Wait the execution close request or timeout selection
In case of fail to one of these operations, the device is deselected and the controls sequence
is aborted with a negative acknowledgement.
Execution phase:
4. Active the associated internal synchrocheck automatism for authorisation to close the
device
5. Wait authorisation to close
Case 1: Synchrocheck automatism respond OK before the time-out of the given delay
• Close the device
• Deselect the device (if it was previously selected)
• Send a positive acknowledgement

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

delay
• Send a negative acknowledgement

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

Case 4: reception of cancel request awaiting synchrocheck response

The following chronogram shows a successful control sequence ”close with internal
synchrocheck”.
SPC select
SPS select
Close/open
Device control
DPS open
close
Feedback Feedback feedback Delay

Delay Delay Selection time-out
0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5
1 selection close request 3 execution request 5 End of control

C0336ENa
The following chronogram shows an abnormal termination of control sequence ”close with
internal synchrocheck”.
SPC select
SPS select
Close/open
Device contro
DPS open
close

0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5
1 selection close request 3 execution request 5 End of control

C0337ENa
6.3.3.2 Close CB with internal synchrocheck with manual set on

The following sequence describes a “close” request of circuit breaker with internal
synchrocheck in “SBO once” mode. Synchrocheck automatism is set on by a separate
direct execute control.
SPC/ DPC Close

with synchrocheck
SPC open/close SPC Select device

device C26X
CIRCUIT
(2) BREAKER
(3) Synchro
(4) Check
Module
OI SPC/ DPC set on

synchrocheck
or (1)
GATE
WAY
(5)
SPC/DPC set off

synchrocheck DPC open/Close
device
Direct execute
The external synchrocheck module is set off automatically at the
select close end of the SBO sequence (if it is configured)
Execute close
(x) sequences order
force close C0338ENa
First sequence (DIRECT EXECUTE): Set on the internal synchrocheck automatism:

1. set on synchrocheck automatism for the device
2. set system input “on/off synchrocheck” (if its is configured)
Second sequence (SBO ONCE): close the device with synchrocheck”
Selection phase:
configured)
4. In case of fail to one of these operations the controls sequence is stopped with
a negative acknowledgement
Execution phase:
5. Ask to the internal automatism to close the device
6. Verify the device position become close in the given delay
7. Set off the synchrocheck automatism if is configured to be set off automatically
Third sequence (DIRECT EXECUTE): set off the internal synchrocheck automatism
This sequence takes place only if the setting off of the synchrocheck automatism is
configured “manual”
1. set off synchrocheck automatism
2. reset system input “on/off synchrocheck” (if its is configured)
NOTE: During SBO sequence after step 5 the initiator of the request may
force the closing of the device.
6.3.3.3 Close CB with internal synchrocheck with forcing

Awaiting authorization from the internal synchrocheck for closing the device, the initiator of
the request may force the closing.
After time-out of the given delay without synchrocheck response
• close the device
• Send a positive acknowledgement

SPC select
SPS select
Close via output

control
DPS open
close

0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5
6
C0339ENa
6.4 Control of disconnectors
6.4.1 Disconnectors features

MiCOM C264/C264C computers manage all types of disconnecting switches such as:
• disconnectors
• earthing switch
• quick break switch
DISCONNECTORS SWITHES
OUTPUTS TYPE A INPUTS ALL TYPES
DEVICE DPC control for open/close of device DPS physical position of the device
CONTROL
DEVICE SPC (optional) control of device SPS (optional) device selection
SELECTION selection position information
6.4.2 Control sequence of disconnectors

The control sequence of disconnectors is identical to control sequence of the non-
synchronised circuit breakers.
6.5 Control of transformers

6.5.1 Transformers features
OUTPUTS INPUTS
TRANFORMER DPC: raise/lower TPI value
CONTROL
SPS (optional) tap change in progress
(TCIP)
TRANSFORMER SPC (optional) transformer SPS (optional) selection position
SELECTION selection information
TRANFORMER Double wound or Auto-wound
TYPE (1)
(1) Transformer type (auto-wound or double-wound) is user selectable.

Double wound (or two winding transformer) is a transformer with galvanic isolation between
primary and secondary coil. Tap Changer (with additional winding) is usually located at HV-
neutral side for economic reasons. Tapping-up (raise order) reduces primary winding and
increase LV tension.
Auto-wound (or auto-transformer or single wound) is a transformer without galvanic
isolation between primary and secondary. Secondary coil follows primary coil, (winding are
serial). Tap Changer (with tap of additional winding) is serial. Increasing tap position (raise
order) acts simultaneously on primary and secondary, it reduces transformer ratio then
voltage at LV side.
6.5.2 Control sequence of transformers

The control of transformer can be performed in the three modes “Direct Execute”, “SBO
once” and “SBO many”.
Additionally of the selection and execution checks described in the previous paragraphs the
following checks are performed:
• A “raise” control is refused if the current tap position value corresponds to the
maximum position of the tap.
• A “lower” control is refused if the current tap position value corresponds to the
minimum position of the tap.
• In case of “go to min”, “go to max” or “go to position x” request, an internal
automatism ( via ISAGRAF) has to be added. This automatism generates the desired
controls sequences in order to reach automatically the expected position. It may
generate “Direct execute”, “SBO once” or “SBO many” sequences according the
configuration of the device
NOTE: If the command of a transformer is configured in SBO many mode, it is
impossible to configure the requests “go to min”, “go to max”
TCIP feature: The TCIP input information (tap change in progress), is used to confirm the
right execution of the low/raise execution. Two delays are given by the configuration for the
TCIP management:
• TCIP apparition delay: The TCIP information must appear before the time-out of this
delay.
• TCIP disappearance delay: The TCIP information must disappear before the time-out
of this delay.
TPI feature: Because the TCIP input information is not always configured, the tap control is
performed using only the Tap Position Indication (TPI) value to verify the right execution of
the request. The TPI value must change in the given delay.
The following examples are given in “SBO many” mode which is the more complex. The
main difference with the “SBO once” mode remains to the possibility to execute many
“raise” or “low” controls before ending the sequence. Moreover, the device is not deselected
automatically but only after an unselect order sent by the initiator of the control request.
6.5.2.1 Control of transformer with TCIP

In this mode, when the TCIP input information is configured, the selection and execution
phase are performed as follows: It is possible by configuration to prevent to have more than
one control at a time.
Selection phase:
1. Close device selection output to select the device (if configured)
configured)
3. Wait the execution request (low/raise) or timeout selection
In case of fail to one of these operations, the device is deselected, the controls
sequence is aborted with a negative acknowledgement.
Execution phase:
4. According the request “raise or lower” and the type of device, execute the
associate control
5. Wait the TCIP information and TIP value to confirm execution. Two cases:
• Case 1: The TCIP information appears and is disappears in the given

delays, the TPI takes the expected value: The computer sends a positive
acknowledgement and waits a new request (execution or unselection).
• Case 2: Timeout awaiting the TCIP appearance or disappearance, or the

TPI value is wrong: The device is deselected (if it was previously
selected), and the sequence is aborted with a negative
acknowledgement.
6. Wait new execution request or unselection request to deselect the device
• In case of new request the computer repeat the steps 4 and 5.
• In case of unselection request the computer deselects the device (if it

was previously selected), and ends the sequence with a positive
acknowledgement
The following chronogram shows a successful sequence with device selection, two “raise”
controls and device unselection
SPC select
(optional)
SPS select
(optional)
DPC raise/lower
OPEN
TPI Value
(1)
raise/lower
CLOSE
SPS TCIP
FeedbackSelection TCIP
Pulse
Delay timeOut disappearance FeedBack
Delay
time Delay Delay
0-5 s 4
0-1 s 0-10mn TCIP apparition 0-1 s 0-1 s

time Delay
11 End of control
1 2 3 0-5 s
4 5 6 7 8 9 10 11
1 selection “raise” request
3 first execution 6 second execution 10 unselect request
request request
C0340ENa
(1) the TPI value must take the expected value at least at the end of TCIP disappearance
The following chronogram shows an abnormal termination of tap changer control sequence
due to absence TCIP confirmation. In this case the device is automatically deselected and
the sequence ends with a negative acknowledgement
SPC select
(optional)
SPS select
(optional)
OPEN
raise/lower
CLOSE
SPS TCIP
TIP value
Feedback Selection FeedBack

Pulse
Delay timeOut Delay
Delay
4
0-5 s
0-1 s 0-10mn 0-1 s
TCIP apparition time
1 2 Delay 5 6
1 selection request “raise” 6 End of control
3 0-5 s
6.5.2.2 Control of transformer without TCIP

In case the TCIP input information is not configured the selection and execution phase are
performed as follows:
Selection phase:
1. Close device selection output to select the device (if configured)
2. Verify selection device input information associated to the output (if configured)
3. Wait the execution close request or timeout selection
In case of fail to one of these operations, the device is deselected, the controls
sequence is aborted with a negative acknowledgement.
Execution phase:
4. According the request “raise or lower” and the type of device, execute the
associate control
5. Wait the TPI information and compare with the previous value. The difference
must confirm the “low” or “raise” execution. Two cases:
• Case 1: The TPI value confirms in the given delay the execution request:
The computer sends a positive acknowledgement and waits a new
request (execution or unselection) from the initiator.
• Case 2: Timeout awaiting the TPI value or unexpected TPI value: The
device is deselected (if it was previously selected), and the sequence is
aborted with a negative acknowledgement.
6. Wait new execution request or unselection request to deselect the device
• In case of new request the computer repeat the steps 4 and 5.

• In case of unselection request the computer deselects the device (if it
was previously selected), and ends the sequence with a positive
acknowledgement.
The following chronogram shows a successful sequence with device selection, a raise
control and device unselection
SPC select
(optional)
SPS select
(optional)
DPC raise/lower
OPEN
raise/lower
CLOSE
TPI
feedback
Feedback Selection Delay
Pulse
Delay time-out
Delay
4
0-5 s
0-1 s 0-10mn 0-1 s
new TPI value
1 2 Delay 6
1 selection “raise” request 7 End of control
6 Unselect request
3 0-5 s 5
3 execution request
C0342ENa
The following chronogram shows an abnormal termination due to the absence of change of
the TPI value in the given delay. The device is automatically deselected, and the sequence
is aborted with negative acknowledgement.
SPC select
(optional)
SPS select
(optional)
DPC raise/lower
OPEN
raise/lower
CLOSE
TPI
Feedback Selection FeedBack

Pulse Delay
Delay timeOut
Delay
4
0-5 s
0-1 s 0-10mn 0-1 s
new SPI value
1 2 Delay 6
1 selection request “raise”
6 End of control
3 0-5 s 5
3 execution request
C0343ENa
6.5.2.3 Suppression, Forcing or Substitution of the TPI

In case of suppress or substitution of TPI value the control sequence is aborted with
negative Acknowledgement. In case of Forcing the sequence is not aborted but the value of
TPI taken in account during the control sequence is the forced value.
6.6 Control of ancillary devices
Ancillary devices are managed in “Direct Execute” or in “SBO once” mode. Refer to
generic explanations above.
6.7 Control of Intelligent Electrical Devices (IED)
6.7.1 Control to IEDs

Control requests to manage device via IEDs may be performed in the three modes (DE,
SBO once, SBO many).
6.7.1.1 Direct Execute mode

If execution checks are successful
1. The computer sends the control (open/close, low/raise, setpoint) via the
communication protocol to IED.
2. Expects IED’s control acknowledgement in the given delay (If is supported by the
protocol).
3. Expects the reception of the feedback of the request (device position SPS, DPS, TPI)
in the given delay (if is configured).
In case of fail in step 2 or 3 the sequence ends with a negative acknowledgement otherwise
the sequence ends with a positive acknowledgement.
6.7.1.2 SBO once mode

This mode can be configured only if is supported by the protocol.
6.7.1.2.1 Selection phase
After having performed the selection checks
1. The computer sends a selection request to the IED,
2. Expects selection acknowledgement from IED in the given delay,
3. Generates a positive or negative selection acknowledgement according to the result of
the selection phase,
4. If positive acknowledgement, the computer starts selection time-out and waits
execution request, otherwise ends the controls sequence.
6.7.1.2.2 Execution phase
Ditto execution phase of “Direct Execute” mode.
6.7.1.3 SBO many mode

In comparison with the “SBO once” mode, in this mode execution phase is repeated until an
unselection request. Unselection request allows to end the sequence within the computer, is
not sent to IED.
6.7.2 IED controls
6.7.3 Digital setting point (SP)
6.8 System controls

System control is used to activate or deactivate automatic functions, change computer’s
mode, bay mode, database management, etc.
A system output control remains internal on the computer (has no digital or IED output) and
may generate a system input information. They are managed in “Direct Execute” mode
only. A hardware selection has no meaning.
For some uses, such as automatism’s activation/deactivation, it is necessary to generate a
system input, which gives the state of the controlled function (e.g. ATCC ON/OFF). This
system input may be able to be used by the control sequence or enter to an interlocking
equation etc. The configuration process allows the user to assign or not a system input,
which may a SPS or DPS. System inputs generated by system outputs are stored in non-
volatile memory. In case of computer’s initialisation they are restored.
6.9 Kind of control sequence

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

Receiving control, the control sequence executes configured checks:
Operational conditions
• MiCOM C264/C264C mode management (Operational, Test, Maintenance..),
• IED connected,
• Substation control mode (Remote/Local),
• Bay control mode,
• SBMC mode,
• Uniqueness of control inside the substation.

Module conditions
• Inter-control delay,
• Status of the device,
• Lock condition,
• Automation already running (AR, AVR, …),
• Interlock equations (substation, bay, local of the module).

Execution conditions
• Delays upon selection feed back, start moving, final position reached.
6.10.1 Mode Management

Control sequences are only performed if the computer mode is in operational mode. In test
mode, control sequences are allowed but digital outputs are not set.
6.10.2 IED connected

If a control has to be sent to an IED, it is only accepted if this IED is connected to the
computer.
6.10.3 Control mode

This control sequence receives requests from the various control points:
• Automation (Auto Recloser, voltage regulation, PLC),
• MiCOM C264/C264C Local Control Display,
• MiCOM C264/C264C TBUS communication from SCADA,
• Station BUS (other computer in distributed automation, PACiS Operator Interface,

PACIS Gateway),
• Legacy BUS (from One Box Solution IED).

To avoid conflict between the control points, substation and bay modes are checked. Each
control sequence can be subject or not to these checks. The switches Remote/Local can be
hardware or software (saved in non-volatile memory).
The SBMC Site Based Maintenance Control allows controlling one specific bay from Local
Display or Operator interface even if substation is in remote. This feature is dedicated to
commissioning or maintenance and has also the possibility to filter data transmitted from the
bay to SCADA.
6.10.4 Uniqueness of control

It is possible by configuration to prevent having more than one control at a time.
6.10.5 Inter-control delay

It is possible by configuration to define an inter-control delay that is a minimum delay
between two consecutive controls on the same device.
6.10.6 Status of the device

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

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

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

Several kind of circuit breaker can be managed:
• Three phases or single phase circuit breaker,
• Synchronised or non-synchronised, with internal or external synchrocheck,
• With and without Auto Recloser.

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

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

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

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

CB Check
close synchroniser
controls
Close
Generator
Network
Busbar
(a) Application to generator
CB Check
close synchroniser
controls
Close
Network
# Network
Line A CB 1 #1
Busbar B
(b) Application to two networks
C0006ENa
FIGURE 46: CHECK SYNCHRONISER APPLICATIONS ~

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

With Vline and Vbusbar TRUE if the measured voltage is above the threshold V>, and not(Vline)
and not(Vbusbar) TRUE if the measured voltage is below the threshold V<.
The selection of the voltage control is made during the configuration phase.
By configuration, a single synchrocheck can manage two circuit breakers. Be careful, in this
case the voltage switching is not managed by the computer.
7.1.2 Auto-Recloser (AR)
7.1.2.1 Introduction
80-90% of faults on the electrical network are transient, such as lightning or insulator
flashover. When a fault occurs, the Circuit Breaker is tripped in order to protect the system.
The Auto-Recloser function is then used to close the circuit breaker after a set time, a time
that is long enough to allow the fault to clear. This duration is called cycle temporisation and
is defined in the database during the configuration phase.
But, as permanent fault can occur, an auto-recloser scheme has to be provided in order to
allow the elimination of a transient fault by an open/close sequence (auto-reclosing cycle)
and the elimination of permanent fault by, after a defined number of auto-reclosing cycle (4
cycles maximum), leaving the circuit breaker in the open state by closing the trip relay.
A transient fault, such as a lightning strike, is one that is cleared by immediate tripping of one
or more CB’s to isolate the fault, and does not recur when the line is re-energised.
This means that in the majority of fault incidents, if the faulty line is immediately tripped out,
and if time is allowed for the arc to de-ionise, reclosure of the CB will result in the line being
successfully re-energised. (A Closed/Open/Closed cycle)
However, some faults will be permanent (such as a line fallen to earth). In this case the auto-
recloser must be able to react to the permanent fault, and on the first reclose and detection
of the permanent fault open the CB’s (and, if required lock out the auto-reclose functionality).
(This is a Closed/Open/Closed/Open, 4 cycle system).
Auto-recloser (AR) schemes are implemented to carry out this duty automatically.
7.1.2.2 Behaviour
The general diagram of the auto-recloser function is:
Auto-recloser out
of service
In Service request
Auto-recloser in
service
TRIP /TRIP_1P_X
3 phases
no 1 phase
CB_HEALTHY Analysis of the CB_HEALTHY no
Cycle n˚=1
= SET ? received trip = SET ?
yes yes
Waiting CB Waiting CB
opening opening
End of 150 ms timer End of 150 ms

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

TRIP closed
Launch Cycle = cycle +1

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

7.1.2.2.1 In Service / Out of service
The auto-recloser function can be in or out of service due to an operator control (through the
station bus, the computer local HMI or a BI).
If the auto-recloser is out of service, no cycle is authorised.
If an out of service request is received during an auto-reclosing cycle, the cycle is
immediately stopped.
7.1.2.2.2 Analysis of the receiving trip

This analyse allows to detect the type of auto-recloser cycle, which can be:
• the first single-phase cycle
• the first 3-phases fast cycle
• the second 3-phases slow cycle
• the third 3-phases slow cycle
• the fourth 3-phases slow cycle

This detection is done by using:
• the current cycle number
• the TRIP_1P_X or TRIP signal sent by the protection relay (single-phase trip / 3-
phases trip)
• the configured auto-recloser cycles

During this phase, if the CB_HEALTHY signal is not in the SET state, the cycle will be not
authorised and the automation will be re-initialised to wait the first cycle. The CB_HEALTHY
BI is optional: if it doesn’t exist, no check is done.
7.1.2.2.3 Waiting CB opening
As soon as the trip has been detected, a 150 ms timer is launched to wait the circuit breaker
opening.
For a 3 single poles CB:
• If the CB position is on a per pole basis:
− In a single phase cycle, only one phase position is awaited in the OPEN state
(CB_STATE_1P_X)
− In a 3-phases cycle, each one phase positions is awaited in the OPEN state
• If the CB position is given globally:
− In a single phase cycle, the position (CB_STATE) is awaited in the MOTION00

state
− In a 3-phases cycle, the position (CB_STATE) is awaited in the OPEN state

For a triple poles CB:
• Whatever was the cycle, the 3 phase position is awaited in the OPEN state
(CB_STATE)
For a 3-phases cycle, the DO “AR_TRIP_3P” is closed (if configured) as soon as the CB is
detected as open.
The auto-recloser function is locked if the CB is not opened at the end of the timer.
7.1.2.2.4 Launch cycle timer
As soon as the CB is detected as open, the timer associated to the current auto-recloser
phase is launched.
During the single-phase cycle, the trip signal must disappear: if not, the auto-recloser
function will be locked. Furthermore, a 3-phases trip could appear. In this case, the current
cycle is stopped and the second 3-phases slow cycle is launched.
7.1.2.2.5 Closing the CB

At the end of the cycle timer, the AR_BLOCKING BI is tested: if it is in RESET state, a close
order is sent to the Circuit Breaker. Note that, if present, the synchrocheck function is used
to control the breaker during the second, third and fourth 3-phases slow cycles. The use of
the synchrocheck function during the first 3-phases fast cycle is configurable.
If the AR_BLOCKING BI is in another state, the automation is re-initialised to wait the first
cycle.
7.1.2.2.6 Launch recovering time
As soon as all concerned CB phases are closed, the Reclaimc recovering timer is launched.
If the CB remains closed during the timer, the reclosing is considered to be successful and
the cycle number is set to 0. The “AR_STATE” signal is set at AR_RECLAIMC state during
this timer.
If a new trip occurs during the timer, the next configured cycle is launched. If the trip occurs
during the last cycle, the auto-recloser is locked.
7.1.2.2.7 Particular treatments
Reclaim time on manual close
If the CB becomes closed (through an external manoeuvre) during an auto-recloser cycle,
the Reclaimmc timer is launched during which the auto-recloser function is inhibited and the
“AR_STATE” signal is set at the AR_RECLAIMMC state.
CB closing failure
If the CB closing order fails, due to DO hardware failure, interlocking scheme, or
synchrocheck inhibition, the AR_FAIL signal is set.
This SI is reset as soon as the CB is closed.
Lock of the auto-recloser
The conditions which lead to an auto-recloser locking are:
• A trip during the last auto-recloser cycle (in this case, the AR_STATE signal is set at
the AR_BAR_SHOTS state)
• A lock signal through the AR_LOCK Binary Input at the SET state
• Trip BI state is Invalid (this BI cannot be suppressed, forced or substitued)
• CB position BI(s) state is (are) Invalid
• The Trip BI is always set at the end of the cycle timer
• There is no pole discordance at the end of the single-phase cycle (i.e. the three
phases are opened)
• 2 phases are in an opened state at the end of the single-phase cycle without 3-phases
trip signal
• the CB is not opened at the end of the 150 ms timer

The AR_STATE signal is set at the AR_BAR_LOCK state if the auto-recloser function is
locked, and the cycle counter is set to 0.
There are two configurable methods to unlock the function. These methods are selected
during the configuration phase and can be used separately or together:
1. a manual closing of a circuit breaker: in this case, the Reclaimmc timer is launched.
2. an “AR_LOCK” signal at the RESET, received either through a BI or an operator order.
If none of these methods are selected, the auto-recloser is automatically unlocked if no lock
condition is set and circuit breaker is closed. In this case, the Reclaimml timer is launched. If
the CB is not closed at the end of this timer, the auto-recloser is locked again.
7.1.2.3 Informations and parameters
Information Description Type

CB_STATE_1P_x CB status, on a per pole basis BI (DP)
CB_STATE CB status (global) BI (DP)
TRIP_1P_x Trip status, on a per pole basis BI (SP)
TRIP 3-phases Trip status BI (SP)
AR_IS/OS Request to put in / out of service the auto-recloser BI (DP) or operator control
AR_LOCK Signal to lock / unlock the auto-recloser BI (SP, Group) or output of a
configurable automation or
operator control
CB_HEALTHY Availability of the breaker to be closed BI (SP)
AR_BLOCKING Signal to block the closure of the circuit breaker BI (SP, Group) or output of a
configurable automation
CB_ORDER_1P_x CB order, on a per pole basis DO
CB_ORDER CB order (global) DO
AR_TRIP_3P 3 phases trip forcing order This information can be wired
to a DO or can be used as an
internal signal.
AR_IS/OS Auto-recloser status: In / Out Of Service SI (DP)
AR_STATE Auto-recloser current state SI (MP)
AR_READY Indicate the auto-recloser is in service, unlocked State1
and no cycle is in progress
AR_WAIT_FOR_OPEN_CB Indicate the auto-recloser is waiting CB opening State2
AR_FIRST_CYCLE_1P Indicate the first single-phase cycle is in progress State3
AR_FIRST_CYCLE_3P Indicate the first 3-phases cycle is in progress State4
AR_SECOND_CYCLE_3P Indicate the second 3-phases cycle is in progress State5
AR_THIRD_CYCLE_3P Indicate the third 3-phases cycle is in progress State6
AR_FOURTH_CYCLE_3P Indicate the fourth 3-phases cycle is in progress State7
AR_WAIT_FOR_CLOSE_CB Indicate the auto-recloser is waiting CB closing State8
AR_RECLAIMC Indicate the Reclaimc timer is launched State9
AR_BAR_SHOTS Indicate an auto-recloser locking due to a max State10
number of reclosing cycles
AR_BAR_LOCK Indicate an auto-recloser locking State11
AR_RECLAIMML Indicate the reclaimml timer is launched State12
AR_RECLAIMMC Indicate the reclaimmc timer is launched State13
AR_FAIL Failure of the close order SI (MP)
AR_SYNC_NOK Due to the synchrocheck State0
AR_HARD_ERROR Due to hardware failure, lock of device or another State1
running automation linked to the device
AR_ILOCK_NOK Due to interlocking function State2
AR_NO_FAULT No failure State3
Parameter Description Value

AR_TYPE Auto-recloser type o cycle configuration Mono / Tri
AR_CYCLE_NUMBER Number of cycles 1, 2, 3 or 4
1P_CYCLE1_TIMER Timer of the first single-phase cycle From 10 ms to 5 seconds,
with a 10 ms step
3P_CYCLE1_TIMER Timer of the first 3-phases cycle From 10 ms to 60 seconds,
with a 10 ms step
3P_CYCLE2_TIMER Timer of the second 3-phases cycle From 1 to 3600 seconds,
with a 1 second step
3P_CYCLE3_TIMER Timer of the third 3-phases cycle From 1 to 3600 seconds,
3P_CYCLE4_TIMER Timer of the fourth 3-phases cycle From 1 to 3600 seconds,
RECLAIM_TIMER Reclaim timer From 1 to 600 seconds,
RECLAIMMC_TIMER Reclaimmc timer From 1 to 600 seconds,
RECLAIMML_TIMER Reclaimml timer From 1 to 600 seconds,
UNLOCKING_METHOD Method to unlock the auto-recloser None, manual close, unlock
signal, both
SYNC_ENABLE Use the synchrocheck function during the 3- Yes / No
phases first cycle
7.1.3 Trip Circuit Supervision

The trip circuit supervision monitors the trip circuit wiring continuity irrespective of CB
position but only when the trip relay is not activated. Activation of the trip relay is indicated to
the C264 by a separate input and inhibits the detection of continuity.
The MiCOM C264/C264C computer is able to support the two diagrams used in Trip Circuit
Supervision:
• Trip Circuit Supervision with one Digital Input + external resistor.
The resistor in the trip circuit supervision scheme (R) should have a value according to 2
criteria:
1. High enough so that once the CB is open, the tripping coil powered via the resistor
has no magnetic effect anymore so that the tripping mecanism is released (within a
possible delay due to inductive effect of the coil).
2. Low enough so that the C264 input powered via the resistor (and the tripping coil) is
detected active.
Therefore:
1. It is assumed that 10% of nominal voltage applied on the tripping coil makes its
magnetic effect low enough to release the tripping mechanism after activation. Taking
into account normal tolerance on power supply, this leads to a minimum value of R
being approximately 10 to 12 times the resistance of the tripping coil.
2. The input has been tested to operate with a series resistor up to 40kOhm, still leaving
voltage across the input above the minimum. Taking into account tolerances, this
defines a maximum value for the resistor of 20kOhm.
Areva recommends the value in the middle of the range (geometrically). If Rc is the
resistance of the tripping coil, then:
R / 12xRc = 20kOhm / R
The power rating of the resistor must be such that it withstands permanent application of
maximum trip circuit voltage . Therefore:
P = (1.2 x Uaux)2 / R
+ Uaux
Computer
Protection relay
Vn+
DI-1
Vn-
Vn+
DI-2
Vn-
Vn+
DI-3
Vn-
CB
- Uaux
C0138ENb
FIGURE 48: TRIP CIRCUIT SUPERVISION WITH ONE DI
• Trip Circuit Supervision with two Digital Inputs without external resistor.
+ Uaux
Computer
Protection relay
Vn+
DI-1
Vn-
Vn+
DI-2
Vn-
Vn+
DI-3
Vn-
Vn+
DI-4
Vn-
CB
C0139ENb
- Uaux
FIGURE 49: TRIP CIRCUIT SUPERVISION WITH TWO DI

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

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

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

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

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

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

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

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

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

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

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

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

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

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

OR
− Actual Voltage is invalid.

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

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

OR
− More than 4 transformers in the group.

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

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

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

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

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

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

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

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

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

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

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

For a Tap Up(to increase voltage), tapping is performed as soon as the following are TRUE:
• T > Ti + T2
• V < Vi + MVCR * (T - Ti)

For a Tap Down (to decrease voltage), tapping is performed as soon as the following are
TRUE:
• T > Ti + T2
• V > Vi - MVCR * (T - Ti)

The maximum voltage rate is achieved as described in the example below:
Volt
RateMax
Time
T1 T2 T2
T0
Tap RAISE 1 Tap RAISE 2 Tap RAISE 3

C0010ENa
FIGURE 50: VOLTAGE REGULATION

Tap RAISE 1 is performed after T1.
Tap RAISE 2 is performed T2 after Tap RAISE 1, at this time the voltage change rate is
lower than the maximum rate.
Tap RAISE 3 is NOT performed T2 after Tap RAISE 2, because at this time the voltage
change rate is greater than the maximum rate. It is performed when the current voltage
change rate becomes lower than the maximum rate.
It is possible to choose by configuration a T1 delay as a fixed delay or as an inverse time
delay.
When inverse initial time delay is selected:
DV = | actual group voltage - deadband limit voltage |
• IF DV < 1% target voltage THEN initial tap time delay = T1.
• IF 1% <= DV < 10% target voltage THEN initial tap time delay = T1/DV.
• IF DV >= 10% target voltage THEN initial tap time delay = T1/10.
When a transformer belongs to a group of several transformers, the time out is applied to the
group. Two different groups have separate time out references, thus allowing simultaneous
taps.
• The tap is defined as the "first one" when (logical OR):
• The group mode has changed.
• The voltage comes back into the deadband2.

When the voltage is crossing from one side of the deadband to the other side.
7.1.4.5.4 Single transformer management
If a group is restricted to one transformer and is in automatic control mode, raise and lower
commands are issued if the voltage exceeds the voltage deadband with respect of the time
outs.
7.1.4.5.5 Multiple transformers management

If a group is composed of more than one transformer and is in automatic control mode, then
the coordination of the transformers of the group aims at minimising the circulating power. To
achieve this, there exist three methods depending on the substation constraint and customer
requirement. By configuration one of these three methods has to be chosen.
For the three following methods, if all the transformer tap-changers reach their end stop
while tapping is required to go further, then the substation alarm "target not achievable" is
generated. This alarm disappears when the problem is cleared.
First method: “TAP”
In this case, assumption is made that:
• the primary voltages of the transformers are identical
• the number of taps and tapping ranges of the transformers are identical
Then the maximum tap span between the transformers will be 1 and there will be a balanced
control of them when the voltage is changing.
Calculation is as follows:
1. if voltage is out of the deadband,
1.1. and under the deadband -> action is raise on the transformer with the lowest
Tap
1.2. and upper the deadband -> action is lower on the transformer with the highest
Tap
2. if voltage is in the deadband, the system sets the transformer within one tap
Second method: “Transformer ratio”
In this case, assumption is made that the primary voltages of the transformers are identical.
Calculation is as follows:
1. if voltage is out of the deadband,
1.1. and under the deadband -> action is raise on the transformer with the lowest
transformer ratio
1.2. and upper the deadband -> action is lower on the transformer with the highest
transformer ratio
2. if voltage is in the deadband, the system sets the transformer within a percentage of
transformer ratio. This percentage P is calculated for all groups:
P = Maximum (tapping range / (number of taps - 1 ))
Example:
Group with 3 transformers:
• SGT1: 19 taps, tapping range = 30 %

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

configuration)
Third method: “circulating current minimisation”
In this case, there is no assumption that the primary voltages of the transformers are
identical.
With a sample example of two transformers:
SGT1 SGT2
I1 I2
Per transformer, we know
• Sn (rating),
• x (Impedance in % on Sbase: e.g.100 MVA),
• U,
• I,
• P,
• Q,
• Current tap
• Unom (nominal secondary voltage)
X (reactance) = x * (Unom)² / Sbase
One transformer can be presented as below:
E
The both transformers can be presented as below:
I
Ic
X1
X2
U
I1 I2
E1 E2
We have
U = E1 - X1*I1 = E2 - X2*I2 => E1-E2 = X1*I1 - X2*I2
I = I1 + I2
E1 - E2 = (X1 + X2 ) * Ic
=> Ic = (X1*I1 - X2*I2) / (X1 + X2)
For each transformer, we have U,I,P,Q (So U1,I1,P1,Q1 and U2,I2,P2,Q2)
We have for i=1 or i=2, Qi/Pi = tan ϕi
According to the signs of Pi and Qi: -π < ϕi < π
If there is a circulating current from transformer 1 to transformer 2 then ϕ1 > ϕ2.
U1 = U2
I
I2
φ1
I1
Voltage out of the deadband
If the voltage is out of the deadband and active power > 0 (|ϕ| < π/2) then:
• If the voltage is under the target then transformer with highest |ϕ| is tapped UP
• If the voltage is over the target then transformer with lowest |ϕ| is tapped DOWN
If the voltage is out of the deadband and active power < 0 (|ϕ| > π/2) then:
• If the voltage is under the target then transformer with lowest |ϕ| is tapped UP
• If the voltage is over the target then transformer with hughest |ϕ| is tapped DOWN
For three or four transformers, the same algorithm is used.
Voltage into the deadband
If the voltage is into the deadband then the circulating current must be checked to know if it
is possible to reduce it.
∆U = E1 – E2 = |X1*I1 - X2*I2|
∆U is compared to the voltage step corresponding to one tap (∆U1tap).
TapSpan: tap span for the transformer
NbTap: number of taps for the transformer
Unominal: nominal secondary voltage
∆U1tap = (TapSpan/(NbTap -1)) * Unominal
if ∆U > ∆U1tap and if ϕi > ϕj so
If the voltage is out of the deadband and active power > 0 (|ϕ| < π/2) then:
• If the voltage is under the target then transformer with highest |ϕ| is tapped UP
• If the voltage is over the target then transformer with lowest |ϕ| is tapped DOWN
If the voltage is out of the deadband and active power < 0 (|ϕ| > π/2) then:
• If the voltage is under the target then transformer with lowest |ϕ| is tapped UP
• If the voltage is over the target then transformer with highest |ϕ| is tapped DOWN
For three or four transformers, the same algorithm is used.
7.1.4.5.6 Target voltage
When the operator changes a target voltage, the new target voltage is indicated immediately.
The actual target voltage will not be changed by more than the corresponding pre-set value if
the busbar is under automatic control. If the busbar is not under automatic control the new
target voltage is immediately achieved.
7.1.4.5.7 AVR inhibited
AVR is inhibited for the corresponding group while the measured system voltage is less than
a pre-set value or higher than an other pre-set value.
Overcurrent on a transformer will also inhibit the transformer's group.
7.1.4.5.8 Homing
Homing is a facility which taps transformers such that their open circuit terminal volts follows
the volts on the busbars that they are selected to within 3% of the busbar voltage when the
mode of this busbar is In automatic control.
Homing is only able if there is at least one transformer connected on the corresponding
busbar and if transformer busbar disconnector is closed and LV circuit breaker open.
Homing is disabled while the busbar voltage is less than Umin (80% of nominal voltage).
If a transformer is under Homing Mode, a manual control is not accepted.
Homing ceases when the tap changer is faulty and until the operator selects "Clear AVR
faults". If the Tap Changer is still faulty then the transformer remains OUT of automatic
control.
Time out T3 is used for the first tap in the homing mode.
Time out T4 is used between successive taps.
7.1.4.6 Capacity
AVR is able to manage a maximum of:
• 7 transformers,
• 4 transformers in parallel,
• 8 busbars,
• 4 transformers per busbar,
• 2 reactors per transformer,
• 2 voltage levels.
7.1.4.7 List of configurable parameters

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

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

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

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

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

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

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

In an electrical substation, the switching devices are primarily the followings:
• Circuit breakers
• Traditional disconnecting switches
• Disconnecting switches with abrupt rupture
• Ground disconnecting switches

The operating of a switching device is directly related on its nature and its environment. It
can be operated only with respect of certain conditions. These conditions, therefore called
interlocking, are managed in the form of logical equations within the computer.
Moreover, interlocking can be applied on whatever module or whatever control.
The goal of the function of interlocking is to prohibit operating which would be ordered by
error, in remote control, to a switching device beyond its standard conditions of operation.
Some equations of substation interlocking also manage the operations of the disconnecting
switches according to topology and by respecting some preset rules: topological interlocking.
The equations of topological interlocking, awashed with substation equations, are generated
by independent software. This software takes in account the topology and some predefined
rules to provide these equations
7.2.1 Inputs
Interlocking function can use the following inputs:
• Digital inputs from the systems digital input boards, from other system computers,
from protection relays and other IED’s via communication network (single and double
point, digital groups),
• Internal indications (e. g. system failures, equipment operation modes, ...),
• Limits derived from measured values from the systems analog input boards (CT, VT,
transducers), from other system computers, from protection relays and other IED’s via
communication network.
7.2.2 Outputs
Result of the interlocking equation is transmitted through a system binary output and saved,
locally in RAM, by the function managing interlocking logical equations.
And, a service is available for any task to get the result of the computation.
Thus , the function managing “control of sequence” uses this service to know whether control
can be executed.
Then, a simple transient binary input can be set if defined in configuration. The same SPS is
used for the commands “open” and “ close” of a xPC
7.2.3 Control
No control. An equation is computed each time that one of its input changes of state or of
validity.
7.2.4 Behaviour
7.2.4.1 Principle
In computer, a logical interlocking equation is defined as a sum of product (AB+CDE+F for
example).
7.2.4.1.1 Introduction
Interlocking function uses up to two interlocking equations per switching device on bay-level
and on substation-level. During configuration process the definition of the switching devices
can be:
• without associated interlocking equations,
• with only one interlocking equation, e. g. for opening, closing being not checked or
vice-versa,
• with two interlocking equations (for opening and closing). The interlocking equations
can be different but can also be identical.
The equation is composed of Boolean information mainly representing the position of other
switching devices.
The interlocking for a switching device may be composed of substation interlocking
equations and local interlocking equations.
Both interlocking are managed by the computer which controls the switching device.
Local equation is made up of information obtained from its own digital inputs and IEDs
connected to this computer.
Substation interlocking is made up information obtained from its digital inputs and inputs
provided by the communication network from other computers, from bay computers and from
IED’s (protection relays, etc.). Substation interlocking can also be managed by the
topological interlocking function (Refer to Topological interlocking for more details.
7.2.4.1.2 Local interlocking
The local interlocking is done by calculation of a logical equation. It can exist up to one
equation per switching device and per each direction (open and close). If there is no
equation for a switching device for a direction, the corresponding variable is true.
7.2.4.1.3 Substation interlocking
The substation interlocking analyses the position of all switching devices in the substation
and calculates the substation interlocking equation to authorise control of a switching device
according to the mechanical and electrical capabilities of the switching device. If there is no
equation for a switching device for a direction, the corresponding variable is true.
7.2.4.1.4 Validity of information
The interlocking equation does not only use the value of the information but also the validity
of the information (invalid, ...).
Thus the result, saved in RAM, of a logical equation is only TRUE or FALSE, An Interlocking
equation in the INVALID state will be considered as FALSE .
But, the system binary input also generated can be valid (SET or RESET) or invalid.
The evaluation of the result of basic logical function such as NOT, AND or OR is defined as
follows:
NOT
True False
False True
Invalid Invalid
OR True False Invalid

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

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

7.2.4.1.5 Interlocking bypass
Bypass made by key switch
Interlocking can be overridden (interlocking bypass mode). Overriding of interlocking can be
set from the local control point.
During configuration optional overriding of interlocking from any other control point can be
defined according to customer requirements. This includes the possibility of overriding of
interlocking per switching device or per bay or per substation entity basis.
If an interlocking is overridden, the associated variable is true.
Bypass within the control
From any control point, operator can bypass the interlocking check. Bypass is then an
attribute of the control. If bypass is set, the function managing the “control of sequence” does
not use the service giving the current result of the interlocking equations.
7.2.4.2 Software tasks

A logical equation is a sum of products. Each product comprises logical data that can be
complemented. Each electrical component has two logical equations at the most, and each
logical equation is associated with one electrical component.
Example of Logical equation: X = A.B + C.D.E
In this example, the component X can be operated only if:
• (A is in the higher state) AND (B is in the lower state)
OR
• (C is in the lower state) AND (D is in the higher state) AND (E is in the lower state)
The terms of these equations can be issued from:
• Simple point status. (BI)
• Double point status (BI)
• 1 among N BI (SIG)
• Measurement (MEAS)
At configuration time, operator has to define the “interlocking profile” of each data included in
an interlocking equation. It means that operator must select for each state or validity of a
data a logical state (TRUE, FALSE or INVALID).
Interlocking computation
As said before, an interlocking equation;
• is computed each time that one of its element changes of quality or state and
• is defined by a sum of product.

Upon reception ofa new state or quality for a data
• Get logical state associated to the received state and validity of the data
• For each equation that includes the data
− Compute the sum of product
− Determine the result of the interlocking equation (TRUE or FALSE)
− Send new state of the system binary input representing the result of the interlock.
BI can be: SET, RESET or INVALID
Interlocking consultation
On reception of open or close request, if the logical equation associated with the switching
device exists, the “control of sequence” function used the service offered by the interlocking
function to get the result of the interlocking associated to the received request.
If result of the interlocking is TRUE, the check is considered as achieved, else request must
be refused and a negative acknowledgement sent to the origin of the request.
Simulation and test of interlocking equations
The interlocking system is checked during the in house test of the substation control system.
Each interlocking equation may be checked by issuing a control to the corresponding
switching device.
For checking the interlocking on site a “SIMULATION mode“ is implemented in the computer.
In this operating mode, a valid control is sent to the output, but closing the contact is not
performed and a positive acknowledgement message is generated.
7.2.5 Limits and performance

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

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

package hardware
C0019ENa
FIGURE 51: PLC WORKBENCH

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

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

• CO
NOTE: A CO can be used as input of a PLC function, but only through the
use of ‘C’ function present by default with the kernel.
7.3.1.3 Acknowledgement of control

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

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

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

request,
• send binary order to computer boards or IED or to another computer,
• send digital setpoints to computer boards or IED or to another computer.
7.3.3 Control
Automations can be triggered:
• by operator request,
• by events (digital or analogue input state changes),
• cyclically (each day, each week or each month),
• at a specific date and time (e. g.: 20. 12. at 10:00).

7.3.4 Behaviour
The computer has a software execution engine designed to interpret the automation
application code according to the cycle described hereafter.
Read inputs
Execute programs
Write outputs
C0345ENa
Basically, the cycle duration depends on the number of I/O to be scanned and the complexity
of the operations to be performed. It will be set during the configuration process.
7.3.4.1 Interfacing with a HMI or a RCP/SCADA

A remotely sited master station can send and receive data to and from the automation
applications of the computer.
In DB, the data sent by a master station to an automation application include DO and BI
entities. Conversely, the data received by a master station from automation applications
include DI, Measurements, Metering (non-tariff), and Tap Changer Position entities. These
data have a unique transmission address for the computer.
7.3.5 Limits and performances

• The execution of the automation sequences can be cyclic and/or event-driven.
• Maximum number of cyclic PLC-programs is 32.
• The two different time cycles of a PLC-program can be set from 10 ms up to several
seconds. For some specific equations a cycle less or equal to 10ms and a cycle less
or equal to 100ms for the other logic equations. The time cycle for the automatic
functions shall be less than 100ms.
• Each PLC-program runs on one computer, which means a PLC-program cannot be

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

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

As automatisms created through ISaGRAF are dependent from the ISaGRAF cycle whose
value is about 50ms in the best case, it is necessary to implement some configurable
automatisms that can be achieved in less than 50ms.
PSL is the solution for implementation of automatism that must be performed as quickly as
possible.
Designed solution is mainly based on mechanism used for the computation of logical
interlocking (refer to §logical interlocking for more details). Indeed, logical gates AND, OR,
NOT, NAND, NOR or a combination of these gates can be processed as a logical equation.
Some other functions (drop-off and pickup timer, bistables) are added to these logic gates.
These automations are event-driven: they are calculated each time an input changes (i.e.
there is no cycle time).
Only BI and measurements described are usable as inputs (controls are not).
PSL are logical equations that use the following functions:
• AND, OR, XOR, NOT, NAND, NOR operators
• "bistable" functions
• pickup and drop-off timers (from 10 ms to 60 seconds, by step of 10 ms)
• BI setting – the system BI is:
− SET if the PSL is TRUE
− RESET if the PSL is FALSE
− INVALID if the PSL is INVALID
• Digital Output setting – the DO is:
− closed if the PSL is TRUE
− opened if the PSL is FALSE or INVALID (only in case of permanent DO)
− INVALID if the PSL is INVALID
The equations management rules described for interlocking equations apply on PSL.
Digital outputs used as outputs are mandatory local hardwired DO directly managed by the
computer
I1
& DO1
setting
I2
& DO2
setting
≥1 t
&
BI1
≥1
setting
≥1
I3
≥1
I4
C0140ENa
FIGURE 52: EXAMPLE OF PSL

8. USER INTERFACE
This section is described in the chapter Human Interface.
9. RECORDS
Several kinds of records are stored into MiCOM C264/C264C.
9.1 Permanent records storage

They are stored on flash disk.
9.1.1 Data storage

All parameters or settings that can be modified via front face LCD are stored in flash disk.
Lists of system information are also stored in the flash disk.
9.1.2 Waveform Recording

A waveform recording deals with the storage of measurement and logical information in
order to visualise the electrical network behaviour when electrical event appear, such as the
start of the generator. These types of events are called “trigger of waveform recording”.
In order to see the influence of a trigger, data are recorded before (pre trigger time) and after
(post trigger time) the raise of the trigger.
Two types of waveform recording can be performed in the computer:
• Fast Waveform recording which gives access to samples
• Slow wave form which gives access to RMS values
9.1.2.1 Fast Waveform Recording

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

8 60
4 120
2 240
1 480
The waveform recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of binary inputs (SP, DP, MP, SI or Groups)
• Changes in state of digital outputs
• Measurement threshold violations
• Operator request
Only one re-trig is allowed: it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are available in COMTRADE 2001 format.
9.1.2.2 Slow Waveform Recording

The inputs for the slow waveform records are:
• analogue values coming from CT VT calculation (RMS values)
• analogue values coming from AIU boards
• Digital inputs
• Digital outputs
The slow waveform manages up to 24 analogue and 48 digital values.
Data from CT/VT can be chosen among:
• RMS Values of phase voltage
• RMS values of busbar voltage
• RMS values of phase current
• RMS values of residual voltage and current
• Fundamental sequence components
• Active Power
• Reactive Power
• Apparent Power
• Frequency
• Harmonics levels
MiCOM C264/C264C stores at maximum 5000 integrated values as follow:
Number of Files Number of integrated values

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

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

9.1.3 Events
All data change or events declared in MiCOM C264/C264C configuration database “To be
logged” are stored in a circular queue.
The event records are available for viewing either via the front panel LCD, via slave protocol
at SCADA level or on CMT equipment. They also can be printed.
Events, following MiCOM C264/C264C configuration, may typically contain the MiCOM
C264/C264C description, the date of the event and the time of the event with an accuracy of
1 ms, plus specific information regarding the causes of the events.
The MiCOM C264/C264C under the following circumstances may create events:
• Changes of state of Binary Inputs (SP, DP, MP, SI, Groups)
• Changes of state of Measurements
• Changes of state and value of Tap Position Indications
• Devices Control actions and acknowledgements
• Alarm acknowledgement
The size queue is:
• 200 data for front panel
• 2000 data for CMT
• configurable per slave protocol for SCADA
9.2 Non-permanent data storage
9.2.1 Alarms
9.2.1.1 Definitions
9.2.1.1.1 Definition of an alarm
An alarm is a visual (and optionally audible) annunciation of the appearance and/or
disappearance, within the controlled electrical process or within the system itself, of an
event, defined during the configuration phase as ”to be alarmed”.
These definitions, of what is to be alarmed and what it is not, are completely user relevant.
However the concept of alarms into PACiS has been introduced to inform the operators of
“abnormal” or “special” events or other miscellaneous events which must absolutely not be
overlooked.
9.2.1.1.2 Types of alarmed data
An alarm can be generated by the following events:
• each Binary Input (SP, DP, MP, SI, IED input, Groups) state
• each Measurement state
• each TPI state or value
• each metering state

associated to “the reason for change” of these events.
For example, the OPEN state of a circuit breaker can be un-alarmed if the change is due to a
control, and alarmed if the change is due to an other reason.
Furthermore, an alarm can be associated to a control acknowledgement. In this case, the
alarm is considered as “spurious”.
9.2.1.1.3 Alarm states definition

An alarm is generated by an event (e.g. a particular datapoint in a state defined during the
configuration phase as “to be alarmed”).
While this event is still present (e.g. the previous particular datapoint is still in the same
state) the alarm is “active”.
When this event disappears (e.g. the previous particular datapoint is now in another not
alarmed state) the previous alarm is “inactive”.
An existing alarm (active or inactive), can be acknowledged by an operator from the front
panel.
So an alarm can have the following states:
• inactive: no transition, no event

• active-acknowledged: the cause is still present but the active state has been taken into
account by the operator
• active-unacknowledged: the cause is still present and the active state has not been
taken into account by the operator
• inactive-unacknowledged: the cause has disappeared but the inactive state has not
been taken into account by the operator (only available for events alarmed on
appearance and disappearance)
• inactive-acknowledged: the cause has disappeared and the inactive state has been
taken into account by the operator
• inactive-active-unacknowledged: the cause has disappeared but the active state
(previous state) has not been taken into account by the operator
9.2.1.1.4 Parameters associated to an alarm
The following user-selectable parameters can be associated with each alarm definition. The
values are set during the configuration phase on a per alarm basis:
• immediate or differed:
− an “immediate” alarm is displayed as soon it has been detected.
− a “differed” alarm is displayed only after a user-selectable time delay following its
detection (the event associated with the alarm must remain present during the
delay; if not, the alarm will be not displayed) ; this delay is in the range of 1 to 120
seconds and can be set to particular value for each “differed” alarm.
• gravity level: this level is defined for each alarm allowing a hierarchical classification to
deal with the urgency of the events; the gravity level value can be: 0, 1, 2, 3, 4 or 5, 5
being the most grave and 0 meaning that there is no gravity level.
• alarm generated:
− only when the associated event appears
OR
− when the associated event appears AND when it desappears

In this case the “differed” parameter is taken into account only when event appears;
when event disappears the new state of the alarm is displayed immediately.
• alarm clearing mode:

− manual: the alarm is cleared only on an operator request; this clearing command
is only allowed on inactive-acknowledged alarms.
− automatic: an alarm is automatically cleared when it reaches the appropriate state.
− gravity basis
• audible or not when detected
9.2.1.2 Alarm processing

Only one alarm (the last one) associated with a state change of a data is displayed. The
previous one (concerning the data) is replaced by the current one.
According to the previous example, only one from the three alarmed states can be displayed
for the switching device: e.g. « JAMMED » or « TOGGLING » or « OPEN » state (the last
one which has appeared).
By configuration, one of the following behaviour is chosen:
Alarm inactive
/ cleared
0
AL+
AL+
Alarm active-
AL- (auto) unacknowledged AL+
AL+ ACK AL-
Alarm active- Alarm inactive-

acknowledged active-
unacknowledged
2 3
AL- ACK
ACK (auto)
Alarm inactive-
acknowledged
CLEAR AL+
4
C0143ENa
FIGURE 53: EVENT ALARMED ON APPEARANCE ONLY

Alarm inactive
/ cleared
0
AL+ AL+
AL+
Alarm active-
unacknowledged
AL+
1
AL+
AL-
ACK Alarm inactive-

active-
unacknowledged
5
ACK
Alarm active- Alarm inactive-

acknowledged unacknowledged
2 AL- 3
ACK
ACK (auto)
Alarm inactive-
CLEAR acknowledged AL+
4
C0144ENa
FIGURE 54: EVENT ALARMED ON APPEARANCE AND DISAPPEARANCE

Transition events:
• AL+: alarmed event appearance
• AL-: alarmed event disappearance
• ACK: operator acknowledgement of the alarm
• CLEAR: operator clearing of the alarm

NOTE: In that case «alarmed event disappears (AL-)» means that the
associated data is now in another state which is not alarmed. The time
stamp of the alarm is modified.
Transition conditions:
• (auto) means Automatic clearing

Transition description:
The transition from alarm state "0" to alarm state "1" is crossed when the alarmed event
appears (AL+).
The alarm state transitions "1 → 1" and "2 → 1" are crossed when the state of the data
associated with the alarm goes from a state which is flagged to be alarmed with any gravity
level to another state which is also flagged to be alarmed with any gravity level (AL+). In this
case the active alarm stays active but the time tagging of the alarm is changed. The new
alarm time stamp corresponds to the last associated data state change. The alarm becomes
unacknowledged if not already unacknowledged.
The alarm state transitions "1 → 2", "3 → 4" and “5 → 3” are crossed on operator
acknowledge action. The time stamp of the alarm is unchanged.
The alarm state transitions "1 → 3" and “1 → 5” are crossed when the alarmed event
disappears (AL-). The time stamp of the alarm is modified.
The alarm state transition "2 → 4" is crossed when the event disappears (AL-) the alarm
being configured to be activated only "on appearance of the event". The time stamp of the
alarm is modified.
being configured to be activated "on appearance and disappearance of the event". The time
stamp of the alarm is modified and the alarm will have to be acknowledged again.
The alarm state transitions "3 → 1", "4 → 1" and “5 → 1” are crossed when the previous
alarmed event appears again or when another state which is also flagged to be alarmed with
any gravity level appears (AL+). The alarm becomes active-unacknowledged. The time
stamp of the alarm is modified.
being configured to be activated only "on appearance of the event" and «to be cleared
automatically». The alarm is suppressed from the alarm list.
The alarm state transition "3 → 0" is crossed on operator acknowledgement only if the alarm
associated with the event is configured as «to be cleared automatically». The alarm is
suppressed from the alarm list.
The alarm state transition "4 → 0" is crossed on operator clearing action. The alarm is
suppressed from the alarm list.
9.2.1.2.1 Acknowledgement
Acknowledgement of an alarm can be done by two ways:
• On operator request: an operator can acknowledge an existing alarm from the front
panel to signify that it has been taken into account.
• Globally: at substation level it is possible to use a SPS (named Global alarm ack)
specially dedicated to a global acknowledgement of alarms.: When this SPS is set to
the SET state all alarms present in the computer are acknowledged. As long as this
SPS remains in the SET state, any new alarm is inserted in the alarm list with the
ACKLOWLEDGED status.
In addition to the Global Alarm Acknowledgement SPS, a Local Alarm
Acknowledgement SPS can be defined on a per C264 basis (i.e. one per C264).
This SPS can be wired or managed by an automation. When this SPS is configured in
a C264, the “Global Alarm Acknowledgement” SPS is no more taken into account by
this C264.
When this SPS is SET, all C264 alarms are immediately acknowledged.
This SPS cannot be transmitted on the Station Bus network (i.e. it remains local to the
C264, so it cannot be associated to a remote – OI or SCADA - control).
9.2.1.2.2 Clearing
Whatever the clearing mode is, the clearing of an alarm is immediately taken into account:
suppression from the alarm list.
Automatic clearing
An alarm can be configured as “to be cleared automatically”. It means that when this alarm
reaches the appropriate state, it is cleared automatically without any operator action. The
cases of “automatic clearing” are:
• the alarm is in the active-acknowledged state and the alarm disappears (for event
alarmed on appearance only)
• the alarm is in the inactive-active-unacknowledged state and the operator
acknowledges it (for event alarmed on appearance only)
• the alarm is in the inactive-unacknowledged state and the operator acknowledges it
(for event alarmed on appearance and disappearance)
This feature can be configured on a per alarm basis.
Operator request clearing

An alarm which is not configured as “to be cleared automatically” has to be cleared by an
explicit operator action (this action being only possible when it is in the “inactive-
acknowledged” state). Otherwise it remains present in the alarm list.
As for acknowledgement done by an operator, clearing of alarms by an operator can be
configured as to be printed or not printed.
A global clearing procedure, which allows to clear all “inactive-acknowledged” alarms in a
single operation, will be provided.
Audible alarms
An audible alarm can be associated with the “unacknowledged” state of an alarm. This
facility is configurable on a per alarm basis.
If an alarm is configured “audible” then the sound appears when the alarm is displayed.
The audible alarm is stopped when all audible alarms are acknowledged.
An audible alarm can be associated with the “unacknowledged” state of an alarm. This
facility is configurable on a per alarm basis.
If an alarm is configured as “audible” then the sound appears when the alarm is displayed.
The audible alarm is stopped when all audible alarms are acknowledged.
BLANK PAGE
Hardware C264/EN HW/C40
MiCOM C264/C264C
HARDWARE
CONTENT
2. HARDWARE DESCRIPTION 4
2.1 Concept 4
2.1.1 Components 4
2.1.2 Hardware Overview 5
2.2 MiCOM C264C 6
2.2.1 Hardware presentation 6
2.2.2 Modularity 7
2.2.3 I/O Capabilities 8
2.2.4 Front Back Plane – FBP24x 8
2.2.5 Front Panels 9
2.3 MiCOM C264 11
2.3.1 Hardware presentation 11
2.3.2 Modularity 12
2.3.3 I/O Capabilities 13
2.3.4 Front Back Plane – FBP28x 13
2.3.5 Front Panels 13
2.4 Coding of board address 14
2.5 Modules description 15
2.5.1 Power auxiliary supply and legacy ports board – BIU241 15
2.5.2 Central Processing Unit and base communications board – CPU260 17
2.5.3 Central Processing Unit and base communications board – CPU270 19
2.5.4 Digital Inputs Unit – DIU200 20
2.5.7 Digital Outputs Unit – DOU200 23
2.5.8 Circuit breaker Control Unit - CCU200 24
2.5.9 Analogue Input Unit – AIU201 25
2.5.12 Transducer less Measurements Unit – TMU200/TMU220 28
2.5.13 Ethernet Switch Unit – SWU200/SWU202 29
2.5.14 Ethernet Redundant Switch Unit – SWR202/SWR212, SWR204/SWR214 31
2.5.15 Dual Homing Ethernet Switch Unit – SWD202/SWD204 37
2.5.16 Extended communication Unit – ECU200 44
2.5.17 Extended communication Unit – ECU201 45
2.6 Hardware tropicalisation 45
C264/EN HW/C40 Hardware
BLANK PAGE

This document is a chapter of MiCOM C264/C264C documentation binders. It describes the
product hardware which is not the commissioning chapter.
2. HARDWARE DESCRIPTION
2.1 Concept
2.1.1 Components
The MiCOM C264/C264C is based on a modular and scalable architecture to support
dedicated hardware modules adapted to the plant data interfaces.
Each MiCOM C264/C264C rack can be equipped with the following modules:
• BIU241: Basic Interface Unit. This board includes the auxiliary power supply
converter, the watchdog relay, 2 digital outputs/2 digital inputs for computer
redundancy and 2 insulated RS485/RS232 interface
• CPU260 (also named CPU2) or CPU270 (also named CPU3): Central Processing Unit
and communications board based on PowerPC processor
• DSP200: Digital Signal Processing board is the processor board for CT VT calculation.
It is the CPU200 daughter board
• FBP28x: Front BackPlane: bus for 80TE case
• FBP24x: Front BackPlane: bus for 40TE case
• DIU200: Digital Inputs Unit each with 16 digital inputs
• DIU210: Digital Inputs Unit each with 16 digital inputs with current-peak and voltages
from 24V to 220V
• DIU220: Digital Inputs Unit each with 16 digital inputs for voltages 48/60V and
110/125V
• DOU200: Digital Outputs Unit each with 10 digital outputs for alarms
• CCU200: Circuit breaker Control Unit each with 8 digital inputs and 4 digital outputs
• AIU201: Analogue Input Unit each with 4 analogue inputs direct current or voltage
• AIU210/AIU211: Analogue Input Unit each with 8 analogue inputs direct current
• TMU200 (TMU220): Transducerless Measurements Unit board for direct CT/VT

measuring acquisition with 4 CT and 4 VT ( 5 VT for TMU220)
• SWU20x: Ethernet SWitch Unit board with 4 electrical links and x= 0 or x=2 optical
links
• SWR2xx: Ethernet SWitch board for Redundant Ethernet ring with 4 electrical links
and 2 optical links for the redundant ring.
• SWD2xx: Ethernet SWitch board for Dual Homing Ethernet star, with 4 electrical links
and 2 optical links for a Dual star.
• ECU200: Extended Communication Unit board to convert non insulated RS232 into
optical signal
• ECU201: Extended Communication Unit board to convert non insulated RS232 into
insulated RS485 signal
• GHU201 (for C264) or GHU200 (for C264C): Graphical Human machine interface
Unit: Front Panel including 17 LEDs (13 free configurable) + 7 pushbuttons (L/R,
Open, Close, etc) + LCD (resolution of 128 x 128 pixels /16 lines of 21 characters
each) and a keypad at the front plate for local MMI management
• GHU211 (for C264) or GHU210 (for C264C): Front Panel including 17 LEDs (12 free
configurable) + 1 pushbutton (L/R)
• GHU221 (for C264) or GHU220 (for C264C): Front Face used to connect a detachable
HMI (GHU20x or GHU21x)
2.1.2 Hardware Overview
Watchdog
FBP280 BIU241
or FBP242 (1) Redundancy
RS232 or RS485 or RS422
COM 1 / COM 2
RS232 or RS485
Power Supply
Electrical RJ45 link
CPU260 Ethernet Optical link ( CPU260 ) or Electrical link (CPU270)

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

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

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

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

2.2 MiCOM C264C

2.2.1 Hardware presentation
The MiCOM C264C mechanical rack has the following features:
• Height: 4 U
• Width: 40 TE
Dimensions of this rack are in the figure below:
FIGURE 2: MiCOM C264C – RACK SIZE

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

2.2.2 Modularity
The MiCOM C264C is available in two case versions allowing flexibility and scalability in the
use of the I/O modules:
FIGURE 4: MiCOM C264C – REAR PANEL OVERVIEW WITH CT/VT BOARD

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

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

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

2.2.5 Front Panels

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

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

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

2.3 MiCOM C264

2.3.1 Hardware presentation
The MiCOM C264 mechanical rack has the following features:
• Height: 4 U
• Width: 80 TE
Dimensions of this rack are in the figure bellow:
FIGURE 10: MiCOM C264 – FRONT PANEL OVERVIEW

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

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

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

2.3.5 Front Panels
2.3.5.1 GHU201
The GHU201 is the front panel with LCD and LEDs used for the MiCOM C264:
• 7 pushbuttons (L/R, Open, Close, etc)
• a keypad at the front plate for local MMI management with 5 pushbuttons
• a LCD (resolution of 128 x 128 pixels /16 lines of 21 characters each)
FIGURE 15: MiCOM C264 – GHU201 BOARD

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

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

Same rule is applicable to all I/O boards (DIU200, DIU210, DIU220, AIU201, AIU210,
AIU211, DOU200, and CCU200):
Binary coding on 4 jumpers top down (From 0 to 15)
− Jumper
− missing => 1
− present => 0
Example:
1 0
0 2
0 0
0 8
address =1 address = 10
C0030ENa
NOTE: Two boards of the same type must not have the same address
2.5 Modules description
2.5.1 Power auxiliary supply and legacy ports board – BIU241
This board includes:
• the auxiliary power supply converter
• the watchdog relay (closed if the product is healthy)
• 2 outputs (Normally open contacts) and 2 inputs for redundancy
• 2 insulated interfaces (Port 1: RS232 or RS485, Port 2: RS232, RS422 or RS485)

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

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

2.5.1.1 Configurable communication Port 1 - RS232/485
The communication link characteristics are:
• full duplex serial protocol
• Transmission rate: 50 b/s to 56 kb/s (configurable with PACiS configurator or settable

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

via GHU20x)
Configuration:
The hardware jumpers arrangement is as follow.
• In RS232 set the jumpers S5, S6, S9 and S3
• In RS485 set the jumpers S7, S8, S2. It is possible to end the line with a 124Ω resistor
by setting S11. (See CO chapter to know when the resistor has to be used).
• In RS422 set the jumpers S7, S8, S4 and S2. It is possible to end the line with a 124Ω
resistor by setting the jumpers S10 and S11. (See CO chapter to know when the
resistor has to be used).
2.5.2 Central Processing Unit and base communications board – CPU260

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

This board is interfaced with all I/O boards and the front panel.
CPU260 has the following key features:
• 32-bit Power PC-based microprocessor (MPC860DP or MPC860P) clocked at

80 MHz;
• 64 Mbytes Dynamic memory DRAM
• 16 Mbytes Flash memory
• 256 Kbytes static memory SRAM
• Calendar saved
FIGURE 20: MiCOM C264 - CPU260 BOARD

FIGURE 21: MiCOM C264 – DSP200 DAUGHTER BOARD ON CPU260

2.5.3 Central Processing Unit and base communications board – CPU270

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

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

2.5.4 Digital Inputs Unit – DIU200

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


• 1 negative or positive common contact for 2 inputs
• All voltages between 24V and 220V DC
• From 48V to 220VDC: High current circulation inside binary contacts inputs during a
short time (to clean external contacts): see the current peak response curve
• With 24Vdc voltage, the high current consumption (>25mA) is permanent
FIGURE 24: MiCOM C264 - DIU210 BOARD

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

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

2.5.7 Digital Outputs Unit – DOU200

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

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

2.5.8 Circuit breaker Control Unit - CCU200

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

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

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

2.5.9 Analogue Input Unit – AIU201

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


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


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

2.5.12 Transducer less Measurements Unit – TMU200/TMU220

The transducers less measurement capabilities are the following:
• 4 measurement Current Transformers (4 CT) inputs
− Transformers have two ranges 1 and 5 amperes
• for the TMU200 4 measurement Voltage Transformers (4 VT) inputs. For the TMU220
5 measurement Voltage Transformers (5 VT) inputs
− AC voltage (VN): 57.73 Vrms to 500 Vrms
• Frequency operating range: 50 or 60 Hz ± 10%
FIGURE 30: MiCOM C264 – TMU200 BOARD

2.5.13 Ethernet Switch Unit – SWU200/SWU202

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

Some jumpers are used to adapt the switch to your network:
Factory
N° Open Closed
setting
W1 No watching port 5 Fault watching Port 5 (Fx) Open
W3 Enable more aggressive Enable less aggressive back-off Open
back-off
W4 Max length is 1536 byte Enable enforce the max frame length for Open
VLAN is 1522
W5 Enable half duplex back Disable half duplex back pressure Open
pressure
W6 Continue sending frame Enable to drop frame after 16 collisions Open
regardless of number of
collisions
W7 Enable flow control Disable flow control Closed
W8 No priority reserve Enable 6KB priority buffer reserved Closed
W9 Half duplex for port 5 (Fx) Full duplex for port 5(Fx) Closed
W10 Unlimited broadcast frames Enable 5% broadcast frame allowed Open
W11 Half duplex for port 6 (Fx) Full duplex for port 6 (Fx) Closed
W12 Enable 802.1p selected by Enable 802.1p field for all port Closed
EEPROM
W13 Share buffers up to 512 Enable equal amount of buffers per port Open
buffers on a single port (113 buffers)
OPEN CLOSE
Port 6
W12
Port 5 (optional)
LED1
LED2
LED3 Port 4
LED4
LED5
Port 3
LED6
W13
W4 Port 2
W3
W5
W6 W8
W7 W9
W10 W1 Port 1
W11
C0118ENa
SWU202 optical links: these 2 optical links are monitored; if one link comes down the default
is announced by the contacts (250V/5A):
Components side Pin State
1 Open
2 Common
1 2 3 3 Close
Close if default
C0119ENa
2.5.14 Ethernet Redundant Switch Unit – SWR202/SWR212, SWR204/SWR214

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

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

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

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

The optical ring is monitored. If one link comes down the default is announced by the
contacts (250V/5A):
1 Default Rp-Es
2 Common
1 2 3 3 Default Rs-Ep
Close if default
C0121ENa
Switch management:
It is possible to manage the switch with the MDIO bus (J6)
Sub D 25 male
J2
8
1 9
MDC 2
3 11
4 18
19
20
21
22
C0122ENa
Ethernet cable type

Use data quality twisted pair shielded cable rated category 5 with standard RJ45 connectors.
The maximum cable length for 10/100BaseT(x) is typically 100 meters.
Ethernet Optical Fibre
The FO cables are connected to the corresponding FO elements.
On the SWR202, the connector type for the multi mode fibre is ST.
On the SWR204 (Ref 2071021 A02 – up to Index B), the connector type for the single mode
fibre is ST.
On the SWR204 (Ref 2071021 A02 – from Index C and upper), the connector type for the
single mode fibre is SC.
Fibre Optic budget calculations
Optical power is expressed in Watts. However, the common unit of power measure is the
dBm and defined by the following equation: Power (dBm) = 10 log Power (mW) / 1 mW.
The following example shows the calculation of the maximum range for various types of
fibres
SWR200 SWR200
1
SWR200 SWR200
Patch Patch
Panel Panel
SWR200 SWR200
C0123ENa
Fibre type Multi mode (SWR202) Single mode (SWR204)

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

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

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

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

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
Example:
Address = 0
Address = 11
OPEN CLOSE
Internal LED:
Some LED are used to indicate the state of the links.
The table below indicates the function of each LED:
LED
FUNCTION DESCRIPTION
number
L1 Receive Link A
L2 Status Link A
L3 Receive Link B
L4 Status Link B
L5 Link and activity port 1 Off: no connection
Green: link
Green + blink: link + activity
L9 Speed port 1 Off: 10Mbps Green: 100Mbps
L10 Speed port 2 «
L11 Speed port 3 «
L12 Speed port 4 «
L13 Number of repeaters detected on the ring bit 0 Only the first 4 bits are visualized
L14 Number of repeaters detected on the ring bit 1 «
L17 Number of repeaters detected on the ring bit 4 Only the first 4 bits are visualized
Fault signal output:

Dual homing links are monitored. If one link comes down the default is announced by the
contacts (250V/5A):
1 Default Link A
2 common
1 2 3 3 Default Link B
Close if default
C0297ENa
Switch management:
It is possible to manage the switch with the MDIO bus (J6).
Sub D 25 male
J2
8
1 9
MDC 2
3 11
4 18
19
20
21
22
C0122ENa
Ethernet cable type

Use data quality twisted pair shielded cable rated category 5 with standard RJ45 connectors.
The maximum cable length for 10/100BaseT(x) is typically 100 meters.
Ethernet Optical Fibre
The FO cables are connected to the corresponding FO elements.
On the SWD202, the connector type for the multi mode fibre is ST.
On the SWD204 (Ref 2071355 A02 – up to index Z), the connector type for the single mode
fibre is ST.
On the SWD204 (Ref 2071355 A02 – from index A and upper), the connector type for the
single mode fibre is SC.
Fibre Optic budget calculations
Optical power is expressed in Watts. However, the common unit of power measure is the
dBm and defined by the following equation: Power (dBm) = 10 log Power (mW) / 1 mW.
The following example shows the calculation of the maximum range for various types of
fibres.
SWR200 SWR200
1
SWR200 SWR200
Patch Patch
Panel Panel
SWR200 SWR200
C0123ENa
Fibre type Multi mode (SWD202) Single mode (SWD204)

Wavelengh:1310nm
62,5/125 micron 9/125 micron
Power coupled into - 19 dBm - 15 dBm
fiber
sensitivity - 31 dBm - 34 dBm
Example 1: between two repeaters
Allowed link attenuation 6,4 dB 13,4 dB
Maximum range 6,4 km 33 km
Example 2: between two repeaters via patch panel
Patch loss (2) 2 dB 1 dB
Allowed link attenuation -0,8 dB 8,2 dB
Maximum range 0 20 km
The values given above are only approximate ones. Always use cable and connector losses
as specified by the manufacturer.
Connecting Dual Homing.
Between 2 Dual Homing SWD20x
Rp LINK A
Rp
LINK A
Es
Es
SWD20x SWD20x
Rs
Rs LINK B
LINK B Ep
Ep
C0298ENa
Between more than 2 Dual Homing SWD20x
Rp LINK A
Rp
LINK A
Es
Es
SWD20x SWD20x
Rs
Rs LINK B
LINK B Ep
Ep
Rp Rp
LINK A LINK A
Es Es
SWD20x SWD20x
Rs Rs
LINK B LINK B
Ep Ep
C0299ENa
2.5.16 Extended communication Unit – ECU200

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

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

2.5.17 Extended communication Unit – ECU201

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

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

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

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

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

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

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

MiCOM C264 uses a standard black MiDOS 28 terminal block for transformer connection.
CT connection has 2 dual terminal groups, this allows dual rated transformer (1A/5A). Each
group has shorting contact to allow disconnection of CTs without damage.
The CT/VT connector block characteristics are the following:
Parameter Value
VT connection
3 second rating 30 A
30 ms rating 250 A
Cable size 2 off 2.5 mm2
CT connection
Cable size 2 off 2.5 mm2 / 1 off 4 mm2
TABLE 2: CT/VT CONNECTOR BLOCK
1 2
3 4
5 6
7 8
9 10
11 12
13 14
15 16
17 18
19 20
21 22
23 24
25 26
27 28
C0042ENa
FIGURE 2: STANDARD MIDOS 28 CONNECTOR

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

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

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

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

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

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

NOTE: The “Daisy Chain or “straight line” configuration is recommended and
the correct way to construct fieldbus.
MiCOM C264 MiCOM C264 (Slave) (Slave) (Slave)

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

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

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

WARNING ABOUT LASER RAYS:
Where fibre optic communication devices are fitted, these should not be viewed directly.
Optical power meters should be used to determine the operation or signal level of the device.
Non–observance of this rule could possibly result in personal injury.
Signals transmitted via optical fibres are unaffected by interference. The fibres guarantee
electrical isolation between the connections.
If electrical to optical converters are used, they must have management of character idle
state capability (for when the fibre optic cable interface is "Light off").
2.5 Ethernet-based communications connections

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

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

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

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

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

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

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

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

C0049ENd
FIGURE 9: SECOND EXAMPLE OF CABLE FITTING

4. CONNECTION DIAGRAMS FOR EACH I/O BOARDS

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

1 RS232 RS232
2 RS232 RS485
3 RS422 RS232
4 RS422 RS485
5 RS485 RS232
6 RS485 RS485
TABLE 3: BASE LEGACY PORTS (PORTS N°1 / N°2) - CAPABILITIES

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

4.1.2 Block diagram
Power auxiliary supply BIU241/

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

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

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

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

NOTE: In this case, the GND signal of the daisy chain extremity is not to be
earthed.
4.1.3 BIU wiring for redundant C264
In case of C264 redundancy, the following signals are to be wired for the management of the
main/ backup redundancy:
C264_1 C264_1 C264_2 C264_2

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

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

The external modules ECU200/ECU201 convert non-insulated RS232 into optical
link/insulated RS485 or RS422.
The DB9 connectors description:
1 CD
2 RX
3 TX
4 5V ( for ECU20x supply)
5 ground
6 Not used
7 RTS
8 CTS
9 Not used
NOTE: Unlike standardized RS232 connector, pin 4 is not normally used as

the DTR signal (Data Terminal ready). It is here permanently
connected to power supply +5 V. So this pin 4 must not be used in a
null-modem cable.
Connector DB 9
5
1
6 9
1
5
9 6
C0152ENa
FIGURE 11: OPTIONAL LEGACY PORTS (PORTS N°3 / N°4) - DESCRIPTION

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

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

4.3 Digital Inputs module – DIU200

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

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

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

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

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


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

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

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

Pin N°. Signal

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


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

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

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

Pin N°. Signal

1 Digital Input 1-
2 Digital Input 2-
3 Positive Common Digital Input 1 / 2
4 Digital Input 3-
5 Digital Input 4-
7 Digital Input 5-
8 Digital Input 6-
10 Digital Input 7-
11 Digital Input 8-
13 Digital Input 9-
14 Digital Input 10-

4.6 Digital Outputs module – DOU200

The Digital Outputs Unit (DOU200) board provides 10 outputs (10 DO) using relays.
4.6.1 Block diagram
D igital Output U nit DOU200

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


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

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

4.7 Circuit breaker Control Unit - CCU200

The Circuit breaker Control Unit (CCU200) board provides 8 digital inputs (8 DI with one
common for 2DI) and 4 double pole outputs (4 DO) using integrated relays.
4.7.1 Block diagram
Circuit breaker CCU 200

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

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

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

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

4.8 Analogue Input module – AIU201

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

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


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

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

4.9 Analogue Input module – AIU210/AIU211

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

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

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

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


Pin N°. Signal

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

Pin N°. Signal

2 Analogue Input 5- (current)
5 Not Connected
6 Ground
11 Not Connected
12 Ground
17 Not Connected
18 Ground
23 Not Connected
24 Ground

4.10 Transducerless Measurements Unit module –TMU200

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


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

1 Current Input 5A - N1
2 Current Input 5A – N2
5 Current Input 5A – C1
9 Current Input 5A – B1
13 Current Input 5A – A1
17 NC
18 NC
19 NC
20 NC
21 Voltage Input – U1
22 Voltage Input – U2
23 Voltage Input – V1
24 Voltage Input – V2
25 Voltage Input – W1
26 Voltage Input – W2
27 Voltage Input – N1
28 Voltage Input – N2
TABLE 14: TMU200 BOARD - CONNECTOR DESCRIPTION

4.11 Transducerless Measurements Unit module –TMU220

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


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

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

4.12 Ethernet Switch Unit - SWU200/SWU202

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

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

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

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

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

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

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

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

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

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

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

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

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

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

BLANK PAGE
Human Interface C264/EN HI/C40
MiCOM C264/C264C
HUMAN INTERFACE
CONTENT
2. THE FRONT PANEL 4

2.1 Overview 4
2.1.1 LED’s management 5
2.2 Technical limits and performances 6
2.3 Configuration data 6
2.3.1 General display management 8
2.3.2 Language support 9
2.3.3 Time and date displaying 9
2.3.4 Bay panels 10
2.3.5 Events panel 16
2.3.6 Faults panel 17
2.3.7 Alarms panel 18
2.3.8 Disturbance records panel 19
2.3.9 Configuration panel 20
2.3.10 Display of binary input information 25
2.3.11 Display of binary output information 26
2.3.12 Menu tree 27
2.3.13 Controls 29
2.3.14 Password management 35
3. THE COMPUTER MAINTENANCE TOOL 36
4. THE EMBEDDED MAINTENANCE WEB SERVER 37
5. THE PRINTER 38
5.1 Inputs 38
5.2 Outputs 38
5.3 Printer management 39
5.3.1 Header & footer 39
5.3.2 Chronology & time stamp 39
5.3.3 Printer out of service 39
5.3.4 Circular FIFO management 39
C264/EN HI/C40 Human Interface
BLANK PAGE

This document is a chapter of MiCOM C264 documentation binders. It describes the three
User Interfaces (coded HI for Human Interface) of this computer:
• The Front Panel ( FP)
• The Computer Maintenance Tool ( CMT)
• The Printer
2. THE FRONT PANEL

2.1 Overview
The MiCOM C264/C264C front panel exists in two versions:
• A simple FP with LEDs, L/R push-button and the serial link ( GHU21x)
• A graphical FP with LEDs, L/R push-button, the Local Control Display and the serial
link ( GHU20x)
LEDs
Key-pad
Local/Remote
Graphical push-button
LCD
RS 232 Serial port
C0020ENc
FIGURE 1: MiCOM C264C FRONT PANEL (GHU20X)

The FP is detachable up to 5 meters from the MiCOM C264/C264C base case using a
specific front panel (GHU22x)
From the graphical panel, the operator can
Control:
• circuit breaker (open, close)
• disconnecting switch (open, close)
• transformer (raise, lower, go to min, go to max)
• generic command (start, stop or open/close)
• setpoint
• Bay mode (local/remote)
• Computer mode (operational, test, maintenance)
• counters value
Switch the database
Modify Settings by menu tree
Acknowledge and clear alarms
Suppress datapoints
Display:
• Device position
• Alarms list
• Disturbance record
• Configuration
• Events list
• Fault list
• Measurements, counter, and TPI
• Physical binary input/output,
• Status information
• Bay mode (local/remote, SBMC)
• Bypass indications
• Setting points
• Board state
• IED state
Activate LED depending on datapoint status
2.1.1 LED’s management
The first 5 LEDs indicate the MiCOM C264/C264C status information. The LEDs indicate
from top to down:
LED id Colour LED on LED slow blinking LED fast blinking LED off
1 Red There is at least one There is at least one Not used There is no
major fault minor fault (I/O board, fault
(hardware, database) communication to IEDs,
…)
2 Yellow All the alarms are All alarms displayed in There is at least one There is no
acknowledged, but the alarm panel are not acknowledged alarm
there is at least one inactive and alarm displayed in
alarm still active. 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 only Red All bays managed by Bays managed by the Not used All bays
for without the computer are in computer are not in the managed
LCD panel: LOCAL mode same control mode by the
GHU2x1) computer
are in
REMOTE
Major fault: MiCOM C26x not available due to internal major fault (database error, CPU
watch-dog, …).
A minor fault is a fault causing only the non-availability of a part of the functionality.
When the alarm disappears, the LED returns automatically to OFF.
Table explaining the fixed LEDs for the Full DHMI:
LED id Colour LED on LED slow blinking LED fast blinking LED off
1 Red Fault There is at least one There is at least one Not used
major fault (hardware, minor fault (I/O
database) board,
communication to
(1) IEDs, …)
(2)
2 Yellow Alarm All the alarms are All alarms displayed There is at
acknowledged, but in the alarm panel least one
there is at least one are inactive and not
alarm still active. acknowledged acknowled
ged alarm
(3) displayed
in the
alarm
panel
3 Yellow Mode Computer in service Computer in Computer
maintenance in test
4 Green Power Power up is present Not used Not used
(1) Major fault: MiCOM C26x not available due to internal failure (database error, CPU
board failure, …).
(2) A minor fault is a fault causing only the non availability of a part of the functionality.
(3) When the alarm disappears, the LED returns automatically to OFF.
The other red LEDs (12 or 13) available on front panel can be attached to a Binary Input (BI).
An information which requires a LED’s display is defined in database during configuration
phase.
Change of state of such information causes change on LED’s display.
The 4 states of the LEDs can be affected to the different states of the BI.
2.2 Technical limits and performances
There are 17 LEDs available with 16 are managed by the software. One is directly
connected to the internal power.
2.3 Configuration data
The behaviour of the free LEDs is defined in the computer DataBase.
When using a Simple DHMI, the 12 free LEDs give the status of the associated BI. Each BI
state is displayed using the ON / OFF / BLINKING led state (defined in the DS).
When using a Full DHMI (with LCD), the 13 free LEDs can be configured to have 2 different
behaviours:
1. give the status of the associated BI. Each BI state is displayed using the ON / OFF /
BLINKING led state (same way as with a Simple DHMI),
2. provide a way to manage BIs as alarms.
This behaviour B is detailed hereafter :
• if the BI is “transient”:
− if the BI is SET, the associated LED is ON or Blinking Slow (depends of the DB),
− after pressing the ‘C’ button, the LED’s state becomes OFF (without any
password).
• if the BI is “permanent”:
− if the BI is SET, the associated LED is Blinking Slow,
− after pressing the ‘C’ button, the LED’s state becomes ON (without any
password),
− if the BI is RESET, the associated LED remains Blinking if the ‘C’ button has not
been pressed or is OFF if it has.
Phenomenon LED status Possible reason Way to solve

Functions as All LEDs are OFF The cable between Verify the connection
communication, CPU and GHU2xx, or between CPU or
automation, printing are GHU2xx itself is not GHU2xx.
well operating and the operational
If connection is OK
watch dog on BIU is
and the problem is
SET.
not already solved
then change the
GHU2xx board.
The supply is ON and All LEDs are OFF Problem with BIU Replace BIU board or
the watch dog on BIU board or CPU board CPU board.
is RESET.
C264 is not running or LED1 ON Incoherent database Download a coherent
not fully operational database
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
disconnected and verify that paper
is available, the
printer is switch ON,
the printer cable.
A problem about clock Go into Fault panel
synchronisation and 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
(ISaGRAF) and connect the
ISaGRAF workbench
to the C264. Verify
the behaviour of the
PLC.
The 12 other LED’s are freely configurable: they can be attached to a datapoint.
Furthermore, the datapoint state is displayed through a led state: on, off, slow blinking, fast
blinking.
For a Single Point, the Set / Reset / Invalid (i.e. all other states) can be attached to a led. For
a Double Point, the Open / Close / Invalid (i.e. all other states) can be attached to a led.
2.3.1 General display management
The computer local HMI is composed of several “panels” and one “menu tree”. The panels
allow to display information, the menu tree allows to display and modify computer settings.
There are 7 main groups of panels, each group can have several kind of panel.
The key allows to display the next panel, the key allows to display the
previous one.
From each panel, the key allows the menu tree access.
The keys and allows to access to the different panels of a group.
List of panel groups

Group 1: graphical – one or two panels for each bay with sub panel for:
• Measurement, counter and TPI
• Single, double and multiple datapoints status
• controls
Group 2: alarm - one panel to display the alarm list and allow acknowledgement and
clearing
Group 3: event - one panel to display the event list
Group 4: fault - one panel to display the fault list
Group 5: disturbance - one panel to display the header of the disturbance file
Group 6: computer information - one panel to display general information, one panel to
display the boards state, one panel to display the IEDs state
Group 7: physical - one panel to display the state of the physical inputs, one panel to
display the state of the physical outputs
GBP 1 alarm event fault disturbance service input
GBP 2 board output
IED
GBP 12
Panel accessible in Maintenance mode
C0153ENa
FIGURE 2: GROUPS MANAGEMENT

From any panel, an help panel is accessible using the key c . From this panel, a new
press on help key allows to display the graphical panel of the first bay in active mode or the
service panel in maintenance mode.
2.3.2 Language support
The displaying on the LCD supports 2 languages that are chosen during configuration
phase. A parameter in the menu tree allows to switch between both languages.
2.3.3 Time and date displaying
Local HMI displays time, date and state of time and date of the computer.
Time: time of day is displayed in all the panels of the LCD. For each panel, time of day is
displayed in the first line of the panel.
The displaying format of the time is THH:MM:SS where T is the time state, HH the hour (0
to 23), MM the minutes (00 to 59) and SS the seconds (0 to 59).
12 characters 1 char 8 characters
P A N E L _ N A M E T H H : M M : S S
C0154ENa
FIGURE 3: TIME DISPLAY

In the events panel, in the alarms’ panel and in the disturbance records panel, time stamp
must be given at milliseconds. So, the format of time is THH:MM:SS.MMM
Date: date is displayed only in the panel of events and in the panel of alarms . Date is
associated with time for the displaying of each event and each alarm.
3 displaying formats for date are configurable, where DD is the month day (01 to 31), MM the
month (01 to 12) and YY the year (00 to 99):
DD/MM/YY
MM/DD/YY
YY/MM/DD
State of date and time: the application software of the computer manages the different
state of the date and time:
not synchronised (“*”): the date/time has never been synchronised
synchronised (“ “): date/time is synchronised
Time, date and state are visible and modifiable in the menu tree. To modify time or date,
refer to ST chapter.
2.3.4 Bay panels

Graphical representations of bays are visible in panels. Each bay has its own panels (up to
2). Up to 12 bays can be displayed via the front Panel of the computer. A maximum of 9
devices can be displayed on a per panel basis..
All information of these panels are configurable excepted the time indication.
Bay Bay Bay

Panel 1 Panel 2 Panel n
Key 4 Key 4 Key 4
…
Key 4
Key 3 Key 3 Key 3
…
Key 3
Key 2 Key 2 Key 2

…
Key 1
Key 1 = page key :
Key 2 = enter key :

Menu tree
Key 3 = cursor left key :
Key 4 = cursor right key :
C0155ENa
FIGURE 4: BAYS MANAGEMENT

When a bay is displayed on two panels, key4 and key3 are used to move from one panel to
the other.
For one bay:
Graphical Bay Panel Help

sub-panel
Measurement Control State Bypass Interlock

sub-panel sub-panel sub-panel sub-panel sub-panel
C0156ENa
FIGURE 5: BAY MANAGEMENT (CONT'D)

Information displayed in the bay panel is:
• the bay name (fixed position)
• the time (hh:mm:ss) and its status
• the bay graphical representation: the bay is displayed in single-pole presentation.

Graphical pictures are made of bitmaps for devices representation, vertical and
horizontal lines and labels.
• the SBMC mode
• the Local / Remote bay mode
• the synchrocheck bypass activation, if exists
• the interlock bypass activation, if exists
• a measurement of CT/VT displayed on a vertical graphical bargraph (Vertical

Measurement Graphical Area) or on a horizontal graphical bargraph (Horizontal
Measurement Graphical Area). VMGA and HMGA are exclusive. Only CT/VT
measurements can be displayed on a bargraph. Up to four CT/VT measurements can
be associated to a bargraph. Buttons and allow to select the

measurement to display on the bargraph. The totality of the bargraph represents either
120% or 200% of the nominal value.
• the name of the measure (fixed position)
• the value of the measure (fixed position)
• the command report (fixed position)
• the access to datapoints panels

Example:
Name of the bay
*hh :mm :ss

time and its status
graphical representation
SBMC DPS1
SBMC mode
local/remote mode L/R
interlock bypass EQL BP
synchrocheck bypass S/C BP
vertical bargraph
DPS2
measure value value horizontal bargraph

measure name measure name
command report message message M S C
access to the measurement panel

access to the state panel
access to the command panel
C0300ENa
FIGURE 6: EXAMPLE OF A BAY PANEL

2.3.4.1 State sub-panel

This panel allows to display the state of the digital datapoints (single points, double points
and multiple points).
3 lines are necessary to display any information.
S T A T E <state of the time> <time>

B A Y i
SPS, DPS or MPS 1 (3 lines)
SPS, DPS or MPS 4 (3 lines)…
A SPS / DPS / MPS is defined by:
<Label of the datapoint > = 16 characters maximum

Module of the BI = 16 characters maximum
State of the BI = 21 characters maximum
From this panel, the operator can suppress a datapoint.
S T A T E * 1 2 : 3 4 : 5 6
C 2 6 4 P
D B i n c o h . S P S
C 2 6 4 P
R e s e t
S L o c a l / r e m o t e D P S
R e m o t e
G o s M s g
S e l f c h e c k f a u l t
M o d u l e D P S
G e n e r a l
J a mm e d
1 / 5
S T A T E * H H : MM : S S
C 2 6 4 P
M o d u l e S P S
G e n e r a l
S e t
L o c a l / r e m o t e D P S
L o c a l
S B MC S P S
R e s e t
D S 1 s w g r p o s .
D S 1
C l o s e d
2 / 5
FIGURE 7: EXAMPLES OF STATE SUB-PANELS
2.3.4.2 Measurements, counters and TPI sub-panel

This panel allows displaying the state of the measurement, the counter and the TPI. It is
defined by 3 lists of element (Measurement , counter and TPI), each list is composed of
several pages (3 information per page).
M E A S C O U N T <state of the time> <time>

B A Y i
Measurement 1
Measurement 2
Measurement 3
…
Display of measures
Analogue values or digital measurements can be displayed in this panel if defined in
database. The value is displayed with 2 digit after the dot and 5 before.
<Label of the meas > = 16 characters maximum

Module of the measurement = 16 characters maximum
Value: 7 char Unit (5 char)
State of the meas = 21 characters maximum
Display of counter
Counter can be displayed in this panel if defined in database. The value is displayed with 2
digit after the dot and 5 before.
<Label of the counter > = 16 characters maximum

Module of the counter = 16 characters maximum
Value: 7 char Unit (5 char)
State of the counter = 21 characters maximum
Display of TPI
TPI can be displayed in this panel if defined in database.
<Label of the tpi > = 16 characters maximum

Module of the counter = 16 characters maximum
Value: 3 char
State of the tpi = 21 characters maximum
From this panel, the operator can suppress a measurement or a TPI (unavailable function for
the counters).
M E A S C O U N T
C 2 6 4 P
T e m p 1
M E A S
U n d e f i n e d
_ _ _ _ _ _ _ _ _ _ _ _ _
T e m p 2
M E A S
U n d e f i n e d
1 / 1
M E A S C O U N T
C A L C U 1
M V
D a t a p o i n t s C 1
U n k n o w n
M V 1
U n k n o w n
M V 2
U n k n o w n
1 / 2
FIGURE 8: EXAMPLES OF MEASUREMENTS SUB-PANELS
2.3.4.3 Controls sub-panel
The operator is allowed to control devices from the controls sub-panel.
The commands are displayed as following:
Name of the control

Name of the module
state Label order
On this panel, the operator selects the chosen command using the key .
SBO and DE controls are possible according to the configuration
and .for OFF and ON

To send a DE control,, operator uses keys
To send a SBO control, operator uses keys and .to select OFF or ON. Then
the execution is sent using key.
The current state is displayed on the third line (only ON or OFF).

The button allows to abort the control.

C O M M A N D <state of the time> <time>
N A M E O F T H E B A Y
Command 1
Command 2
Command 3
Command 4
Page
C OMM A N D
C A L C U 1
D P C 1
ON O r d e r O p e n
K l a x o n
S B MC c o n t r o l S P C
O f f O r d e r O n
1 / 2
C OMM A N D
C A L C U 1
S e t P o i n t
+ 0 0 0 0 6 . 0 0
2 / 2
FIGURE 9: EXAMPLES OF CONTROL SUB-PANELS
2.3.4.4 Interlocking sub-panel
When a module is selected in the graphic bay panel, the button c allows to access to
the interlocking panel. Any button allows to leave this panel and come back to the graphic
bay panel.
This panel displays the interlocking equation result (TRUE / FALSE) associated to a device
control.
C O N D I T I O N S <state of the time> <time>
< Label of the device > = 16 characters
E Q L O P E N : state
E Q L C L O S E : state
E X I T
2.3.5 Events panel

The event panel allows to display the event list of the computer in a chronological order.
Display of events is done from newest to oldest: that means that the newest event declared
is displayed at the top of the events panel (i.e. newest event is always rank 1).
This event list is a circular queue. List maximum size depends of computer version series.
This list is displayed in a scrollable view using arrows buttons. When the circular queue is full
and a new event appears, then the rank of each event is increased and the oldest event in
the queue is removed.
One screen of the LCD contains at maximum 2 events.
At first time the user enters the events’ panel, the 2 newest events are displayed.
E V E N T <state of the time> <time>

0 0 1 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯
<Date, time and state of time of the event> =21 char.
<Information about event>
5 lines * 21 char./line maximum:
0 0 2 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯
<Date, time and state of time of the event> =21 char.
<Information about event>
5 lines * 21 char./line maximum
An event is composed of 7 lines:

Line 1: rank of the event in the circular queue
Line 2: event time stamp
Line 3: label of the bay
Line 4: label of the module
Line 5: label of the datapoint
Line 6: state of the datapoint
Line 7: value and unit of the datapoint (if exists)
Display mechanism for the first page:
• If the operator visualises the first page, it is assumed that he is looking for the newest
events. Therefore, the page will be updated at the apparition of any new event.
Display mechanism for an intermediate page:
• The operator visualises one page between the first page and the last one, it is
assumed that he examines more precisely these events.
• Therefore, when n events appear, the user keeps visualising the 2 same events.
However, the rank of each event is incremented by n in real time in the list. When the
displayed event is removed from the FIFO, the oldest event is displayed.
Display mechanism for the last page:
• Last page means visualisation of the two oldest event of the FIFO and the FIFO is full.
When the displayed event is removed from the FIFO, the new oldest event is
displayed.
E V E N T * 1 2 : 3 4 : 5 6
0 0 1 - - - - - - - - - - - - - - - - - -
0 6 /M 0 5 / 10 2 * 1 1 : 2 2 : 3 3 . 1 2 3
C 2 6 4 P
C 2 6 4 P
L o c a l / r e m o t e D P S
R e m o t e
0 0 2 - - - - - - - - - - - - - - - - - -
0 6 /M 0 5 / 10 2 * 1 1 : 2 2 : 3 3 . 5 6 7
C 2 6 4 P
C 2 6 4 P
I S A G R A F s t a t u s
WA I T I N G
0 0 1 / 10 0 0
FIGURE 10: EXAMPLE OF EVENT SUB-PANEL
2.3.6 Faults panel
The first LED of the local HMI indicates 2 levels of fault.
When the LED is ON, a major fault is present. It can be:
• A database incoherence
• A hardware fault
If there is a minor fault the fault LED is blinking. It can be:
• A disconnected IED
• A problem about IRIG-B
• A problem about ISaGRAF

The Fault panel displays these faults.
2.3.7 Alarms panel

Alarms are displayed in the form of one list in the panel. This list is a circular buffer and is
displayed in a scrollable view in the same way as for the events panel.
One screen of the LCD can contain a maximum of 2 alarms:
A L A R M <state of the time> <time>
<Date, time and state of time of the last alarm state change > =21 char.
<State of the alarm>=19 char. Max. Gr
<Information about event that generate
the apparition or the state change of the alarm>
5 lines * 21 char./line maximum.
<Date, time and state of time of the last alarm state change > =21 char.
<State of the alarm>=19 char. Max. Gr
<Information about event that generate
the apparition or the state change of the alarm>
5 lines * 21 char./line maximum
An alarm is composed of 7 lines:

Line 1: alarm apparition time stamp
Line 2: alarm state and gravity
Line 3: label of the bay
Line 4: label of the module
Line 5: label of the datapoint
Line 6: state of the datapoint
Line 7: value and unit of the datapoint (if exists)
Alarms acknowledgement and clearing is defined in “Controls” chapter.
A L A R M * 1 2 : 3 4 : 5 6
0 6 /M 0 5 / 0 4 * 1 1 : 2 2 : 3 3 . 1 2 3
I N C T A C T U N A C K A L 1
C 2 6 4 P
D S 1
D S 1 C t r l D P C
S e l e c t e d
K O - i n t e r l o c k
0 6 /M 0 5 / 0 4 * 1 1 : 2 2 : 3 2 . 4 5 6
A C T U N A C K A L
C 2 6 4 P
C 2 6 4 P
G o s M s g
R e s e t
0 0 1 / 0 0 2
A L A R M 0 1 : 0 2 : 0 3
0 6 /M 0 5 / 0 4 * 1 1 : 2 2 : 3 3 . 7 8 9
A C T U N A C K A L
C A L C U 1
S P S 7
R e s e t
0 6 /M 0 5 / 0 4 * 1 1 : 2 2 : 3 1 . 9 6 3
A C T U N A C K A L
C A L C U 1
S P S 7
R e s e t
0 0 1 / 0 1 6
FIGURE 11: EXAMPLE OF ALARM SUB-PANEL
2.3.8 Disturbance records panel
Display of disturbance records corresponds to the list of available disturbance records of the
computer. Two types of files are managed:
• Disturbance file from an IED
• Waveform computed inside the C264
D I S T U R B . <state of the time> <time>

FileName ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯
<Record beginning date, time and state of time > =21 char.
<Information about event that causes the recording>:
2 lines * 21 char./line maximum for computer waveform record
Name of the IED for IED disturbance record
FileName ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯
<Record beginning date, time and state of time > =21 char.
The records are displayed on the panel using 2 lists according to the origin. Displayed
information depend on the origin of the file:
• waveform records are in COMTRADE format, 3 files can be displayed per page. Only
the .cfg file name is displayed on the panel (the .dat files are only available to be
uploaded).
Name of the file (format name . cfg) Type (F,S)

Time stamp
Bay Name / Module Name / Datapoint label (up to 2 lines)
(F for fast waveform, S for slow waveform)
• From an IED: 3 files can be displayed per page.
Name of the file (format name . ext)

Time stamp
Name the IED
2.3.9 Configuration panel

The configuration panel allows to display several panels concerning the computer itself:
• Board panel
• External devices panel
• Service information panel
Board Ext. device Service Information

panels panels panel
Key 4 Key 4 Key 4
Key 3 Key 3 Key 3
Key 2 Key 2 Key 2
Key 1
Key 1 = page key :
Key 2 = enter key :

Menu tree Key 3 = cursor left key :
Key 4 = cursor right key :
C0158ENa
FIGURE 12: CONFIGURATION PANELS MANAGEMENT

2.3.9.1 Boards panel

Board’s list view is a text list containing the status of I/O boards.
For each board, the following informations are displayed in one line of the board panel:
• its type,
• its state among the following ones: OK (Board connected and operational), MISSING
(Board missing), FAILURE (Board in fault), TOO MANY (Board present but not
configured).
B O A R D * 1 2 : 3 4 : 5 6
board label B I U
board status O k
G H U 2 0 0
O k
D I 0
O k
D I 1
O k
D I 2
O k
D I 3
O k
1 / 2
B O A R D * 1 2 : 3 4 : 5 7
D O 0
O k
D O 1
O k
D O 2
O k
D O 3
O k
A I U 2 1 0
O k
A I U 2 1 0 1
O k
page number 2 / 2
number of pages
C0301ENa
FIGURE 13: EXAMPLE OF BOARDS SUB-PANEL

2.3.9.2 External devices panel

This panel display all external devices connected to the computer by a legacy protocol and
by the IP protocols (as IEC61850). This panel contains 3 sub sets:
• IP client connection number: it defines the number of client currently connected to the
computer.
• IP server connection state: it defines the list of the server connected to the computer.
Each server is displayed with its name, its IP address, and the state of its connection.
server name
IP address state
• Legacy protocol connection state: each IED is displayed with its name, its address,
and the state of its connection.
IED name
address state
The panel for “IP IED” is as follows:
E X . D E V I C E S <state of the time> <time>
I P C L I E N T N B :
I P S E R V E R : protocol
Server 1
Server 2
Server 3
page
The panel for “Legacy IED” is as follows:
E X . D E V I C E S <state of the time> <time>
L E G A C Y D E V I C E protocol
IED 1
IED 2
IED 3
IED 4
page
I E D * 1 2 : 3 4 : 5 6
I P C L I E N T N B : 0 0 0
S C A D A I E D
T 1 0 1 D I S C O N N
0 0 1 / 0 0 2
I E D * 1 2 : 3 4 : 5 7
I E D s : T 1 0 3
P 4 4 2 _3 3
0 0 3 D I S C O N N
P 6 3 2 _4 4
0 0 4 D I S C O N N
P 1 3 9 _ 2
0 0 2 D I S C O N N
P 1 2 7 _ 1
0 0 1 D I S C O N N
0 0 2 / 0 0 2
FIGURE 14: EXAMPLE OF EXTERNAL DEVICES PANEL
2.3.9.3 Service information panel

The local control panel is able to present computer related information on several views:
• serial number of computer
• software version
• version’s number and revision’s number of the first database
• version’s number and revision’s number of the second database
• state of both database
• operating hours of MiCOM computer
• operating modes
• redundancy mode
S E R V I C E * 1 2 : 3 4 : 5 6
S E R I A L N B
0 0 0 0 3 9 6 2
S O F T WA R E V E R S I O N
A 4 . 3 1 A
D B 1 V E R S I O N S T A T E
0 . 3 A C T I V E
D B 2 V E R S I O N S T A T E
N O B D
O P E R A T I N G H O U R S
6 0 1
O P E R A T I N G MO D E
O P E R A T I O N A L
R E D U N D A N C Y MO D E
N O T R E D U N D E
FIGURE 15: EXAMPLE OF SERVICE INFORMATION PANEL
2.3.10 Display of binary input information

The state of the physical binary input can be displayed in the “binary input panel”. The
operator defines (with the SCE) a list of binary input displayed in this panel among all binary
input defined in the computer.
Each panel contains:
• The board number and its type (DIU, CCU)
• A list of binary input defined by:
− The input number: DI xxx
− The state of the physical input with 3 possible values (On, off , fault)
E T O R <state of the time> <time>
B O A R D X X Board type
D I X X X value D I X X X value
E T O R * 1 2 : 3 4 : 5 6
board number
B O A R D 0 D I U
board type
D I 0 O N D I 8 O N
D I 1 O F F D I 9 O F F
D I 2 O N D I 1 0 O N
D I 3 O F F D I 1 1 O F F
D I 4 O N D I 1 2 O N
D I 6 O N D I 1 4 O N
input number
input status
1 / 4
C0302ENa
FIGURE 16: EXAMPLE OF BINARY INPUT SUB-PANEL

2.3.11 Display of binary output information

The state of the physical binary output can be displayed in the “ binary output panel”. The
operator defines (in the menu tree) a list of binary output displayed in this panel among all
binary output defined in the computer.
Each panel has:
• The board number and its type (DOU, CCU)
• A list of binary output defined by:
− The output identifier: DO xxx
− The state of the physical output with 3 possible values (on,off,fault)
S T O R <state of the time> <time>
B O A R D X X
D O X X X value D O X X X value
S T O R * H H : M M : S S
board number
B O A R D 0 D O U
board type
D O 0 O N D O 8 O N
D O 1 O F F D O 9 O F F
D O 2 O N
D O 3 O F F
D O 4 O N
D O 5 O F F
D O 6 O N
D O 7 O F F
output number
output status
1 / 4
C0303ENa
FIGURE 17: EXAMPLE OF BINARY OUTPUT SUB-PANEL

2.3.12 Menu tree

Some parameters of the computer can be set by the operator from local HMI. The display /
modification of the parameter value is done in the menu tree from the local HMI. All the
parameters are group in the same path of the menu tree.
The parameters that can be modified on-line are:
• language
• counters value
• synchrocheck parameters
• autorecloser parameters
• pulse delay for open / close controls
• motion 00 and motion 11 delays
• persistence filtering delays
• toggling parameters
• measurements thresholds, deadband and hysteresis
• serial communication parameters

The controls that can be performed from the menu tree are:
• reset of operating hours
• change of computer operating mode
• global alarm acknowledgement
• global alarm clearing
• database switching
• date and time setting
• modify counters value
• modify energy counters value

The following figures show the menu tree in the three operating modes.
root
COMMAND MAIN RESET OP HOURS

CHANGE MODE OP
GLB ACK ALARM
GLB CLR ALARM
DATE
TIME
DB SWITCH
LANGUAGE
COUNTER
CONFIG COMPUTER MAIN IP ADDRESS
BAY (name of bay) INTERNAL S/C
AR
DEVICE (name of device 1) TIME OPEN

TIME CLOSE
(name of device i) TIME OPEN
TIME CLOSE
BI ( name of BI 1) MOTION 00 FILT

MOTION 11 FILT
PERS CLOSE FILT
PERS OPEN FILT
TOGGLING OPTION
( name of BI i) MOTION 00 FILT

MOTION 11 FILT
PERS CLOSE FILT
PERS OPEN FILT
TOGGLING OPTION
MV ( name of MV 1) HYSTERESIS
DEADBAND
THRESHOLD1
THRESHOLD2
THRESHOLD3
THRESHOLD4
THRESHOLD5
THRESHOLD6
( name of MV i) HYSTERESIS
DEADBAND
THRESHOLD1
THRESHOLD2
THRESHOLD3
THRESHOLD4
THRESHOLD5
THRESHOLD6
COMM. PORT COMM. PORT 4 BAUDRATE

PARITY
STOP BIT
NB BIT PER CHAR
HMI MAIN EXIT MT TIME
BACK LIGHT DELAY
SELECT EXIT TIME
PASSWORD
BYPASS DELAY
BAY (name of bay) DISPLAY DEV NAME

C0304ENa
FIGURE 18: MENU TREE IN OPERATIONAL AND TEST MODES

root
COMMAND MAIN CHANGE MODE OP

DATE
TIME
DB SWITCH
CONFIG COMPUTER MAIN IP ADDRESS
HMI MAIN EXIT MT TIME

BACK LIGHT DELAY
SELECT EXIT TIME
PASSWORD
BYPASS DELAY
C0305ENa
FIGURE 19: MENU TREE IN MAINTENANCE MODE
2.3.13 Controls
Some controls can be performed from the local HMI:
• Bay Local / Remote mode
• Control of circuit breakers or disconnecting switches
• Tap changer control
• Computer mode
• Database switch
• Reset of operating hours
• Time and date setting
• Manual reset/modification of counters and energy counters
• Alarms acknowledgement
• Alarms clearing
Some of these commands are accessible in a panel (bay panel or alarm panel), the others
are accessible in the menu tree. Some controls are protected either by the bay local mode or
by a password.
The following table sums up the protection rules and the accessibility of the controls:
Local Control Protection

Local / Remote control of bay Protected by a password (optional)
X Device command Not protected by a password.
But protected by the password of
command 1 if it exists
Computer mode Protected by a password
Data Base switch Protected by a password
Reset operating hours Protected by a password
Time and date setting Protected by a password
Manual reset of counters Protected by a password
Alarms Acknowledge Protected by a password
Alarms clearing Protected by a password
2.3.13.1 Local / Remote control of bay

Local / Remote control of bay for LCD front panel (GHU20x)
The operator is allowed changing the bay mode:
• From local to remote
• From remote to local

If the computer manages several bays, the state local / remote of bays is set bay by bay.
Change of bay mode is enabled if a bay panel is defined. It means that, if a bay is not
associated to a bay panel, its local/remote control mode cannot be controlled through the
L/R button of the panel.
Switch from the state remote to local can be protected by a password.
Switch from the state local to remote is not protected.
Local / Remote control of bay for simple panel with LEDs (GHU21x)
In case of simple panel, the operator controls all the bays of the computer in the same time.
To change mode, he has to press of the button during at least 3 seconds. No password is
necessary to check the control. A LED is necessary to display the current mode, so the 5th
LED is required for that. If all the bays are NOT in the same state, the command will switch
them all to local mode.
2.3.13.2 Commands of circuit breakers, disconnecting switches and generic devices
Device command is possible by 2 ways:
• From the graphical panel
• From the sub panels command

Circuit breakers, disconnecting switches or generic command are ordered from the local HMI
by the operator. Commands allowed from the local HMI are:
• open
• close
• close a synchronised circuit breaker
• close with bypass on a synchronised circuit breaker (forcing closure), available only
when the DI “Accept Forcing is configured))
SBO command
In case of the select/execution order (SBO) for opening or closing a module, the operator
has to make on the local HMI a selection before an execution command.
For that, operator presses the command button (button for OFF or button for
ON) a first time for the selection command, and presses button for the execution
command.
After a positive acknowledgement of the selection command, the device is displayed in video
inverted.
DE command
In case of the Direct execute order (DE) for opening or closing module, the operator send
directly the command using the command buttons.
Interlocking and Synchrocheck bypass

In both previous cases, operator can send the command using bypass flag on:
• interlocking equation
• synchrocheck (forcing closure)

The interlocking bypass is set before the execute order sending.
The S/C bypass flag is optional (it is present when the “Accept Forcing” DI is configured).
The S/C bypass flag can be set before or after the execute order sending.
Operator accesses to the bypass flag modification panel by the enter button.
B Y P A S S <state of the time> <time>
N A M E O F T H E D E V I C E
E Q L B Y P A S S O N
S / C B Y P A S S O N
E X I T
Interface with the operator on local control panel
The button allows to select graphically the device or the command of the bay. When
a device is selected, its label is displayed flashing.
The operator sends this command from the bay panel with button (for OFF) or button
(for ON).
The button allows to abort the choice during the selection step (in case of SBO
order), or in case of command on a close_synchrocheck.
2.3.13.3 Tap changer control request
The button allows to select one by one the devices of the bay. When a transformer is
selected, the operator can control it from local control panel by dealing with associated tap
changer positions.
In order to command the tap changer, the bay whose transformer belongs to has to be in
local mode.
The commands that can be sent through the local HMI are:
• Raise (= current tap position + 1) with the button

⇒ for a Double Wound transformer the Low Voltage is increased
⇒ for an Auto-wound transformer the Low Voltage is reduced
NOTE: A “raise” control is refused if the current tap position value
corresponds to the maximum position of the tap.
• Lower (= current tap position -1) with the button

⇒ for a Double Wound transformer the Low Voltage is reduced
⇒ for an Auto-wound transformer the Low Voltage is increased
NOTE: A “lower” control is refused if the current tap position value
corresponds to the minimum position of the tap.
• In case of “go to min”, “go to max” or “go to position x” request, the computer uses an
internal automatic function (via ISAGRAF) which generates the desired controls
sequences in order to reach automatically the expected position. This function may
generate “Direct execute”, “SBO once” or “SBO many” sequences according the
configuration of the device.
2.3.13.4 Computer mode

The operator is allowed to change the computer mode between:
• Operational
• Maintenance
• Test
The operator sends this command from the menu tree with a password protection.
2.3.13.5 Data base switch
MiCOM C264 Computer has 2 databases. The operator can switch between both databases.
2.3.13.6 Reset operating hours
The operator is allowed to reset the operating hours counter.
2.3.13.7 Time and date setting
The operator is allowed to set time and date of the computer from the local HMI.
Time and date are set from the menu tree with a password protection.
2.3.13.8 Manual value change of counters

Counters can be reset or affected to a new value manually by the operator at BCP.
Counters are changed from the menu tree with a password protection.
M E N U T R E E * H H : M M : S S
/ / C O M M A N D / C O U N T E R /
c o u n t e r 1 /
C O U N T E R v a l u e
current value
0 0 0 0 0 0 0 0 0 4
wanted value
0 0 0 0 0 0 0 0 0 4
M I N 0
M A X 2 1 4 7 4 8 3 6 4 7
C0306ENa
FIGURE 20: EXAMPLE OF MANUAL CHANGE VALUE OF A COUNTER

When this panel is displayed the most right digit of the wanted value is in inverse video. Buttons
and are used to select the digit of the wanted value that has to be modified. Buttons
and allow to change the value of the selected digit.
Once the correct wanted counter value is defined, it can be validated by pressing button .
2.3.13.9 Acknowledgement of alarms

Acknowledgement of alarms is performed globally or on a per alarm basis:
• Global acknowledgement: the operator can acknowledge all the unacknowledged

alarms of the computer. It is performed from the menu tree (with password check).
• Alarm per alarm acknowledgement: the operator can perform the alarm acknowledge
one by one. It is performed from the alarm panel.
2.3.13.9.1 Global acknowledge
The operator can acknowledge all the unacknowledged alarms of the computer
Interface with the operator on local control panel:
Acknowledgement of all alarms is done from the menu tree (with password check).
2.3.13.9.2 Alarm per alarm acknowledge

The operator can perform the alarm acknowledge one by one.
In this case, in the “alarm panel” he selects an alarm and can activate the acknowledge .
Acknowledgement alarm by alarm is done from the alarm panel.
The procedure of acknowledgement by the operator is the following one:
• the operator select (in the alarm panel) one alarm with the select button: . Once
the alarm is selected, the two first lines of the alarm in the alarm panel are blinking.
.
(deselecting is performed by the button
• the operator press the ‘enter’ button , enter the password if necessary
The button allows to abort the command.

If the button sequence is correct, the selected unacknowledged alarm is acknowledged.
The state of the alarm is then changed depending of its initial state:
active unacknowledged Î active acknowledged
inactive unacknowledged Î inactive acknowledged if the disappearance of the alarm
has to be acknowledged
The alarm list is updated with the new state of the alarm. The alarm in the inactive
acknowledged state is automatically cleared and removed from the alarm list if the automatic
clearing mode is set for this alarm in the database.
2.3.13.10 Alarms clearing
Clear of alarms is performed globally or on a per alarm basis:
• Global clear: the operator can clear all the inactive acknowledged alarms of the
computer. It is performed from the menu tree (with password check).
• Alarm per alarm clear: the operator can perform the alarm clear one by one. It is
performed from the alarm panel.
2.3.13.10.1 Global clear
The operator can clear all the inactive acknowledged alarms of the computer
clear of all alarms is done from the menu tree (with password check).
2.3.13.10.2 Alarm per alarm clear
The operator can perform the alarm clear one by one.
In this case, in the “alarm panel” he selects an alarm and can activate the clear.
Clear alarm by alarm is done from the alarm panel.
The procedure of clear by the operator is the following one:
• the operator selects (in the alarm panel) one alarm with the select button: .
Only the inactive acknowledged alarm can be selected.
• Once the alarm is selected, the two first lines of the alarm in the alarm panel are
blinking. (deselecting is performed by the button .

• The operator press the ‘enter’ button , enters the password if necessary.
The button allows to abort the command.
If the button sequence is correct, the selected alarm is cleared and disappears from the list.
2.3.14 Password management
The password is composed of a string of 4 characters. Only letters, from A to Z, are used.
(upper case)
2 passwords are valid in the computer:
• A user password modifiable by an operator
• A secret password always valid and not modifiable.

Password (user or secret) is necessary to activated some commands from local HMI:
• command from bay panel
• command with menu tree
• remote to local bay mode (optional)

User password is modifiable by the menu tree.
When a password is required, a string “password ??: “ is displayed in the current panel. The
operator has to enter it.
The first character is selected. The buttons and allows to change of selected
character.
The buttons and allow to change the value of selected character.

During the key boarding, the character is displayed at each button press. The button
validates the entered password.
• The password validity time is 15 minutes. During this delay, user can run another
command. This delay is re-armed at each button press.
3. THE COMPUTER MAINTENANCE TOOL

The Computer Maintenance Tool 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, switch
new database, and upload database (for some restricted applications)
• Access to boot parameters and facility to change them
• Access to date and time and facility to change them
• Access to sequence of events

4. THE EMBEDDED MAINTENANCE WEB SERVER

When the C264 is equipped with a CPU270 (also named CPU type 3) some maintenance
web facilities are available through the Internet Network. For detailed information, refer to
section 4 of chapter C264/EN MF.
5. THE PRINTER
Some specific events (the events to log are declared in the database) are printed and
chronologically sorted on logbook printers. They are printed with their time stamping and a
complete description (location and event description).
Logbook printers can be connected to SCP operator interface or to a bay level computer.
The printout format, which can be defined by user during the system configuration phase, is
the same across the whole log book printers connected.
A computer does not print information coming from other computers.
5.1 Inputs
A computer receives acquisition from various equipment (protection, captors, etc.) and, after
processing, may generate events that have to be printed. These kinds of events are defined
in the database during the configuration phase.
Types of events can be:
• Binary inputs (SP, DP, MP, SI and Groups)
• Tap position indication
• Measurement
• Operator action:
• Log-in and log-off,
• Devices control
• Alarm acknowledgement / clearing

5.2 Outputs
The 5 following properties can be printed. Each property is separated from the other by one
blank character The position of each property in the printed line (i.e. position 1, 2, 3, 4 or 5)
is defined in configuration:
Chronology – 1 character: refer to § “SOE events”
TimeStamp – 24 or 26 characters: refer to § “SOE events”
Origin - 67 characters: for BI, TPI, 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.
5.3 Printer management

5.3.1 Header & footer
A header and footer can be printed at each page. They are composed of one line, separated
from the events by a blank line.
Site Name – Computer Name Date / Time

<blank line>
<Log Book>
<blank line>
Page Number
C0141ENa
FIGURE 21: PAGE FORMAT

The page number is in the range [1..999]. It is reset at 1 after reaching 999 and at each new
day.
The date could have the following format: DD/MM/YY or MM/DD/YY or YY/MM/DD or
DD/MM/YYYY or MM/DD/YYYY or YYYY/MM/DD. The time has the following format:
hh:mm:ss.
5.3.2 Chronology & time stamp
The printers are managed in a real-time printing mode.
All synchronised information is printed in a chronological order.
Events are printed with their time-stamping and a complete description (location and event
description). The equipment detecting the event does the time-stamping (time-stamping at
source).
5.3.3 Printer out of service
If a printer fails, all the messages are stored in a circular buffer
When the buffer is full, any new message replaces the oldest one.
An indication (Printer status) is generated to indicate the printer failure.
5.3.4 Circular FIFO management
Before being printed, all information goes into a circular buffer
A latency delay is configured to sort information.
latency
Printers Buffer Length Data flow

C0142ENa
FIGURE 22: FIFO MANAGEMENT

The size of the buffer is 1000.
When the buffer is full, the oldest information are deleted (300 information suppressed) in
order to have place for new ones.
A specific message is inserted in the buffer to indicate the lost of information, this message
has the following information:
TimeStamp = date of the oldest suppress information
Origin = Name of the computer (configurable)
ObjectName = SUPPRESSED INFOS (configurable)
ObjectMessage = number of lost information
The following figure shows an example of SOE page.
substation-C264_GTW 05/07/06 09:08:35.232

* 05/07/06 09:08:35.232 CALC C264N3 /Generic module Group Permanent Self Check fault
* 05/07/06 09:08:35.232 CALC C264N3 /Group 0 to 499 Group Self Check fault
* 05/07/06 09:08:35.232 CALC C264N3 /Group 0 to 499 Group 1 Self Check fault
PAGE 001
FIGURE 23: EXAMPLE OF SOE PRINT

MiCOM C264/C264C
APPLICATION
CONTENT
2. REQUIREMENTS 6
3. COMPUTER CONFIGURATION SCOPE 7

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

ARCHITECTURE 9
4.1 Setting general system configuration relevant to computers 9
4.2 Adding a computer in the system architecture 13
4.3 Setting general attributes of a computer 14
4.3.1 Configuring binary input (BI) filtering 15
4.3.2 Configuring measurement acquisition and transmission 16
4.3.3 Configuring counter acquisition 17
4.3.4 Configuring computer internal fault characteristics 17
4.3.5 Locating computer in a substation (mandatory) 17
4.3.6 Defining a computer as system master clock 18
4.3.7 Defining a redundant computer (optional) 19
4.4 Adding computer hardware components 21
4.4.1 Adding boards 21
4.4.2 Setting specific attributes to computer boards 22
4.4.3 Adding extra communication channels to CPU board 24
4.4.4 Configuring a communication channel 25
4.4.5 Configuring an AI channel 27
4.4.6 Adding a printer 28
4.5 C264 IP adress and routing table definition 31
4.5.1 C264 as a gateway connected to a router and a remote IEC104 Scada 31
4.5.2 C264 as a gateway directly connected to a remote DNP3 Scada 34
4.6 Networking computer on the station-bus network 35
4.6.1 Connecting computer to others station-bus sub-systems 35
4.6.2 Defining addressing mapping of station-bus network 37
4.7 Networking IED on computer legacy network 40
4.7.1 Creating a legacy network of IED 40
4.7.2 Defining addressing mapping of a legacy IED 48
4.7.3 Addressing a datapoint on an IED legacy network 66
C264/EN AP/C40 Application
4.8 Networking SCADA on computer SCADA network 67

4.8.1 Creating a SCADA network 67
4.8.2 Defining addressing mapping of SCADA network 75
4.8.3 Addressing datapoint on SCADA legacy network 89
4.9 Defining wave record file management 90
4.9.1 Defining management of disturbance file for IED 90
4.9.2 Defining T103 IED extra information for disturbance file 92
4.9.3 Defining management of wave record file for computer CT/VT board 94
4.10 Defining a computer klaxon 102
4.11 Setting system information for computer components 103
4.11.1 Setting general system information of a computer 104
4.11.2 Setting system information of board 108
4.11.3 Setting system information of legacy IED 110
4.11.4 Setting system information of serial printer 111
4.11.5 Setting system information of a SCADA network 112
5. DEFINING DATAPOINT 113

5.1 Creating a datapoint 113
5.1.1 Overview of binary input processing 113
5.1.2 Defining a SPS datapoint 114
5.1.3 Defining a DPS datapoint 116
5.1.4 Defining a MPS datapoint 118
5.1.5 Overview of measurement processing 120
5.1.6 Defining a TPI datapoint 125
5.1.7 Defining a Counter datapoint 128
5.1.8 Overview of control sequence processing 132
5.1.9 Defining a SPC datapoint 132
5.1.10 Defining a DPC datapoint 137
5.1.11 Defining a SetPoint datapoint 141
5.2 Linking a datapoint to a profile 147
5.2.1 Defining a SPS profile 149
5.2.2 Defining a DPS profile 153
5.2.3 Defining a MPS profile 158
5.2.4 Defining a MV profile 164
5.2.5 Defining a Counter profile 170
5.2.6 Defining a SPC profile 174
5.2.7 Defining a DPC profile 178
5.2.8 Defining a SetPoint profile 182
5.3 Defining computer local archiving of datapoint events 185
5.4 Defining computer local archiving of datapoint alarms 185
5.5 Defining computer local logging of datapoint events and alarms 185
5.6 Defining acquisition source for input datapoints 186

5.6.1 Acquiring input datapoint via input channels 186
5.6.2 Acquiring input datapoint via an IED legacy network 191
5.6.3 Acquiring input datapoint via non-PACiS IEC61850 communicant IED 192
5.6.4 Producing input datapoint 193
5.7 Defining control source for output datapoints 195
5.7.1 Controlling output datapoint via output channels 195
5.7.2 Controlling output datapoint via an IED legacy network 198
5.7.3 Controlling output datapoint via non-PACiS IEC61850 communicant IED 199
5.7.4 Producing output datapoint 200
5.7.5 ACKnowledgement definition in case of simultaneous orders 200
5.8 Defining datapoint association 201
5.8.1 Adding a target datapoint 201
5.8.2 Linking the target datapoint to the original datapoint 202
5.8.3 Defining the states associations 204
6. DEFINING COMPUTER CONFIGURATION IN ELECTRICAL

ARCHITECTURE 205
6.1 Defining an electrical topology 205
6.1.1 Defining a Site 207
6.1.2 Defining a Substation 207
6.1.3 Defining a Voltage level 212
6.1.4 Defining a Bay 214
6.1.5 Defining Module 220
6.2 Defining a Synchrocheck function 231
6.2.1 Completing circuit-breaker definition for synchrocheck 231
6.2.2 External synchrocheck behaviour 235
6.2.3 Internal synchrocheck behaviour 235
6.2.4 Automation description of internal synchrocheck 235
6.2.5 Creating a synchrocheck function 238
6.3 Defining an Auto-recloser built-in function 244
6.3.1 Auto-recloser behaviour 244
6.3.2 Creating an auto-recloser function 244
6.4 Defining a Tap changer built-in function 251
6.4.1 Tap changer behaviour 251
6.4.2 Creating a tap changer built-in function 252
6.5 Defining an Automatic Voltage Regulation (AVR) built-in function 254
6.5.1 AVR behaviour 254
6.5.2 Creating an AVR function 254
6.6 Defining an electrical regulation by user function 267
6.6.1 Defining a FBD fast automation 267
6.6.2 Defining an ISaGRAF slow automation 273
6.6.3 Defining a group 281

6.6.4 Controlling xPC by xPS change of state 283
6.6.5 Producing a DPS from two SPS 284
6.6.6 Defining interlocking 284
6.6.7 Defining an automatic/manual dependency 286
6.7 Defining a Fast Load shedding application 287
6.7.1 General Architecture 287
6.7.2 FLS Data Flow summary 288
6.7.3 Priority Setpoints 288
6.7.4 Load Shedding Preselection (LSP) 288
6.7.5 Graphical animation with LSP 289
6.7.6 Use of LSP in PSL 289
6.7.7 Use of LSP in ISAGRAF scheme 290
6.7.8 Trigger definition 290
6.7.9 Topology calculation 290
7. DEFINING COMPUTER LOCAL HMI 291

7.1 Defining a bitmap table 291
7.2 Defining a computer workspace 294
7.2.1 Settings LHMI labels 294
7.2.2 Creating a workspace 294
7.3 Defining a computer bay mimic 295
7.3.1 Creating a computer bay mimic 295
7.3.2 Defining static part: line, bitmap, fixed text 298
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation,
transformer representation 301
7.3.4 Assigning MV to bay mimic 308
7.4 Displaying datapoint status with Led 309
8. ANNEX A: COUPLING SCE DATA MODEL AND ISAGRAF 310

8.1 ISaGRAF presentation 310
8.1.1 ISaGRAF workbench description 310
8.1.2 Directories structure of ISAGRAF 311
8.1.3 Uploaded files towards the target 312
8.2 Usage of SCE datapoints in ISaGRAF 313
8.2.1 Hierarchical relationship: Function management DPs. 313
8.2.2 Server relationship 313
8.2.3 Client relationship 314
8.2.4 Access rights summary table 314
8.2.5 Equivalence of SCE datapoint in ISaGRAF 315
8.2.6 ISaGRAF dictionary data structure 316
8.2.7 Prototype and usage of PACiS function for ISaGRAF 319

The present document is a MiCOM C264/C264C section of the documentation binder. This
document is intended to present you how to configure the Computer. It is the section
Application (AP) of this Product.
2. REQUIREMENTS
First, if it is not already done, you will need to install the PACiS SCE (System Configuration
Editor), see the chapter IN (Installation) of this product.
This document presents you the objects and the attributes of a referenced database made
with the PACiS SCE. For understanding this document you first need to be familiar with
PACiS SCE and PACiS computer C264.
To add an IEC-61850 computer into an existing system you need to have the mapping of the
system (IP address, Network names of equipment…).
To generate a template, for an existent IEC-61850 computer, see the chapter Functional
Description of the SCE product.
3. COMPUTER CONFIGURATION SCOPE

3.1 General PACiS system configuration
To define a complete PACiS system, three aspects should be taken into account.
The first one is the system topology. It consists of device composition that manages the
customer’s electrical process. Generally, this part of furniture is relevant to 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 (computer local HMI).
When creating a new configuration using SCE, these three topologies are automatically
instantiated via root objects:
− A ‘Site’ object for the electrical topology, containing one ‘Substation’ object.
− A ‘Scs’ object for the system topology, containing one ‘Ethernet network’ object (SCS
is an abbreviation of Substation Control System).
− A ‘Graphic’ object for the graphical topology.
FIGURE 1: GENERAL ARCHITECTURE OF A PACIS CONFIGURATION IN SCE

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

used for communication at station bus level.
− Electrical topology (Site): computer manages bays and relevant modules or substation
information.
− Graphical topology (Graphic): computer can own a LCD display used for animated
graphical bay panel representation and others list panels.
3.3 Sparing object

At SCE level, a spare object is an object having its spare attribute set to true. The
configurations of this object and of its spare attribute are the same as for any other object
and attribute. Any objects can be spare and particularly those concerning the computer
configuration.
Spare objects are not provided to the generator tools, respecting the following rules:
− An object O2, not spare, linked directly or not to a spare composite parent object O1,
is considered as spare.
O1 (Spare = Yes)
O2 (Spare = No)
S0387ENa
− A relation defined on an object O1, not spare, and linked to a spare object O2, is
considered as a relation without link.
O1 (Spare = No)
link
Relation O2 (Spare = Yes)
S0388ENa
4. DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE

4.1 Setting general system configuration relevant to computers
System configuration is done at SCS root. It is relevant to some general behaviour of PACiS
devices.
It concerns those specific attributes:
− Common labels used for control acknowledgement, time quality logging, alarm
management logging, computer board management.
− Alarm management characteristics (alarm processing type, audibility delays, alarm

clearing mode per gravity basis).
And those specific relations:
− Designation of the master clock computer(s) in the system. Up to two computers can
be declared as System Master Clock. A System Master Clock computer gives the time
reference to all others devices connected to the station-bus network through SNTP
(Simple Network Time Protocol). A System Master Clock computer is always located
in a substation.
− Designation of elementary action rights by default used by system datapoints of the

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

Some attributes of SCS objects concern all the computers defined under the station network.
Hereafter, are listed these attributes:
1. time zone: used for timestamp information.
2. behaviour on DOU failure (Control refused on faulty board / computer goes in faulty
mode).
3. computer password : local HMI password by default.
4. Default board labels and status.
5. Control acknowledgement labels used for order logging.
(1)
(2)
(3)
(4)
(unused at
computer
level)
C0161ENb
FIGURE 2: GENERAL AND LABELS ATTRIBUTES OF SCS

(5)
unused at
computer
level
C0162ENb
FIGURE 3: LABELS ATTRIBUTES OF SCS (CONT’D)

unused at
computer
level
(6)
C0163ENb
FIGURE 4: ALARM ATTRIBUTES OF SCS

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

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

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

The addition of a computer definition is done via the “Objects entry” window at Ethernet
network level by clicking on mouse’s right button as the following:
FIGURE 6: ADDING A COMPUTER IN THE SYSTEM ARCHITECTURE

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

1. Binder ‘Hardware’, that groups all defined boards and printers of the computer.
2. Binder ‘System infos’, that groups all general system datapoints of the computer.
3. ‘PLC’ object for Programming Logic Chart that corresponds to ISAGRAF and PSL
project directory.
4. ‘IEC Mapping’ object, that describes the station-bus network addressing mapping of
datapoints managed by the computer.
4.3 Setting general attributes of a computer

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

1. short name and long name: used for logging, alarms, …
2. rack model (80 TE / 40 TE): there exist two models of computers: C264 and C264C.
The C264 is a large size computer (80TE) and C264C is the compact one (40TE). The
height of both computers is 4U.
3. date format: this attribute defines the date format used in the computer HMI (LCD).
4. synchronisation source (None / IRIG-B): indicates if the computer is synchronized
through IRIG-B. The relation at SCS level “has for master clock” defines which device
is the master clock in the system. A master clock computer is necessary synchronized
through IRIG-B.
5. TCP/IP address and network name of the computer.
Configuration rules and checks
• The "TCP/IP address" value of a device must be unique among all the devices per
Ethernet Network (except for OI server and OI client).
• The "network name" value of a device must be unique among all the devices per
Ethernet Network (except for OI server and OI client).
4.3.1 Configuring binary input (BI) filtering

There exist two types of input signal handling:
• Debouncing: the start transition is signalled with the correct time, the following
changes within the debounce time are ignored. The range of the debounce time is
from 0 to 20 ms (with a 1 ms step). The event is time tagged at the instant of the first
transition.
• Filtering: the transition is only signalled if the signal is stable for minimum as long as
the filtering time. The range of the filtering time is from 0 to 20 ms (with a 1 ms step).
The filtering is allowed only if the debouncing is applied (i.e. the filtering cannot be
applied if there is no debouncing before). The event is time tagged at the instant of the
first transition.
Filtering time
Debouncing
time
t0 t1 t2
C0127ENa
FIGURE 9: DEBOUNCING AND FILTERING

A value of 0 means that no filter is applied: a change of state is validated as soon as it is
detected.
Three couples of delays (debouncing/filtering) are defined:
• one for all Digital Inputs which will be used as Binary Inputs.
• one for all Digital Inputs which will be used as Digital Measurements.
• one for all Digital Inputs which will be used as counters.
(1)
(2)
(3)
FIGURE 10: SETTING BI ACQUISITION ATTRIBUTES

1. debouncing delay (range [0, 20 ms], step 1 ms).
2. filtering delay (range [0,.20 ms], step 1 ms.
3. Toggling attributes are defined as the following:

A digital input (DI) is said to be toggling if its state has changed more than N times in a
given period of time T1.
A toggling DI returns in the normal state if its state has not changed within another
period of time T2.
N (toggling transition number), T1 (toggling delay) and T2 (toggling end delay) are
parameters determined during the configuration step on a per computer basis.
• If the attribute "debouncing delay" is set to 0, then the attribute "filtering delay" must
be set to 0.
4.3.2 Configuring measurement acquisition and transmission
(1)
(2)
(3)
(4)
FIGURE 11: MEASUREMENTS VALUES ATTRIBUTES FOR A COMPUTER

1. Debouncing delay and filtering delay: used for digital measurements.
2. Analogue measurements acquired on AIU board: acquisition samples ranges for long
scanning (range [500 ms, 10000 ms], step 500 ms) and short scanning (range [100
ms, 1000 ms], step 100 ms). For each channel of AIU board, short or long scan period
should be chosen (refer to section 4.4.5 Configuring an AI channel).
3. Acquisition on TMU board with CTVT fundamental 50 or 60 Hz (number of harmonics
is fixed to maximum 16).
4. Short transmission period on station bus (range [0,.60 s],step 100 ms) and long
transmission period given by a multiple of the short period ([0..600]x short
transmission period).
be set to 0.
4.3.3 Configuring counter acquisition
(1)
FIGURE 12: COUNTER ACQUISITION ATTRIBUTES OF A COMPUTER

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

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

4.3.6 Defining a computer as system master clock

As said in section 4.1 (Setting general system configuration relevant to computers), up to two
computers can be master clock for the system. This is done by defining the mandatory
relation (1) “has for master clock:“ at SCS level. By double clicking this relation the
Relation link editor dialog box opens and lists the computers (2) which can be declared as
master clock (by clicking it and then by clicking the Ok button). In our example computer
C264_A has been selected as System master clock (3). If a second master clock is needed
a second "has for master clock:" relation (4), available in the object entry window
associated to the Scs level, has to be added and defined by the same way as the first one. In
this case the Relation Link editor lists only the three remaining computers. When two
computers have been declared as master clock the "has for master clock:" relation is no
more available in the object entry window associated to the Scs level.
(2)
(1)
(3)
(4)
FIGURE 15: DEFINING A (TWO) COMPUTER(S) AS SYSTEM MASTER CLOCK

4.3.7 Defining a redundant computer (optional)

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

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

Automatic creation of
"has for UCA2/IEC
server" relation for the
main computer
Slave computer created

after manual updating of
its short and long names,
and IP characterisitics
Automatic creation of
"backup" relation between
the two computers
C0166ENc
FIGURE 17: DEFINING A REDUNDANT COMPUTER (ONCE CREATED)

4.4 Adding computer hardware components

4.4.1 Adding boards
PACiS 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/AIU211 - Analogue input boards with 8 analogue input channels:

- analogue measurement acquisition
• TMU200/TMU210/TMU220 - CT and VT input boards with 4 CT and 4 VT input

channels ( 5 VT inputs on TMU220):
- ct/vt sampling acquisition,
- MV computations based on acquired samples
• 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, CPU270 : CPU boards with communication channels (1*Ethernet on

CPU260, 2 Ethernet on CPU270 and serial communication ports)
• BIU241 : Power Supply board with communication channels (serial communication

ports)
• GHU200 - Graphical panel boards with led channels

Computer hardware definition is done in SCE by adding typed boards below computer
object. Mandatory boards (CPU260/CPU270, GHU200, BIU241) are automatically created at
computer’s creation. Implicit typed channel creations are done at board’s creation.
Linking datapoint to channels does datapoint wiring.
The addition of a board definition is done via the “Objects entry” window by clicking on
mouse’s right button as the following:
FIGURE 18: ADDING A BOARD TO THE COMPUTER


Slots and boards in a C264 computer
A B C D E F G H I J K L M N O P Q
BIU CPU
• Slots from C to P may contain a board of the following types: AIU201, AIU210/AIU211,
DOU200, DIU20x, DIU210 or CCU20x
• Slot Q may contain one TMU200 board or one 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.
• If present the Ethernet boards (SWU20x, SWR20x, SWD20x) are to be installed in

slots C or D.
Slots and boards in a C264C computer
A B C D E F G H
BIU CPU
• Slots from C to F may contain a board of the following types: AIU201, AIU210/AIU211,
DOU200, DIU20x or CCU20x
• Slots G and H may contain one TMU200 board or two 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.
• If present the Ethernet boards (SWU20x, SWR2xx, SWD2xx) are to be installed in

slots C or D.
4.4.2 Setting specific attributes to computer boards
4.4.2.1 Setting common attributes to computer board
For each board of the computer the short name attribute (1) may be updated for correct
logging and alarm discrimination concerning board status datapoint.
For boards AIU2xx, CCU200, DIU2x0, DOU200 the physical board number attribute (2)
must be updated.
For boards CPU260, BIU241, GHU200, TMU2x0 this attribute is forced to 0 by the SCE and
is not displayed in the attributes window
(1)
(2)
FIGURE 19: GENERAL ATTRIBUTES OF A BOARD

• Per board type (AIU201, AIU210/AIU211, DOU200, DIU20x, CCU20x), the physical
board number attribute values must begin from 0, be unique and contiguous.
4.4.2.2 Setting specific features of a GHU200 board

For GHU board, the specific attribute ‘HMI type’ (1) has to be set to:
• ‘Simple’ if GHU board without LCD is used.
• ‘Complete’ if GHU board with LCD is used.
(1)
FIGURE 20: GENERAL ATTRIBUTES OF A GHU200 BOARD

For complete HMI, the extra relation ‘has for workspace’ (1) must be
filled at board level. For details about computer workspace, refer to
section 7.2 Defining a computer workspace.
(1)
FIGURE 21: DEFINING WORKSPACE FOR COMPLETE GHU200 BOARD

For computer LED configuration, refer to section 7.4 Displaying datapoint status with Led.
• If the value of the "HMI type" attribute is "Simple", then "Led#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.
4.4.2.3 Setting specific attributes of a 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 / Delta).
2. reference phase (Phase A / Phase B / Phase C).
3. reference phase side (Phase A, B, C wired line side / Phase A, B, C wired busbar
side).
4. nominal current and nominal voltage.
Extra attributes are reserved for future use.
(1)
(2)
(3)
(4)
FIGURE 22 TMU200 BOARD SPECIFIC ATTRIBUTES

If reference phase signal is absent, values transmitted by TMU board are set to invalid.
Please refer to the Chapter CO (Connections) for the description of the TMU2xx electrical
CT/VT inputs and database association.
4.4.3 Adding extra communication channels to CPU board
At CPU260 board level, the frontal RS232 port is mandatory and automatically created at
board creation. Two extra communication channels can be added from SCE objects entry
window.
FIGURE 23: ADDING COMMUNICATION CHANNELS

4.4.4 Configuring a communication channel

A communication channel is a physical port available on CPU or the BIU board at their
creation or manually added as option.
A communication channel can be used exclusively for:
1. Communication with an IED legacy network.
2. Communication with a SCADA network.
3. Communication with a serial printer.
(1)
(2)
mandatory frontal port
(3)
C0167ENb
FIGURE 24: USAGE OF COMMUNICATION CHANNEL

Once used by a communication link, the physical port has to be set relatively to the
communication link characteristics:
1. RS type (RS232 / RS485).
2. baud rate (bits/s) (50 / 100 / 200 / 300 / 600 / 1200 / 2400 / 4800 / 9600 / 19200 /
38400 / 56000 / 64000)
NOTE: For the CPU260 board with serial ports 3 and 4, this attribute (baud
rate) must be set to the same value . For the CPU270 ports 3 and 4,
the baud rate can be different.
3. parity (No parity / Odd parity / Even parity)
4. number of stop bits (1 bit / 2 bits)

5. nb. bits per char (7 bits / 8 bits)
6. Tx carrier management (Switched / Constant / Soft):
− Switched: when the computer has to send a frame it sets the RTS line and
waits for the CTS line to be set by the receiver. It then waits during a time
defined by attribute (9) before starting the transmission of the frame. At the end
of the transmission the computer waits during a time defined by attribute (10)
before resetting the RTS line
− Constant: the RTS line is always set by the computer. When it has to send a
frame it waits for the CTS line to be set by the receiver to start the transmission.
− Soft: the RTS and CTS line are not managed by the computer.
7. CTS wired (No / Yes): this attribute must be set to YES if the TX carrier
management attribute is set to Switched or to Constant
8. CD wired (No / Yes): in order for the DCD line to be managed by the computer this
attribute must be set to YES if the TX carrier management parameter is set to
Switched.
9. pre TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore significant
only if attribute (6) is set to Switched.
10. post TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore
significant only if attribute (6) is set to Switched.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10
)
FIGURE 25: GENERAL AND TRANSMISSION ATTRIBUTES OF A COMMUNICATION

CHANNEL
4.4.5 Configuring an AI channel

An AI channel is an analogue input available on AIU201 and AIU21x boards at their creation.
AI channels are used for analogue measurement acquisition.
implicit AI#0 to
AI#3 channels
creation on
AIU200 board
C0168ENb
FIGURE 26: USAGE OF ANALOGUE CHANNELS

Once used by a MV, the AI has to be set relatively to the acquisition characteristics:
1. sensor range for AIU201 -20 mA …+20 mA / -10 mA …+10 mA / -5 mA …+5 mA / -1
mA …+1 mA / 0 mA …+1 mA / 0 mA …+5 mA / 0 mA …+10 mA / 0 mA …+20 mA / 4
mA …+20 mA / -10 V … +10 V / -5 V … +5 V / -2.5 V … +2.5 V / -1.25 V … +1.25 V
sensor range for AIU210/AIU211: -20 mA …+20 mA / -10 mA …+10 mA / -5 mA
+5 mA / -1 mA …+1 mA / 0 mA …+1 mA / 0 mA …+5 mA / 0 mA …+10 mA / 0 mA
+20 mA / 4 mA …+20 mA
2. acquisition period (short period / long period): refer to section 4.3.2 Configuring
measurement acquisition and transmission.
(1)
(2)
FIGURE 27: CONFIGURING AN AI CHANNEL

4.4.6 Adding a printer

SCE data modelling describes printers used in PACiS system for ‘sequence of events’ and
log book functions at operator interface level and computer level.
A printer at computer level must be a serial one connected to a communication channel of
the computer.
To create a computer printer:
• Add a serial printer from object entry available at computer level.
FIGURE 28: ADDING A SERIAL PRINTER
• Update its ‘has for communication port’ relation (1) and its attribute ‘printer control’ (2).
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 29: UPDATING THE COMMUNICATION PORT RELATION FOR A SERIAL PRINTER
To control the way logging is managed and formatted on a serial printer, updating printer
attributes is necessary:
3. page size (range [20 lines, 65535 lines ], step 1 line).
4. buffer size (range [100 events, 3000 events ], step 100 events)
5. number of events to suppress when buffer is saturated (.range [30 events, 1000
events ], step 10 events)
6. Rank of the different columns used for printing formats.
• The following constraint must be respected : buffer size > nb of events to suppress
when saturated
Hereafter an extract of logging that illustrates the different columns used for printing formats:
origine
time stamp object name
chronology object message
C0169ENa
FIGURE 30: THE DIFFERENT COLUMNS USED FOR PRINTING FORMATS

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

4.5 C264 IP adress and routing table definition

You’ll find hereafter example of C264 adressing and routing table definition in two typical
C264 application cases.
4.5.1 C264 as a gateway connected to a router and a remote IEC104 Scada
T104 SCADA
client address
192.168.10.5,
192.168.10.9,
192.168.10.110,
192.168.10.54
192.168.10.0
192.168.10.99
192.168.20.99
PACiS
192.168.20.0
192.168.20.1
subnet mask 255.255.255.0
192.168.20.98
192.168.30.12
WebServer or other IP application (CMT, SMT, ...)

192.168.30.2
192.168.30.0
C0426ENa
4.5.1.1 C264 Routing table parameters

In SCE configuration C264’s routing table is declared as follow:
“Gateway TCP/IP address” give the address of the router.
“Target TCP/IP address” is the address of the remote “Client” to be connected through this
router.
NOTE: “Gateway TCP/IP address” is not linked to the C264’s gateway

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

192.168.30.2 can be replied by C264.
The label “Gateway TCP/IP address” is to be understood as: “Router IP address”.
The label “Target TCP/IP address” is to be understood as: “Target or Network IP address”.
4.5.1.2 T104 protocol configuration

It is possible to secure T104 client remote connection by giving a short list of authorized
clients.
In the example, T104 SCADA link configuration is to be as defined as hereafter:
4.5.1.3 C264 IP adress definition

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

In the example the C264 have address 192.168.20.1 and subnet mask 255.255.255.0
(default value) he is able to reach all equipment with address 192.168.30.x.
4.5.1.4 C264 IP Parameters with the maintenance CMT tool
IP on Ethernet: the Internet address of the Ethernet interface.

The Internet addresses (IP) are specified in "dot" notation (e.g., 10.22.92.52).
Example: 10.22.92.52
This field can have an optional subnet mask of the form inet_adrs:subnet_mask.
Example: 10.22.92.52:0xFFFF0000 subnet mask = 255.255.0.0
10.22.92.52:0xFF000000 subnet mask = 255.0.0.0
By default, the subnet mask is set to 0xFFFFFF00 subnet mask = 255.255.255.0

4.5.1.5 Router-PC configuration (case of PC under Microsoft-windows)
In case of PC with two Ethernet boards, you have to configure both IP board and activate IP
routing thanks to a registry key.
In a registry editor, navigate to
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\Tcpip \Parameters
Select the "IPEnableRouter" entry (by defining as value : 1 ) :
To enable IP routing for all network connections installed and used by this computer, assign
a value of 1.
This will be taken into account after rebooting computer.
4.5.1.6 PC configuration when using the C264 Maintenance Webserver
On WebServer’s PC it is necessary to define and add the “route” to access the C264:
-> open a DOS command and type: Route ADD 192.168.20.1 MASK 255.255.0.0
192.168.30.12.
(According the usual definition “route ADD @target MASK mask @gateway”)
4.5.1.7 Particular case of DHCP network
The Dynamic Host Configuration Protocol (DHCP) is based on automatic assignment of IP
addresses, subnet masks, default gateway, and other IP parameters.
WARNING: C264 IS DESIGNED FOR FIXED IP ADRESS NETWORK: IP ADRESSING
CONFLICTS COULD BE MET WITH THE C264 INSTALLED ON
NETWORKS WITH DHCP ADRESSING.
4.5.2 C264 as a gateway directly connected to a remote DNP3 Scada
NOTE: In case of DNP3/IP SCADA connected to C264-GTW without using

any router, it is not necessary to configure IP addressess at SCS level
(Gateway TCP/IP address, Target TCP/IP address).
In this example, C264 must have address 192.168.20.1 and SubNetwork mask must be set
to 255.255.0.0; it will accept connection from SCADA 192.168.30.4
4.6 Networking computer on the station-bus network

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

Computer A has
for IEC- 61850
server computer B
Computer B has
for IEC- 61850
client computer A
(1)
C0170ENb
FIGURE 32: COMPUTER (A) AS UCA2/IEC CLIENT OF COMPUTER (B)

When adding the ‘has for UCA2/IEC server’ relation to computer (A), a specific attribute of
the relation, modelling/goose usage (1), can be set to precise the way data are transmitted
from server (B) to computer (A). There are three possibilities:
• Data model only (or report mode only).
• Goose only.
• Data model and goose.

Basically, the Report mode is used to transmit filtered data for displaying, printing and
archiving. The Goose mode is used to transmit data as soon as possible after their
acquisition and as quickly as possible, for automation purpose.
Goose transmission must be used if computer (A) uses BIs served by computer (B), for
ISaGRAF, FBD or interlock computation (refer to section 6.6 Defining an electrical regulation
by user function).
During a loss of communication between a client and a server, all server BIs are set to
• A client must not be linked to the same server through multiple relations "has for
UCA2/IEC server".
Report based mode

Via its IEC-61850 address, a BI (see section 5.1.1 Overview of binary input processing) can
be configured to be transmitted in Report mode. In this mode, a confirmed change of status
is spontaneously transmitted to the subscribers.
The BI information transmitted in a report is:
• the state and quality (the BI resulting state is split in state and quality on IEC-61850)
• the reason for change, which could be one of the below values :
− change of data (set if the state has changed, before persistence or motion filtering)
− change of quality (set if the quality has changed, before persistence or motion
filtering)
− change due to control (set if the state or quality change is due to a control)
From one server, all BI reports are not transmitted in a chronological order (it is an IEC-
61850 client feature to put, if needed, all information in a chronological order).
During a loss of communication, the events detected on the computer are not buffered.
GOOSE based mode
A BI (only SPS and DPS) can be configured to be transmitted in GOOSE mode. In this
mode, the change of status is transmitted in multicast to the configured receivers. Only the
BI unfiltered states are transmitted, the time stamping and the reason for change are not.
Due to GOOSE format, all BI resulting states given below cannot be transmitted. So, the
following mapping is applied:
BI Resulting State GOOSE value

RESET, FORCED RESET, SUBSTITUTED RESET, 01
CLOSE, FORCED CLOSE, SUBSTITUTED CLOSE
SET, FORCED SET, SUBSTITUTED SET, 10
OPEN, FORCED OPEN, SUBSTITUTED OPEN
JAMMED 00
UNDEFINED, TOGGLING, SELFCHECK FAULTY, 11
SUPPRESSED, UNKNOWN
A measurement can be configured to be transmitted in GOOSE mode as well ( refer to

section 5.2.9 of chapter C264/EN FT).
4.6.2 Defining addressing mapping of station-bus network
An IEC 61850 mapping is an aggregation of logical devices, composed of bricks. Generally,
a brick corresponds to an electrical device or function. It provides its real-time data (status,
measurements, and controls …) and some configuration aspects. To do that, a brick groups
data by categories (Status, measurements, Control, Configuration), called functional
components.
A functional component groups data objects. A data object must be seen as a real-time
equivalent of a PACiS datapoint. So, when a PACiS sub-system (IEC 61850 client) needs
the real-time value of a datapoint managed by another sub-system (IEC 61850 server), this
last one transmits the information via a data object of its own IEC 61850 mapping. At SCE
data modelling level, IEC 61850 clients must precise which IEC 61850 servers it retrieves
information from (see section 4.6.1 Connecting computer to others station-bus sub-systems).
Generally, an IEC 61850 data object has a stereotype, called common class. The structures
of these ones are known by all PACiS IEC 61850 communicant sub-systems. For PACiS
sub-systems, the number and structure of common classes are fixed. They are the terminal
description of IEC 61850 PACiS data modelling.
In IEC 61850 Mapping of PACiS sub-system, there is a native logical device LD0 with fixed
and hard-coded bricks (DBID, DI (LPHD), GLOBE (LLN0), and DIAG). When creating a
PACiS computer at SCE level, an IEC 61850 mapping with LD0 and its default bricks is also
created. LD0 is a system logical device that groups all system diagnostics and controls
relevant to the computer. Datapoints addressed in the brick of LD0 are only relevant to
system topology.
Extra logical devices can be created in the IEC 61850 mapping of a computer. Generally,
there is one logical device for each bay managed by the computer, and, in each logical
device, there is one brick for each module or built-in function.
4.6.2.1 SBUS automatic addressing
“SBUS automatic addressing” function is based on the substation electrical topology and
especially on bays.
The easiest way to create application logical devices relevant to electrical bays managed by
a computer is to run “SBUS automatic addressing function” for the computer. The contextual
menu (mouse right click) of the computer (1) can launch this function.
(1)
FIGURE 33: SBUS AUTOMATIC ADDRESSING

NOTE: Only no-Spared datapoints are taken into account in automatic
addressing. If a datapoint is unspared then an automatic addressing
treatment must be done again
• Some datapoints are out of scope of automatic addressing. Theses datapoints are
identified by their data model mnemonic and their short name. They are listed in the
following table:
Excluded datapoints
Parent object
mnemonic name
Module Circuit breaker SynCheck_Close_DPC Sync CB close
SynCheck_Close_SPC Sync CB close

Select_SPC Selection SPC
Switch_SPC_PhA Switch phA SPC
Switch_SPC_PhB Switch phB SPC
Switch_SPC_PhC Switch phC SPC
SwitchPos_PhA (DPS) Switch PhA pos.
SwitchPos_PhB (DPS) Switch PhB pos.
SwitchPos_PhC (DPS) Switch PhC pos.
SwitchPos_SPS_PhA Switch PhA pos. SPS
SwitchPos_SPS_PhB Switch PhB pos. SPS
SwitchPos_SPS_PhC Switch PhB pos. SPS
SwitchPos (DPS) Switchgear pos.
SwitchPos_SPS Switchgear pos.
PhaseNotTogether_SPS Ph not together
External automatic CS_CtrlOnOff_DPC on/off ctrl DPC
synchrocheck built-in function
CS_CtrlOnOff_SPC on/off ctrl SPC
Relay [XX] function XX_thresholdY_trip XX tY trip
examples:
With :XX = function number
46 t1 trip
Y = threshold number 67 t3 trip
XX_thresholdY_inst_dir_rev XX tY in di rev
examples:
With :XX = function number
67 t1 in dir rev
Y = threshold number 67 t3 in dir rev
XX_thresholdY_interlock XX tY interlock
With :XX = function number example:
67 t1 interlock
Y = threshold number
Relay [automatism] start_disturbance start dist ctrl
Relay [49] function 49_trip_th_overload 49 trip th over.
• Some measurements computed by a TMU 210 are out of scope of automatic

addressing if the measure type ( measure type attribute of the relation "is computed
by" linked to the related MV) is one of the followings:
− mod Vo (ADC)
− mod I1 (ADC)
− mod I2 (ADC)
− mod V1 (ADC)
− mod V2 (ADC)
− thermal status
NOTE: For the datapoints which are excluded of the automatic addressing it
is possible to add the relation "has for IEC address and then define it.
4.7 Networking IED on computer legacy network
4.7.1 Creating a legacy network of IED
Generally, specific devices called relays or IEDs insure protection of electrical modules and
bays. IED connection to PACiS system is commonly done via IED legacy networks managed
by PACiS computer as master.
At SCE data modelling level, up to four IED legacy networks (relevant to a specific protocol)
can be located under a PACiS computer C264 or C264C. Each IED legacy network has to
be linked to communication port embedded in computer boards. Up to sixteen IED can be
added under a legacy network.
4.7.1.1 Adding a legacy network

To create a legacy network on a computer:
• Add a legacy network relevant to a specific protocol from object entry available at
computer level (1),
• Update the legacy network attributes relevant to its protocol characteristics,
• Update its ‘has for main comm. port’ relation and the communication port
characteristics (see section 4.4.4 Configuring a communication channel),
(1)
FIGURE 34: ADDING A LEGACY NETWORK

4.7.1.2 Setting general attributes of a legacy network
Whatever the kind of legacy network, its short name and long name attributes (1) must be
updated for correct logging and alarm discrimination concerning IED status datapoint
connected to the legacy network.
(1)
FIGURE 35: GENERAL ATTRIBUTES OF A LEGACY NETWORK

4.7.1.3 Setting acquisitions attributes of a T103 legacy network

When adding a T103 legacy network, the following attributes, available for all its IEDs, must
be updated:
1. number of retries (range [1, 10]): number of tries of the same frame without IED
response, the computer will send it before setting it disconnected.
2. acknowledgement time-out (range [100 ms, 30 s], step 100 ms): maximum delay an
IED answer is awaited when the computer asks it a information.
3. synchronisation cycle (range [10 s, 655350 s]): time synchronisation period of the
IED by the computer.
4. downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by
the computer, it tries to re-connect it regularly at this cycle.
5. inter frame duration (range [1 , 50 ], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames.
(1)
(2)
(3)
(4)
(5)
FIGURE 36: SETTING ACQUISITION ATTRIBUTES OF A T103 LEGACY NETWORK

4.7.1.4 Setting acquisition attributes of a T101 legacy network
When adding a T101 legacy network, the following attributes, available for all its IEDs, must
be updated:
1. number of retries (range [1, 10], step 1): corresponds to the number of tries of the
same frame without IED response, the computer will send it before setting it
disconnected.
2. station address size (range [1 byte, 2 bytes]): size of the IED addresses
3. ASDU address size (range [1 byte, 2 bytes]): size of the ASDU.
4. info address size (range [1 byte, 3 bytes]): size of the information addresses.
5. transmission cause size (range [1 byte, 2 bytes]): size of the transmission cause.
6. frame length (range [64 bytes, 255 bytes]): if an IED cannot manage frame whose
length is superior to 255, the frame length attribute must be set to the available length
for the IED.
IED answer is awaited when the computer asks it an information.
8. synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation
period of the IED by the computer.
10. Type of link (Balanced / Unbalanced): if unbalanced link, only master (here computer)
asks IED. If balanced link, IED can also ask the master (here computer) without
sollicitation.
11. test frame time-out (range [1 s, 255 s], step 1 s): in case of ‘balanced link’ (cf.
attribute (10)), a life message (test frame) is sent periodically between computer and
IED. This attribute corresponds to maximum delay to receive this life message, to
computer’s point of view. If no reception within this delay, IED is set disconnected.
12. inter frame duration (range [1, 50 ], step 1): this attribute represents the minimum
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
FIGURE 37: SETTING ACQUISITION ATTRIBUTES OF A T101 LEGACY NETWORK

4.7.1.5 Setting acquisition attributes of a Modbus legacy network
When adding a Modbus legacy network, the following attributes, available for all its IEDs,
must be updated:
disconnected.
IED answer is awaited when the computer asks it an information.
3. synchronisation (none / AREVA / SEPAM) : refer to section 4.3.5.2 of chapter
C264/EN CT for details and to the reference document of the connected IED).
period of the IED by the computer. Only significant if attribute (3) is set to ‘AREVA’ or
to SEPAM.
5. downgraded cycle (range [1s, 10 s], step 100 ms): if an IED is set disconnected by
6. inter frame duration (range [1, 50], step 1): this attribute represents the minimum
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 38: SETTING ‘ACQUISITION’ ATTRIBUTES OF A MODBUS LEGACY NETWORK

4.7.1.6 Setting acquisition attributes of a DNP3 legacy network

When adding a DNP3 legacy network, the following attributes, available for all its IEDs, must
be updated:
1. master address : computer address on the DNP3 legacy network.
IED answer is awaited when the computer asks it a information.
disconnected.
4. application time-out (range [0 s, 255 s], step 1 s): time-out used by the computer, at
application layer of DNP3 protocol.
5. class 0 polling period (range [0 s, 3600 s], step 1 s): emission period of the general
request message. If this attribute equals zero, no general request message is sent.
period of the IED by the computer.
8. inter frame duration (range [1, 50], step 1): this attribute represents the minimum
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 39: SETTING ACQUISITION ATTRIBUTES OF A DNP3 LEGACY NETWORK

4.7.1.7 Adding an IED to a legacy network

To create an IED on a legacy network:
• Add an IED from object entry available at ‘Legacy networks’ level (1).
• Update the IED attributes relevant to its protocol characteristics.
• For DNP3, T103, or Mobdus IED, update the ‘has for acquisition profile’ relation with a
previously created IED acquisition type.
(1)
FIGURE 40: ADDING AN IED TO A LEGACY NETWORK
updated relation
netween IED and
IED acquisition type
C0176ENb
FIGURE 41: LINKING IED ACQUISITION PROFILE TO AN IED

4.7.1.8 Setting attributes of a legacy IED
Whatever the kind of IED, the following attributes must be updated:
1. short name and long name: used for correct logging and alarm discrimination
concerning IED status datapoint.
2. network address of the IED on the legacy network (4 byte-address).
3. automatic disturbance (No / Yes): unavailable for DNP3 IED.
4. localisation for disturbance file: non-significant for DNP3 IED, used for basic file
name upload by SMT on OWS hard disk: <localisation>_N#.
(1)
(2)
(3)
(4)
FIGURE 42: SETTING GENERAL ATTRIBUTES OF A LEGACY IED

• For each IED, its "network address" and "short name" attributes value must be unique,
per Legacy Network.
4.7.1.9 Adding an IED acquisition type to a legacy network
Common acquisition and communication characteristics are shared by IEDs. These ones are
grouped in an object called ‘IED acquisition type’, similar to acquisition profile. It is available
for DNP3, T103 and Modbus protocols.
To create an IED acquisition type on a legacy network:
• Add an IED acquisition from object entry available at legacy network level (1).
• Update the IED acquisition type attributes relevant to its protocol characteristics.
(1)
FIGURE 43: ADDING AN IED ACQUISITION TYPE TO A LEGACY NETWORK

(E.G. FOR DNP3)
• For each computer and all its Legacy Networks, the maximum count of "xxx acq type"
components is 10.
4.7.1.10 Setting attributes of a T103 acquisition type

When adding a T103 acquisition type, the following attributes, available for all its linked IEDs,
must be updated:
1. IED type (T103 standard IED / Px3x Serie / Px2x Serie / REG-D / Tapcon 240)
2. function type (range [0, 255]: function type number used for acquisition: see IED
documentation to set correctly this attribute
3. general interrogation period (range [0, 24 h], step 1 s): cycle used to fetch regularly
statuses and measurements from IED and to avoid loss of event information
4. MV reduction coefficient (1.2 / 2.4 ): used for scaling (ASDU 3 usage): refer to T103
documentation for details about this scaling
5. Four sets of three nominal values (voltage, current and frequency) used for scaling.
Refer to International Standard IEC 60870-5-103 for details about this scaling.
(1)
(2)
(3)
(4)
(5)
FIGURE 44: SETTING ATTRIBUTES OF A T103 ACQUISITION TYPE

4.7.1.11 Setting attributes of a MODBUS acquisition type

When adding a Modbus acquisition type, the following attributes, available for all its linked
IEDs, must be updated:
1. IED type (Modicon / M300 / MICOM S20 / M230 / WAGO): by default use ‘Modicon’.
2. MODBUS function (1 / 2 / 3 / 4 / 7 / 8 ): function number used for polling frame: To
test the IED connection, this attribute gives which Modbus function is used. For
AREVA IED product, the function 7 is generally used.
3. mapping address (range [0, 232-1]): associated to attribute (2), it gives which start
address is used to test the IED connection
− if MODBUS function is set to 1 or 2 this attributes defines a bit address
− if MODBUS function is set to 3 or 4 this attributes defines a word address
− if MODBUS function is set to 5 this attributes is not significant
− if MODBUS function is set to 8 this attributes defines a sub-code
− if MODBUS function is set to 7 this attributes is not significant

4. size to read (range [0, 2048]: associated to attribute (3), it gives which length is used
to test the IED connection.
− if MODBUS function is set to 1 or 2 this attributes defines a number of bits
− if MODBUS function is set to 3 or 4 this attributes defines a number of words
− if MODBUS function is set to 7 or 8 this attributes is not significant

5. data frame length (range [2 bytes, 256 bytes]): if an IED cannot manage frames
longer than 256 bytes, this attribute must be set to the available length for the IED.
(1)
(2)
(3)
(4)
(5)
FIGURE 45: SETTING ATTRIBUTES OF A MODBUS ACQUISITION TYPE

4.7.1.12 Setting attributes of a DNP3 acquisition type

When adding a DNP3 acquisition type, some attributes available for all its linked IEDs must
be updated:
1. global class usage (No / Yes): used for addressing. Not yet implemented. Always
considered as ‘yes’ at computer level.
2. synchronisation type (Network synchronisation / External synchronisation): in case
of network’ synchronisation, computer synchronises the time of the IED, otherwise the
synchronisation is assumed independently by an external equipment directly
connected to the IED. Not yet implemented. Always considered as ‘Network
synchronisation’ at computer level.
3. CROB parameters (Usage of 'code' field / Usage of 'Trip/Close' field / Usage of 'code'
and 'trip/close' fields):
(1)
(2)
FIGURE 46: SETTING ATTRIBUTES OF A DNP3 ACQUISITION TYPE

4.7.2 Defining addressing mapping of a legacy IED
To transmit information between IED and PACiS system, an IED legacy network connected
to a PACiS computer is used.
To receive or send information between legacy IED and PACiS system, each concerned
data must have a specific address on the legacy network relatively to its protocol. General
modelling of legacy network address mapping can be done. At SCE level, an IED of a legacy
network owns an “IED mapping” object, that is split in categories of mapping on a per
datapoint kind basis. In each category of mapping, elementary IED addresses can be
created. For details about datapoint, refer to section 5 DEFINING DATAPOINT. This
mapping is implicitly created during IED adding at legacy network level. Addressing a MPS
datapoint on legacy IED is not available.
created DO
C0355ENa
FIGURE 47: STRUCTURE OF THE ADDRESSING MAPPING OF LEGACY IED

(E.G. FOR T101 IED)
For details about addressing mapping of a given IED on a specific protocol, refer to relay
documentation.
In the IED Mapping, the address identification of each "xxx addr. on IED" must be unique.
• DNP3: address identification is given by the attribute "address" of the "xxx addr. on
IED".
• MODBUS:address identification is made of the following combinations of its attribute

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

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

values:
- { "information object address" , "common address of ASDU" }
- { "information object address" }
4.7.2.1 Defining an IED address for a SPS datapoint

The addition of an IED address for a SPS datapoint is done via the “Objects entry” window at
IED SPS mapping level by clicking on mouse’s right button.
FIGURE 48: ADDING AN IED SPS ADDRESS (E.G. FOR T101 IED)
Once added, IED SPS address attributes must be set at SCE level:
1. short name: used for internal SCE identification.
For Modbus protocol:
2. mapping address (range [0, 65535],step 1): word address or bit address depending
on the bit number attribute.
3. bit number (range [0, 65535],step 1): used only if word read or status read is used
(see function attribute).
4. fonction (range [0, 65535],step 1): number of the Modbus function used to read the
SPS:
- 1, 2 : read bit,
- 3, 4 : read word,
- 7 : read status
For T101 protocol:
5. information object address (range [0, 16777215],step 1).
6. common address of ASDU (range [-1, 65535],step 1): by default (–1) is equal to IED
address (see section 4.7.1.8 Setting attributes of a legacy IED).
For T103 protocol:
7. ASDU number (range [0, 65535],step 1):
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
8. fonction type (range [0, 65535],step 1).
9. information number (range [0, 65535],step 1).
address (see section 4.7.1.8 Setting attributes of a legacy IED.).
For DNP3 protocol:

11. address (range [0, 65535],step 1).
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103 (7)
(8)
(9)
(10
)
DNP3
(11
)
FIGURE 49: DEFINING AN IED ADDRESS FOR A SPS DATAPOINT

4.7.2.2 Defining an IED address for a DPS datapoint

The addition of an IED address for a DPS datapoint is done via the “Objects entry” window at
IED DPS mapping level by clicking on mouse’s right button.
FIGURE 50: ADDING AN IED DPS ADDRESS (E.G. FOR T101 IED)
Once added, IED DPS address attributes must be set at SCE level:
1. short name of the address: used for internal SCE identification.
2. mapping address (range [0, 65535],step 1): Word address or Bit address depending
on bit number attribute.
3. bit number (range [0, 65535],step 1): Used only if Word read or status read is used
(see function attribute).
4. fonction (range [0, 65535],step 1): Modbus function to use to read the DPS:
- 1, 2 : read bit,
- 3, 4 : read word,
- 7 : read status
For T101 protocol:
For T103 protocol:
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
8. fonction type (range [0, 65535],step 1): refer to relay documentation.
9. information number (range [0, 65535],step 1): refer to relay documentation.
For DNP3 protocol:
For all protocol types, DPS acquisition on IED can also be done via two different addresses.
In that case, two ‘DPS address on IED’ must be created for this DPS. For each of them, the
attribute contact identifier (12) must be set to ‘Open’ or ‘Closed’, to precise which state of
the DPS is concerned by the IED address. If DPS status is given by only one IED address,
set ‘contact identifier’ value to ‘unused’.
Modbus
(1)
(2)
(3)
(4)
(12
)
T101
(5)
(6)
(12
)
T103
(7)
(8)
(9)
(10
(12 )
)
DNP3
(11
)
(12
)
FIGURE 51: DEFINING AN IED ADDRESS FOR A DPS DATAPOINT

4.7.2.3 Defining an IED address for a MV datapoint
The addition of an IED address for a MV datapoint is done via the “Objects entry” window at
IED MV mapping level by clicking on mouse’s right button.
Once added, IED MV address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): Word address
3. fonction (range [0, 65535],step 1): Modbus function to use to read the MV:
- 3, 4 : read word,
- 7 : read status
4. data format: see following paragraph (Measurement formats that can be used with
the MODBUS protocol).
For T101 protocol:

For T103 protocol:
- 3, 4, 9 (for all IED)
- 21 (for acquisition of measurement with "generic Services"
- 77 (Only for Px2x)
- 73 (Only for Px3x)
8. fonction type (range [0, 65535],step 1).
9. information number (range [0, 65535],step 1).
10. index in the ASDU (range [0, 65535],step 1).
address.
12. unit of the MEAS (Voltage / Current / Power / Frequency / No Unit).
13. substituted if unknown (No / Yes)
For this protocol it is possible to perform acquisition of measurements only using the Generic
Services of IEC 60870-5-103 protocol by polling. This can be done by setting some
parameters as follows:
− ASDU number: 21
− function type 254
− information number: 244
− index in the ASDU: Generic Identification Number given by the mapping of the IED
For DNP3 protocol:
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103
(7)
(8)
(9)
(10
(11 )
) (12
(13 )
)
DNP3
(14
)
FIGURE 52: DEFINING AN IED ADDRESS FOR A MV DATAPOINT

Measurement formats that can be used with the MODBUS protocol

Because the Modbus norm only describes the transmission of 16 bits values (transmission of
the high order byte first), new formats must be defined to describe the different ways to
transmit 32 bits values (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 are
numbered from 1 (lowest order byte) to 4 (highest order byte).
Transmission
Format Description
order
INT8_LB Transmission of an 8 bit signed integer in a 16 bit value. /
The significant byte is the low order byte of the word.
INT8_HB Transmission of an 8 bit signed integer in a 16 bit value. /
The significant byte is the high order byte of the word.
UINT8_LB Transmission of an 8 bit unsigned integer in a 16 bit value. /
The significant byte is the low order byte of the word.
UINT8_HB Transmission of an 8 bit unsigned integer in a 16 bit value. /
The significant byte is the high order byte of the word.
INT16 Transmission of a 16 bit signed integer. The high order 2-1
byte is transmitted first (see Modbus norm)
UINT16 Transmission of a 16 bit unsigned integer. The high order 2-1
byte is transmitted first (see Modbus norm)
INT32_LW_LB Transmission of a 32 bit signed integer. The low order 1-2-3-4
word of the long value is transmitted first. The low order
byte of each word is transmitted first.
INT32_LW_HB Transmission of a 32 bit signed integer. The low order 2-1-4-3
word of the long value is transmitted first. The high order
INT32_HW_LB Transmission of a 32 bit signed integer. The high word of 3-4-1-2
the long value is transmitted first. The low byte of each
word is transmitted first.
INT32_HW_HB Transmission of a 32 bit signed integer. The high order 4-3-2-1
UINT32_LW_LB Transmission of a 32 bit unsigned integer. The low order 1-2-3-4
UINT32_LW_HB Transmission of a 32 bit unsigned integer. The low order 2-1-4-3
UINT32_HW_LB Transmission of a 32 bit unsigned integer. The high order 3-4-1-2
UINT32_HW_HB Transmission of a 32 bit unsigned integer. The high order 4-3-2-1
REAL32_LW_LB Transmission of a 32 bit real value. The low order word is 1-2-3-4
transmitted first. The low order byte of each word is
transmitted first.
Transmission
Format Description
order
REAL32_LW_HB Transmission of a 32 bit real value. The low order word is 2-1-4-3
transmitted first. The high order byte of each word is
transmitted first.
REAL32_HW_LB Transmission of a 32 bit real value. The high order word is 3-4-1-2
transmitted first. The low order byte of each word is
transmitted first.
REAL32_HW_H Transmission of a 32 bit real value. The high order word is 4-3-2-1
B transmitted first. The high order byte of each word is
transmitted first.
M230_T5_TYPE Transmission of a 32 bit : Unsigned Measure 4-3-2-1
Bit 31to 24 decimal exposant (signed 8 bytes)
Bit 23…00 binary unsigned value 24 bytes
M230_T6_TYPE Transmission of a 32 bit : Signed Measure 4-3-2-1
Bit 31to 24 decimal exposant (signed 8 bytes)
Bit 23…00 binary signed value 24 bytes
M230_T7_TYPE Transmission of a 32 bit: power factor 4-3-2-1
Bit 31to 24 Signed :Import / Export (00/FF)
Bit 23…16 Signed :Inductive / capacitive (00/FF)
Bit 15…00 Unsigned value (16 bytes)
ION_MODULUS Transmission of a 32 bit: ION Energy values 4-3-2-1
_10000_unsigne
Bit 31to 16 reg Hight: RH= unsigned value/10000
d
Bit 15…00 reg Low : RL = unsigned value modulus 10000
Value = RH*10000+RL
ION_MODULUS Transmission of a 32 bit: ION Energy values 4-3-2-1
_10000_signed
Bit 31to 16 reg Hight: RH= signed value/10000
Bit 15…00 reg Low : RL = signed value modulus 10000
Value = RH*10000+RL
Both reg high and low are signed
4.7.2.4 Defining an IED address for a Counter datapoint

The addition of an IED address for a Counter datapoint is done via the “Objects entry”
window at IED Counter mapping level by clicking on mouse’s right button.
FIGURE 53: ADDING AN IED COUNTER ADDRESS (E.G. FOR T101 IED)
Once added, an IED Counter address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): word address.
3. fonction (range [0, 65535],step 1): Modbus function used to read the MV:
- 3, 4 : read word
4. data format: similar to MV.
For T101 protocol:
6. common address of ASDU (range [-1, 65535], step 1): by default (–1) is equal to IED
address.
For T103 protocol:
8. function type (range [0, 65535],step 1):
9. information number (range [0, 65535],step 1):
10. index in the ASDU (range [0, 65535],step 1):
11. common address of ASDU (range [-1, 65535],step 1):
For DNP3 protocol:
12. address (range [0, 65535],step 1):
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103
(7)
(8)
(9)
(10
)
(11
DNP3
)
(12
)
FIGURE 54: DEFINING AN IED ADDRESS FOR A COUNTER DATAPOINT

4.7.2.5 Defining an IED address for a SPC datapoint

The addition of an IED address for a SPC datapoint is done via the “Objects entry” window at
IED SPC mapping level by clicking on mouse’s right button.
FIGURE 55: ADDING AN IED SPC ADDRESS (E.G. FOR T101 IED)
Once added, IED SPC address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): Bit address for function 5 or 15, Word
address for function 6.
3. bit number (range [0, 65535],step 1): Used only if Function 6 is used (see function
attribute).
4. function (range [0, 65535],step 1): Modbus function to use to send the SPC:
- 5 : write 1 bit (Mapping address indicates the address of the bit),
- 6 : write 1 word (Mapping address indicates the address of the word, bit number
indicates the number of the bit in the word),
- 15 : write N bits (used to set only 1 bit at a time, Mapping address indicates the
address of the bit)
For T101 protocol:
address.
For T103 protocol:
- 20 (for all IED)
- 45,46 (Only for Px3x)
8. function type (range [0, 65535],step 1): refer to relay documentation.
For DNP3 protocol:
Modbus (1)
(2)
(3)
(4)
unused
T101
(5)
(6)
unused
T103 (7)
(8)
(9)
unused
DNP3
(10)
)
unused
C0178ENb
FIGURE 56: DEFINING AN IED ADDRESS FOR A SPC DATAPOINT

4.7.2.6 Defining an IED address for a DPC datapoint

The addition of an IED address for a DPC datapoint is done via the “Objects entry” window
at IED DPC mapping level by clicking on mouse’s right button.
FIGURE 57: ADDING AN IED DPC ADDRESS (E.G. FOR T101 IED)
Once added, IED DPC address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): Bit address for function 5 or 15, Word
address for function 6.
3. bit number (range [0, 65535],step 1): used only if Function 6 is used (see function
attribute).
4. function (range [0, 65535],step 1): Modbus function to use to send the DPC:
- 5 : write 1 bit (Mapping address indicates the address of the bit),
indicates the number of the bit in the word),
- 15 : write N bits (used to set only 1 bit at a time, Mapping address indicates the
address of the bit)
For T101 protocol:
address.
For T103 protocol:
- 20 (for all IED)
- 45,46 (Only for Px3x)
For DNP3 protocol:
For all protocols:

11. contact type (open / close / unused): For all protocol type, DPC control on IED can
also be done via two different addresses. In that case, two ‘DPC address on IED’ must
be created for this DPC. For each of them, this attribute must be set to ‘Open’ or
‘Close’, to precise which order of the DPC is concerned by the IED address. If DPC
control is given by only one IED address, set ‘contact type’ value to ‘unused’.
Modbus (1)
(2)
(3)
(4)
(unused)
(11
)
T101
(5)
(6)
(unused
(11 )
)
T103 (7)
(8)
(9)
(unused)
(11)
DNP3
(10)
(unused)
(11)
C0179ENb
FIGURE 58: DEFINING AN IED ADDRESS FOR A DPC DATAPOINT

4.7.2.7 Defining an IED address for a SetPoint datapoint

The addition of an IED address for a SetPoint datapoint is done via the “Objects entry”
window at IED SetPoint mapping level by clicking on mouse’s right button.
FIGURE 59: ADDING AN IED SETPOINT ADDRESS (E.G. FOR T101 IED)
Once added, IED SetPoint address attributes must be set at SCE level:
SetPoint address on Modbus is only available for WAGO relay, where output format is fixed
to UINT16.
2. mapping address (range [0, 65535],step 1): Word address for function 6.
3. function (range [0, 65535],step 1): Modbus function to use to send the SetPoint:
indicates the number of the bit in the word).
For T101 protocol:
5. output format (REAL32 (IEEE 754) / Normalized / Scaled).
For T103 protocol:
6. SetPoint address on T103 is only available for REGD relay, where output format is
configurable.
7. ASDU number (range [0, 65535],step 1): refer to relay documentation.
10. output format (INT8 / UINT8 / INT16 / UNIT16 / REAL32 (IEEE754))
For DNP3 protocol:
For all protocol type, values of SetPoint control on IED must be verified and scaled
depending on output format, before transmission. This is done via two extra attributes
‘minimal value’ (11) and ‘maximal value’ (12).
Modbus (1)
(2)
(3)
(unused)
(11)
(12)
T101 (4)
(unused)
(5)
(11)
(12)
(6)
T103
(7)
(8)
(unused)
(9)
(11)
(12)
DNP3 (10)
(unused)
(11)
(12)
C0180ENb
FIGURE 60: DEFINING AN IED ADDRESS FOR A SETPOINT DATAPOINT

4.7.3 Addressing a datapoint on an IED legacy network
Protocol
DP type Identifier DNP3 ModBus T103 T101

basic address Mapping
default address address ASDU number Not used
extra address #1 Not

default used Not used fonction type Not used
extra address #2 Not Information object

Counter
default used fonction information number address
extra address #3 Not common address

default used Not used index in the ASDU of ASDU
extra address #4 Not common address of

default used Not used ASDU Not used
Mapping
basic address address address ASDU number Not used

default used bit number fonction type Not used
xPC
extra address #3 Not common address

default used Not used Not used of ASDU
Mapping

default used bit number fonction type Not used
xPS
extra address #3 Not common address of common address

default used Not used ASDU of ASDU
Mapping

default used Not used fonction type Not used
MV extra address #2 Not Information object


default used Not used index in the ASDU Not used

Mapping
Set default used bit number fonction type Not used
point
4.8 Networking SCADA on computer SCADA network

4.8.1 Creating a SCADA network
An electrical substation can be supervised and controlled from many points inside the
substation via PACiS operator interfaces (Substation Control Point or SCP) and/or PACiS
computer bay panels (Bay Control Point or BCP), and outside the substation. Generally, the
distant control of the substation (Remote Control Point or RCP) is done via specific networks
called SCADA legacy network.
Several SCADA legacy networks can be connected to a PACiS system, via PACiS computer
or PACiS telecontrol gateway sub-systems. SCADA legacy networks are managed as
master by distant SCADA and can be redundant for safety reason. A PACiS computer can
manage up to two SCADA networks.
At SCE data modelling level, only SCADA legacy networks and their protocol are modelled
and connected to gateway sub-systems. Each SCADA network has to be linked to a main
communication port and eventually an auxiliary communication port in case of redundancy.
4.8.1.1 Adding a SCADA network
To create a SCADA network on a computer:
• Add a SCADA network from object entry available at computer level (1),
• Update the SCADA network attributes relevant to its protocol characteristics (see
section 4.8.2 Defining addressing mapping of SCADA network).
• If SCADA does not use the substation network to communicate with the computer,
update its ‘has for main communication port’ relation and the communication port
characteristics.
• For DNP3 and T101 protocol on serial line, SCADA link can be redundant. To create a
redundant SCADA link, just add the relation ‘has for auxiliary communication port’ (2)
extra relation on computer SCADA network and fill it with the relevant serial port.
• A computer can manage up to two T104 SCADA clients. These two clients have
separate configurations but may have same data. On the SCADA port, up to four front
ends can be defined, corresponding to one active port and three backup ports. So, up
to four IP addresses will be defined during the configuration of each T104 client (
attributes (13) in section 4.8.1.6 Setting specific attributes of a T104 SCADA
network.) If both clients are communicating with the computer, they must manage
thein own redundancy for doing controls with coherency.
(1)
FIGURE 61: ADDING A SCADA NETWORK

(2)
FIGURE 62: CREATING A REDUNDANT SCADA LINK

4.8.1.2 Setting general attributes of a SCADA network
Whatever the kind of SCADA network, its short name and long name attributes (1) must be
updated for correct logging and alarm discrimination concerning status datapoints managed
by the computer for each connected SCADA network. Then the supported protocol (2) must
be selected (T101 in the example given hereafter). So the SCADA attributes tab-panes
(Protocol, SOE and Disturbance) are refreshed relatively to the selected protocol.
(1)
(2)
(3)
(4)
FIGURE 63: SETTING GENERAL ATTRIBUTES OF A SCADA NETWORK

4.8.1.3 Setting general attributes of a T101 SCADA network
When adding a T101 SCADA network its general attributes must be updated (refer to the
previous figure)
3. redundancy type (Active line after GI received / Active line after Reset line received /
Active line on trafic):
4. time reference (UTC / local):
4.8.1.4 Setting specific attributes of a T101 SCADA network

When adding a T101 SCADA network, the following attributes available for this protocol must
be updated (Protocol and SOE tab-panes):
1. link address length (1 byte / 2 bytes)
2. link address (range [1, 65534], step 1)
3. ASDU common address length (1 byte / 2 bytes)
4. ASDU common address (range [1, 65534], step 1)
5. address structure (Address on 8 bits (1 byte) / Address on 16 bits (2 bytes) / Address
on 8 bits.8 bits / Address on 8 bits.16 bits / Address on 16 bits.8 bits / Address on 8
bits. 8 bits. 8 Bits / Address on 24 bits (3 bytes))
6. frame max length (range [1, 255], step 1)
7. cause of transmission length (Address on 8 bits / Address on 16 bits)
8. MV periodic cycle (range [0 s, 65534 s], step 1 s)
9. binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
10. background scan cycle (range [0 s, 65535 s], step 1 s)
11. type of link (unbalanced / balanced)
12. T3: test frame time-out (range [1 s, 255 s], step 1 s)
13. SBO time-out (range [0 s, 65535 s], step 1 s)
14. interframe duration (range [1, 50], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames
15. validity for 'Jammed' state (Valid / Invalid)
16. SOE file support (No / Yes)
17. SOE file address: this attribute is visible and significant only if attribute SOE file
support is set to Yes
18. SOE file format (T101 / S900) this attribute is visible and significant only if attribute
SOE file support is set to Yes
19. SOE file nb of events (range [0, 1000], step 1) this attribute is visible and significant
only if attribute SOE file support is set to Yes
20. 'full' SOE file nb of events (range [0, 1000], step 1) file message sent to SCADA
(this attribute is visible and significant only if attribute SOE file support is set to Yes)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18 )
(19)
(20)
FIGURE 64: SETTING PROTOCOL AND SOE ATTRIBUTES OF A T101 SCADA NETWORK
The following constraints between the attributes must be respected :
"SOE file nb of events" > "'full' SOE file nb of events".
4.8.1.5 Setting general attributes of a DNP3 SCADA network
In the following figure the selected protocol for the SCADA link is ‘DNP3’ (1).
(1)

When setting a DNP3 SCADA network, some specific attributes available for the protocol
must be updated (Protocol tab-pane):
1. TCP/IP usage (No / Yes): set to ‘Yes’ if substation network is used by the DNP3
SCADA to communicate with the computer
2. Link address (1..65534)
3. SPS/DPS class ( 1 / 2 / 3)
4. MV class ( 1 / 2 / 3)
5. Counter ( 1 / 2 / 3)
6. MV format (32 bits / 16 bits)
7. static MV (without flag / with flag)
8. event MV (without time, with time)
9. counter format (32 bits / 16 bits)
10. static counter (without flag / with flag)
11. event counter (without time, with time)
12. SBO time-out: maximum time between select orde and execute order
time, expressed in number of characters, that must exist between two frames
14. spontaneous message enable ( No / Yes): this attribute defines if the unsolicited
mode is allowed or not for the protocol. If this attribute is set to No there is possibility
to allowed it from the SCADA. If this attribute is set to Yes the computer can send
unsolicited messages as soon as the SCADA is initialiazed. Furthermore the SCADA
may disable or enable this unsolicited mode.
15. spontaneous message class ( none / class 1 / class 2 / class 1 & 2 / class 3 / class 1
& 3 / class 2 & 3 / class 1 & 2 & 3): This attribute is only significant if the previous
attribute is set to Yes. This attribute defines which class(es) is (are) concerned by this
unsolicited mode.
Setting SOE information SOE tab-panes, for DNP3 SCADA network is not significant (not
implemented).
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
) (14)
(15)
FIGURE 66: SETTING PROTOCOL ATTRIBUTES OF A DNP3 SCADA NETWORK

4.8.1.6 Setting specific attributes of a T104 SCADA network

In the following figure the selected protocol for the SCADA link is ‘T104’ and the selected
time reference is UTC.
(1)

When setting a T104 SCADA network, some specific attributes available for the protocol
must be updated (Protocol and SOE tab-panes):
1. ASDU common address (range [1, 65534], step 1)
2. address structure (Address on 8 bits.16 bits / Address on 16 bits.8 bits /
Address on 8 bits.8bits.8bits / Address on 24 bits (3 bytes)):
3. frame max length (range [1, 255], step 1)
4. MV periodic cycle (range [0 s, 65534 s], step 1 s)
5. binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
6. background scan cycle (range [0 s, 65535 s], step 1 s)
7. T1: APDU time-out (range [1 s, 255 s], step 1 s)
8. T2: acknowledgement time-out (range [1 s, 255 s], step 1 s)
9. T3: test frame time-out (range [1 s, 255 s], step 1 s)
10. K: sent unack. frames (APDU) (range [1, 255], step 1)
11. W: ack. received frames (APDU) (range [1, 255], step 1)
12. max command delay (range [0 s, 32767 s], step 1 s)
13. socket IP #i (i ∈ [1, 4])

14. SBO time-out (range [0 s, 65535 s], step 1 s)
15. validity for 'Jammed' state (Valid / Invalid)
16. Switchover (Automatic switchover / Manual switchover)
17. SOE file support (No / Yes)
18. SOE file address (this attribute is visible and significant only if attribute SOE file
support is set to Yes)
19. SOE file format (T101 / S900) (this attribute is visible and significant only if attribute
SOE file support is set to Yes)
20. SOE file nb of events (range [0, 1000], step 1) (this attribute is visible and significant
only if attribute SOE file support is set to Yes)
21. 'full' SOE file nb of events (range [0, 1000], step 1) file message sent to SCADA
(this attribute is visible and significant only if attribute SOE file support is set to Yes)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10
(11 )
) (12
(13 )
) (14
(15 )
) (16
)
(17
) (18
(19 )
) (20
(21 )
)
FIGURE 68: SETTING SPECIFIC ATTRIBUTES OF A T104 SCADA NETWORK

• The following constraints between the attributes must be respected :

"SOE file nb of events" > "'full' SOE file nb of events"
"T2" < "T1"
"T3" > "T1"
"W" ≤ "K"
4.8.1.7 Setting specific attributes of a MODBUS SCADA network

In the following figure the selected protocol for the SCADA link is ‘Modbus’.
(1)
FIGURE 69: SETTING PROTOCOL TYPE OF A SCADA NETWORK

When setting a MODBUS SCADA network, some specific attributes available for the protocol
must be updated (Protocol tab-pane):
1. TCP/IP usage (No / Yes): set to ‘Yes’ if substation network is used by the MODBUS
SCADA to communicate with the computer.
2. link address: not significant if TCP/IP usage is set to ‘Yes’.
For a MODBUS SCADA network, the SOE tab-panes attributes are not significant (not
implemented).
(1)
(2)
(3)
FIGURE 70: SETTING PROTOCOL ATTRIBUTES OF A MODBUS SCADA NETWORK

4.8.2 Defining addressing mapping of SCADA network

To transmit information between PACiS system and SCADA, a SCADA legacy network is
used. To receive or send information between legacy IED and PACiS system, each
concerned data must have a specific address on the legacy network relatively to its protocol.
General modelling of SCADA legacy network address mapping can be done. At SCE level, a
SCADA legacy network owns a “SCADA mapping” object, that is split in categories of
mapping on a per datapoint kind basis. In each category of mapping, elementary SCADA
addresses can be created. For details about datapoint, refer to section 5 DEFINING
DATAPOINT. This mapping is implicitly created during IED adding at legacy network level.
WARNING: ADDRESSING A MPS DATAPOINT ON A SCADA NETWORK IS NOT
AVAILABLE.
Entry point
of SCADA
mapping
Categories
per datapoint
kind basis
C0181ENb
FIGURE 71: STRUCTURE OF THE ADDRESSING MAPPING OF A SCADA NETWORK

• In the SCADA Mapping, the address identification of each "Gtw xxx addr." must be
unique. In the particular cases of T101 and T104 protocols, the uniqueness constraint
is applicable only for addresses of the same type. Addresses of different types can
have identical addresses and therefore this does not lead to an error but to a warning.
• On a DNP3 protocol, a "Gtw MV addr.", which is the SCADA address of a "Tap pos
ind" datapoint, must have its "Format" attribute set to the "Natural" value.
4.8.2.1 Defining a SCADA address for a SPS datapoint
The addition of a SCADA address for a SPS datapoint is done via the “Objects entry”
window at SCADA SPS mapping level by clicking on mouse’s right button.
FIGURE 72: ADDING A SCADA SPS ADDRESS

Once added, SCADA SPS address attributes must be set at SCE level:
1. shortname of the address used for internal SCE identification.
2. object address - register
For T101/T104 protocol:
3. object address.
4. Event (No / Yes with time tag / Yes witout time tag): when set to ‘Yes with time tag’,
indicates that change of state of the datapoint are transmitted spontaneously with time
Tag.
5. Event record ( Does not involved in a transfert of file / Create a RECORD EVENT if
there is not it current / Add to the current record EVENT / Create a RECORD EVENT
and adds to the current record EVENT): when set to a value different from ‘Does not
involved in a transfer of file’, indicates if change of state of the datapoint must be
saved in Sequence of Event file. At computer level, values different from ‘Does not
involved in a transfer of file’ are associated to the same treatment, because only one
SOE file is managed by computer. The set of available values is maintained for
compatibility with MiCOM gateway addressing in MiCOM gateway.
6. Inversion (No / Yes): Indicates that the datapoint value needs to be inverted before
transmission.
7. Background scan (No / Yes): indicates if the datapoint belongs to the background
scan cycle.
8. Group ([0..16)] / 0=no group): indicates to which “T101/T104 General Interrogation
group” the datapoint is assigned. 0 means ‘no group’ assignation.
For DNP3 protocol:

9. object address - index.
10. Event (No / Yes with time tag): when set to ‘Yes with time tag’, indicates if change of
state of the datapoint are transmitted spontaneously with time Tag.
11. Inversion (No / Yes): indicates that the datapoint value needs to be inverted before
transmission.
Modbus
(1)
(2)
T101/T104
(3)
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
FIGURE 73: DEFINING A SCADA ADDRESS FOR A SPS DATAPOINT

4.8.2.2 Defining a SCADA address for a DPS datapoint

The addition of a SCADA address for a DPS datapoint is done via the “Objects entry”
window at SCADA DPS mapping level by clicking on mouse’s right button.
FIGURE 74: ADDING A SCADA DPS ADDRESS

Once added, SCADA DPS address attributes must be set at SCE level:
1. short name: used for internal SCE identification
2. double address usage (No / Yes): only available for Modbus SCADA protocol. If set
to ‘Yes’, DPS is transmitted to SCADA via two distinct SCADA address, one for the
open state, the other one for the close state.
3. object address - register: used if ‘Double address usage’ is set to ‘No’.
4. open state address: used if ‘Double address usage’ is set to ‘Yes’. This attribute
defines the SCADA address for the open state of the DPS.
5. Closed state address: used if ‘Double address usage’ is set to ‘Yes’. This attribute
defines the SCADA address for the closed state of the DPS.
6. Event (No / Yes with time tag /Yes without time tag): when set to ‘Yes with time tag’,
indicates if change of state of the datapoint are transmitted spontaneously with time
Tag.
7. Event record (Does not involved in a transfert of file / Create a RECORD EVENT if
there is not it current / Add to the current record EVENT / Create a RECORD EVENT
and adds to the current record EVENT): when set to a value different from ‘Not
involved in a transfer of file’, indicates if change of state of the datapoint must be
saved in Sequence of Event file. At computer level, values different from ‘Not involved
in a transfer of file’ are associated to the same treatment, because only one SOE file
is managed by computer. The set of available values is maintained for compatibility
with MiCOM gateway addressing in MiCOM gateway.
transmission.
9. Background scan: (No / Yes): indicates if the datapoint belongs to the background
scan cycle.
10. Group ([0..16)] / 0=no group): indicates to which “T101/T104 General Interrogation
group” the datapoint is assigned. 0 means ‘no group’ assignation
11. object address (index)
For DNP3 protocol:
state of the datapoint are transmitted spontaneously with time Tag
transmission
14. object address - index
Modbus
(1)
(2)
(3)
(4)
(5)
T101/T104
(6)
(7)
(8)
(9)
(10
)
(11)
DNP3
(12)
(13)
(14)
FIGURE 75: DEFINING A SCADA ADDRESS FOR A DPS DATAPOINT

4.8.2.3 Defining a SCADA address for a MV datapoint

The addition of a SCADA address for a MV datapoint is done via the “Objects entry” window
at SCADA MV mapping level by clicking on mouse’s right button.
FIGURE 76: ADDING A SCADA MV ADDRESS

Once added, SCADA MV address attributes must be set at SCE level:
1. short name of the address used for internal SCE identification.
3. Format (Natural / Unsigned normalized / Signed normalized /Real IEEE754 – little
endian / Real IEEE754 – big endian): transmission format.
4. Precision (8..16): number of transmitted bits.
5. object address.
6. Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’,
indicates that change of state of the datapoint are transmitted spontaneously with time
Tag.
7. Event record ( No / Yes): indicates if change of state of the datapoint must be saved
in Sequence of Event file or not..
8. Format (Normalized / Adjusted / Float):transmission format.
9. cycle type (None / Periodic / Background scan): indicates which transmission cycle
the MEAS belongs to.
10. Group ([0..16)] / 0=no group): indicates which “T101/T104 General Interrogation
group” the datapoint is assigned to. 0 means ‘no group’ assignation.
For DNP3 protocol:

11. object address
13. Format (Natural / Adjusted).
Modbus
(1)
(2)
(3)
(4)
T101/T104
(5)
(6)
(7)
(8)
(9)
(10)
DNP3
(11)
(12)
(13)
FIGURE 77: DEFINING A SCADA ADDRESS FOR A MV DATAPOINT

4.8.2.4 Defining a SCADA address for a Counter datapoint

The addition of a SCADA address for a Counter datapoint is done via the “Objects entry”
window at SCADA Counter mapping level by clicking on mouse’s right button.
FIGURE 78: ADDING A SCADA COUNTER ADDRESS

Once added, SCADA Counter address attributes must be set at SCE level:
3. Format (Natural / Unsigned normalized / Real IEEE754 – little endian / Real IEEE754
– big endian): transmission format.
4. object address.
5. Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’,
indicates if changes of state of the datapoint are transmitted spontaneously with time
Tag.
6. Group ([0..4] / 0=no group): indicates which “T101/T104 General Interrogation group”
the datapoint is assigned to. 0 means ‘no group’ assignation.
For DNP3 protocol:
7. object address.
Modbus
(1)
(2)
(3)
T101/T104
(4)
(5)
(6)
DNP3
(7)
(8)
FIGURE 79: DEFINING A SCADA ADDRESS FOR A COUNTER DATAPOINT

4.8.2.5 Defining a SCADA address for a SPC datapoint
The addition of a SCADA address for a SPC datapoint is done via the “Objects entry”
window at SCADA SPC mapping level by clicking on mouse’s right button.
FIGURE 80: ADDING A SCADA SPC ADDRESS

Once added, SCADA SPC address attributes must be set at SCE level:

2. object address - register.
3. object address
4. SCADA execute order type (Select execute / Direct execute): precise if SCADA uses
a ‘Select execute” or a ‘Direct execute’ sequence to send control on the datapoint.
For DNP3 protocol:
5. object address
6. SCADA execute order type (Select execute / Direct execute):precise if SCADA uses
a ‘Select execute” or a ‘Direct execute’ sequence to send control on the datapoint.
Modbus
(1)
(2)
T101/T104
(3)
(4)
DNP3
(5)
(6)
FIGURE 81: DEFINING A SCADA ADDRESS FOR A SPC DATAPOINT

4.8.2.6 Defining a SCADA address for a DPC datapoint

The addition of a SCADA address for a DPC datapoint is done via the “Objects entry”
window at SCADA DPC mapping level by clicking on mouse’s right button.
FIGURE 82: ADDING A SCADA DPC ADDRESS

Once added, SCADA DPC address attributes must be set at SCE level:
3. object address.
4. SCADA execute order type (Select execute / Direct execute): precises if SCADA
uses a ‘Select execute” or a ‘Direct execute’ sequence to send control on the
datapoint.
For DNP3 protocol:
5. object address in [0..65535].
datapoint.
Modbus
(1)
(2)
T101/T104
(3)
(4)
DNP3
(5)
(6)
FIGURE 83: DEFINING A SCADA ADDRESS FOR A DPC DATAPOINT
4.8.2.7 Defining a SCADA address for a SetPoint datapoint

The addition of a SCADA address for a SetPoint datapoint is done via the “Objects entry”
window at SCADA SetPoint mapping level by clicking on mouse’s right button.
FIGURE 84: ADDING A SCADA SETPOINT ADDRESS

Once added, SCADA SetPoint address attributes must be set at SCE level:

3. format.(signed 16 bits / Real IEEE754 – little endian / Real IEEE754 – big endian)
4. object address.
5. SCADA execute order type (Select execute / Direct execute): this attibute defines if
SCADA uses a ‘Select execute” or a ‘Direct execute’ sequence to send control on the
datapoint.
6. Minimal value: available minimal value on the protocol (used for scaling and checks).
7. Maximal value: available maximal value on the protocol (used for scaling and
checks).
8. Format (Normalized / Adjusted / Float).
For DNP3 protocol:
9. object address [0..65535].
datapoint.
11. minimal value: available minimal value on the protocol (used for scaling and checks).
12. maximal value: available maximal value on the protocol (used for scaling and
checks).
13. format (Natural / Adjusted).
Modbus
(1)
(2)
(3)
T101/T104
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
(12)
(13)
FIGURE 85: DEFINING A SCADA ADDRESS FOR A SETPOINT DATAPOINT

4.8.2.8 Defining a SCADA address for bypass synchrocheck

For details about synchronised circuit-breakers, refer to section 6.2 Defining a Synchrocheck
function.
Synchronised circuit-breaker can be controlled through SCADA network. In that case, the
SPC (resp. DPC) control of the synchronised breaker is linked to a SCADA SPC (resp. DPC)
address. Unfortunately, bypass synchrocheck is not implemented in SCADA protocol. To
solve this problem, an extra SCADA SPC (resp. DPC) address that will bypass the
synchrocheck must be given to the SPC (resp. DPC) control of the breaker. At SCE level,
this extra address is linked to the SCADA address of the SPC (resp. DPC) control of the
synchronised breaker.
To define a SCADA address for bypass synchrocheck:
• Create the SCADA SPC (resp. DPC) address (A) to send SPC (resp. DPC) control of
the synchronised breaker.
• Create a SCADA SPC (resp. DPC) address (B) for bypass synchrocheck in the
SCADA mapping.
• Add the relation ‘has for bypass synchrocheck address’ via the “Objects entry” window
at SCADA address (A) and fill it with the SCADA address (B).
address (A)
address (B)
C0347ENa
FIGURE 86: ADDING A BYPASS SYNCHROCHECK ADDRESS TO A SCADA SPC/DPC ADDRESS

(E.G. FOR SCADA DPC ADDRESS)
4.8.3 Addressing datapoint on SCADA legacy network

For details about datapoint, refer to section 5 DEFINING DATAPOINT.
To exchange datapoint values between station-bus sub-systems and SCADA, datapoints
should be linked to specific SCADA addresses, by adding at datapoint level the relation ‘has
for SCADA address’ (1) and filling it with the corresponding SCADA address in a pre-
configured SCADA addressing mapping (refer to section 4.8.2 Defining addressing mapping
of SCADA network, for SCADA mapping definition).
Addressing a MPS datapoint on the SCADA legacy network is not available.
(1)
FIGURE 87: REALISING SCADA ADDRESSING OF A DATAPOINT

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

The C264/C264C computers manage two kinds of wave recording file:
• IED connected to computer legacy network can produce disturbance files. In that
case, computer monitors their availability. As soon as available, they are uploaded
and stored at computer level. Computer computes for System Management Tool
(SMT) a real-time data per IED basis that gives the availability of a disturbance file, via
station-bus network. Then, SMT downloads it from computer. At the end of successful
downloading, computer erases the real-time data of availability.
• Via a CT/VT board (TMU200), computer can manage its own waveform record files.
Waveform channels are directly acquired on CT/VT board channels and buffered.
Triggered by pre-defined change of state, associated buffers are flushed on files that
correspond to waveform record files. In that case computer computes for SMT a real-
time data that gives the availability of a computer waveform record file, via station-bus
network. Then processing is similar to IED’s one.
4.9.1 Defining management of disturbance file for IED
Allowing computer to manage IED disturbance is done at IED configuration level by:
• Setting its ‘automatic disturbance’ attribute to yes.
• Adding RDRE brick (1) for the IED in LD0 logical device of the IEC-61850 mapping of
the computer.
• Adding the system SPS datapoint ‘DREC ready’ (2) at IED level, linked to a pre-
defined datapoint profile.
• Fill the mandatory IEC address for this datapoint, with the relevant data object of the
RDRE brick (3).
(2)
(1)
FIGURE 88: ADDING RDRE BRICK AND DREC READY DATAPOINT FOR IED
(3)
FIGURE 89: SETTING IEC-61850 ADDRESS OF DREC READY DATAPOINT FOR IED
For T103 IED extra information must be configured to process correct disturbance file
COMTRADE structure at computer level (see following section).
4.9.2 Defining T103 IED extra information for disturbance file

T103 extra informations for disturbance file are located at T103 acquisition type and concern
definition of analog and digital channels, stored in disturbance file, relatively to COMTRADE
format.
4.9.2.1 Adding an analog channel definition
The addition of an analog channel definition for T103 is done via the “Objects entry” window
at T103 acquisition type level by clicking on mouse’s right button. Up to 15 analog channels
can be created under a T103 acquisition type.
FIGURE 90: ADDING A T103 ANALOG CHANNEL DEFINITION

Once added, channel definition attributes must be set at SCE level:
1. channel label.
2. long name of the channel used for internal SCE identification.
3. phase name: label of the phase corresponding to the channel.
4. channel number: (cf. mapping IED– field ACC in IEC 60870-5-103 documentation).
5. unit: unit corresponding to the channel.
6. coefficient (0: not used): value which the samples must be multiplied by in order to
get the real value (0: not used). Generally, data uploaded from IED allows to compute
this ‘multiply coefficient’. Unfortunately, some IED don’t give correct data. In this case,
this coefficient must be set here.
7. shift time (range [0 s, 1 s], step 1 µs): elapsed time since the beginning of the
sampling period.
8. maximal sample value (range [0 , 32767], step 1).
9. minimal sample value (range [-32768, 0], step 1)..
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 91: SETTING T103 ANALOG CHANNEL DEFINITION

For more details about the analog channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
4.9.2.2 Adding a digital channel definition

The addition of a digital channel definition for T103 is done via the “Objects entry” window at
T103 acquisition type level by clicking on mouse’s right button. Up to 255 digital channels
can be created under a T103 acquisition type.
FIGURE 92: ADDING A T103 DIGITAL CHANNEL DEFINITION

Once added, channel definition attributes must be set at SCE level:
1. channel label.
2. long name of the channel used for internal SCE identification.
3. function number (range [0 , 255], step 1): corresponds to function type of the channel
in T103 protocol.
4. information number (range [0 , 255], step 1): corresponds to information number of
the channel in T103 protocol.
5. default state (Off / On).
(1)
(2)
(3)
(4)
(5)
FIGURE 93: SETTING T103 DIGITAL CHANNEL DEFINITION

For more details about the digital channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
4.9.3 Defining management of wave record file for computer CT/VT board
Allowing computer to manage its own wave record file is done at computer configuration
level by:
• Defining a fast and/or slow waveform recording (see following sections):
− fast waveform recording gives access to samples acquired via CT/VT board.
− slow waveform recording gives access to analogues (MV) and digital values
(SPS, DPS, SPC, DPC) file recording.
• Adding RDRE brick (1) for the computer in LD0 logical device of the IEC-61850
mapping of the computer.
• Adding the system SPS datapoint ‘C26x DREC ready’ (2) at computer level, linked to
a pre-defined datapoint profile.
• Fill the mandatory address for this datapoint, with the relevant data object of the
RDRE brick (3).
(2)
(1)
FIGURE 94: ADDING A RDRE IEC-61850 BRICK AND A DREC READY DATAPOINT FOR A COMPUTER
(3)
FIGURE 95: SETTING IEC 61850 ADDRESS OF DREC READY DATAPOINT FOR COMPUTER
4.9.3.1 Defining fast waveform recording

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

8 60
4 120
2 240
1 480
The waveform recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of binary inputs (SPS or DPS datapoint)
• Changes in state of digital outputs (SPC or DPC datapoint)
• Measurement threshold violations (MV datapoint)
Only one re-trig is allowed: it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are available in COMTRADE 2001 format.
The addition of a fast waveform recording is done via the “Objects entry” window at
computer level by clicking on mouse’s right button. Only one fast waveform recording can be
created under a computer.
FIGURE 96: ADDING A FAST WAVEFORM RECORDING

Once added, fast waveform recording attributes must be set at SCE level:
1. short name and long name: used for internal SCE identification.
2. pre-trigger cycle (range [0 , 480], step 1): corresponds to number of cycles (up to
480), that are stored before triggering.
3. total cycles (range [0 , 480], step 1): see previous description.
4. number of files (1 / 2 / 4 / 8): see previous description.
(1)
(2)
(3)
(4)
FIGURE 97: SETTING FAST WAVEFORM RECORDING

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

To define the triggers of a fast waveform recording, just add the relevant relation (2)
available at recording level and fill the relation with proper datapoint. Be careful, only
datapoints acquired on the computer can be defined as input of its fast waveform recording.
(2)
FIGURE 99: DEFINING TRIGGERS OF FAST WAVEFORM RECORDING

Depending on the datapoint type, extra attributes must be set for ‘has for trigger’ relation.
These attributes gives the datapoint states (or thresholds for MV) that trig the record (see
following figure).
Triggering state for DPS:

Open,Close or Open+Close

Triggering threshold for MV:

For each threshold:
- no trigger
- trigger on threshold hold
- trigger on threshold reset
and reset
Triggering state for SPC:

Reset Set or Reset + Set
Triggering state for SPS:

Off, On or Off + On
C0183ENb
FIGURE 100: DEFINING TRIGGER CONDITIONS OF FAST WAVEFORM RECORDING


- "pre-trigger cycle" ≤ "total cycles"
- "number of files" ∗ "total cycles" ≤ 480 cycles
4.9.3.2 Defining slow waveform recording

The inputs for the slow waveform records are:
• MV datapoint coming from CT VT computation.
• MV datapoint coming from AIU boards.
• SPS or DPS datapoints.
• SPC or DPC datapoints.

The slow wave form manages up to 24 analogues (MV) and 48 digital values (SPS, DPS,
SPC, DPC).
MiCOM C264 stores at maximum 5000 integrated values as follow:
Number of Files Number of integrated values

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

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

The addition of a slow waveform recording is done via the “Objects entry” window at
computer level by clicking on mouse’s right button. Only one slow waveform recording can
be created under a computer.
FIGURE 101: ADDING A SLOW WAVEFORM RECORDING

Once added, slow waveform recording attributes must be set at SCE level:
1. short name and long name of the recording used for internal SCE identification.
2. pre-trigger cycle (range [0 , 5000], step 1): corresponds to the number of cycles (up
to 480) that are stored before triggering.
3. total records (range [0 , 5000], step 1): see previous description.
4. number of files (1 / 2 / 5 / 10 / 20 / 50): see previous description.
5. arbitration period (range [0 , 100], step 1): this data represents the percentage of
time during which the logical data must be set to 1 to consider the integrated data set
to 1.
6. integration time (range [0 , 216000], step 1): see previous description.
Data unit is number of cycles and has the following range:
- [1, 180000] if electric network frequency is 50 Hz
- [1, 216000] if 60 Hz
(for network frequency configuration, refer to section 4.3.2 Configuring measurement
acquisition and transmission)
7. activation period (Non periodic trigger / Daily trigger / weekly trigger / Daily and
weekly trigger): see previous description.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 102: SETTING FAST WAVEFORM RECORDING

To define the inputs of a slow waveform recording, just add the relevant relation (1) available
at recording level and fill the relation with proper datapoint. Be careful, only datapoints
acquired on the computer can be defined as input of its slow waveform recording.
(1)
FIGURE 103: DEFINING INPUTS OF SLOW WAVEFORM RECORDING

To define the datapoint-triggers of a slow waveform recording, just add the relevant relation
(2) available at recording level and fill the relation with proper datapoint. Be careful, only
datapoints acquired on the computer can be defined as input of its slow waveform recording.
A slow waveform can be configured without any datapoint-trigger, if a daily or weekly
activation period has been defined for it.
(2)
FIGURE 104: DEFINING TRIGGERS OF FAST WAVEFORM RECORDING

Depending on the datapoint type, extra attributes must be set for ‘has for trigger’ relation.
These attributes give the datapoint states (or thresholds for MV) that trig the record (see
following figure).


Triggering threshold for MV:

For each threshold:
- no trigger
- trigger on threshold reset
and reset
Triggering state for SPC:

Reset Set or Reset + Set
Triggering state for SPS:

Off, On or Off + On
C0184ENb
FIGURE 105: DEFINING TRIGGERS CONDITIONS OF SLOW WAVEFORM RECORDING


- "pre-trigger cycle" < "total records"
- "number of files" ∗ "total records" < 5000 records
• If "electrical frequency" ≡ 50 Hz:

- The "integration time" value must be in the range [1..180000].
- If the "integration time" value is > 5, then no DPC, SPC, DPS, SPS recording is
allowed.
• If "electrical frequency" ≡ 60 Hz:

- The "integration time" value must be in the range [1..216000].
- If the "integration time" value is > 6, then no DPC, SPC, DPS, SPS recording is
allowed.
4.10 Defining a computer klaxon

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

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

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

4.11.1 Setting general system information of a computer

When creating a computer, the following mandatory datapoints are implicitly added.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
FIGURE 108: MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR A COMPUTER

These datapoints must be configured (see section 5 DEFINING DATAPOINT) according to
their described features:
• Controls and statuses for functioning mode
− Mode control DPC (9): this datapoint is only used by the SMT to turn device
functioning mode to Maintenance or Operational/Run.
The available states of this datapoint are:
“OPEN” for the Maintenance mode
“CLOSED” for Operational mode
An IEC address for this datapoint is defined by using SBUS automatic addressing.
− Operating mode MPS (10): this datapoint is the MPS equivalence of Device mode
DPS (4).
“STATE 0” for the Faulty mode
“STATE 1” for Operational mode
“STATE 3” for Test mode
“STATE 5” for Maintenance mode
− Test control DPC (18): this datapoint is only used by the SMT to turn device
functioning mode to Test or Normal.
“OPEN” for the Test mode
“CLOSED” for Normal mode
This datapoint has no IEC-61850 address
• Control and status for local/remote
− Local/remote ctrl DPC (5): this datapoint is required by IEC-61850 protocol but is
meaningless for the computer.
“OPEN” for Remote
“CLOSED” for Local
This datapoint has no IEC address
− Local/remote DPS (6):
“OPEN” for Remote
“CLOSED” for Local
− Local/remote SPS (7):
“RESET” for Local mode
“SET” for Remote mode
This datapoint has the "RESET" state if the Local/remore DPS datapoint of all the
bays managed by the computer have the "OPEN" state and has the "SET" state if
at least the Local/remore DPS datapoint of one bay managed by the computer has
not the "OPEN" state.
The IEC-61850 address of this datapoint is defined by using SBUS automatic
addressing.
• Control and status for database management
− Database incoherency SPS (1): this datapoint is put in ‘SET’ state if current
database is not self-consistent. In that case, computer enters the Maintenance
mode.
“RESET” for coherent database
“SET” for incoherent database
− Database switch control SPC (2): this datapoint is only used by the SMT to turn
device functioning mode to Maintenance or Operational/Run.
The available state of this datapoint is:
“ON” for Switch
• Synchronisation status
− Synchronisation SPS (17): this is put in ‘SET’ state if device is synchronised.

“RESET” for not synchronised device
“SET” for synchronised device
An IEC-61850 address for this datapoint is defined by using SBUS automatic
addressing.
• Communication status
− Device link SPS (3): although this datapoint is under the computer, it is not
managed by it. Each IEC-61850 client of the computer computes locally this
datapoint status by supervising the IEC-61850 real-time link with the computer. In
fact, there are as many ‘Device link SPS’ per computer basis as IEC-61850 clients
connected to the computer. Is put in ‘SET’ state if device link is operational.
“RESET” for not OK
“SET” for OK
This datapoint has no IEC address
• Health statuses
− DI acquisition stopped SPS (4): in case of saturation of the internal file used for
acquisition of wired digital inputs and gooses, acquisition is automatically stopped
and this datapoint is put in ‘SET’ state. As soon as this internal file is un-saturated,
this datapoint is reset and acquisition restarts.
“RESET” for acquisition running
“SET” for acquisition stopped
addressing.
− Software error SPS (16): in case of software error, this datapoint is set and
computer enters the Faulty mode.
“RESET” for software running
“SET” for software error
− Watchdog SPS (19): in case of software watchdog time-out, this datapoint is put in
‘SET’ state and computer enters the Faulty mode.
“RESET” for watchdog OK
“SET” for watchdog time-out
− ISaGRAF status MPS (20):

“STATE 0”: Isagraf is running normally
“STATE 1”: Not activated
“STATE 2”: Cycle too long
“STATE 3”: Queue overflow (Isagraf queue has reached overflow limit)
“STATE 4”: An Isafraf POU (Program Organisation Unit) is faulty
addressing.
• Control and statuses for redundancy management:
The four following datapoints are used internally by computer if it is redunded. These
datapoints must be linked to datapoint profiles by default for proper behaviour of
redundancy.
− Redundancy change mode SPS (11)

− Redundancy change status SPS (12)
− Redundancy mode control SPC (13)
− Redundancy status control SPC (14)
These datapoints have no IEC-61850 address.
− Main status MV (8)

addressing.
At computer level, the following optional datapoint can be added.
(21)
(22)
(23)
(24)
FIGURE 109: OPTIONAL ‘SYSTEM INFOS’ DATAPOINTS FOR A COMPUTER

− Counter Top SPS (21): this datapoint is used to launch the transmission of
counters value on IEC-61850 and SCADA networks. Launching is done when the
datapoint goes in ‘SET’ state. This datapoint is generally wired.
“RESET” for no transmission
“SET” for transmission
An IEC-61850 address can be manually added to this datapoint.
− DREC ready SPS (22): this datapoint indicates the availability of a waveform
record file for the computer (for details, refer to section 4.9 Defining wave record
file management).
“RESET” for no waveform record available
“SET” for waveform record file available
addressing.
− External clock status SPS (23): this datapoint indicates the status of the IRIG-B
synchronisation. This datapoint is mandatory if ‘synchronisation source’ attribute at
computer level is set to IRIG-B (for details, refer to section 4.3 Setting general
attributes of a computer). The available states of this datapoint are:
“SET” for lack of IRIG-B signal
“RESET” for IRIG-B signal is present
An IEC-61850 address can be manually added to this datapoint.
− Device mode DPS (24): this datapoint gives the current functioning mode of the
computer.
“JAMMED” for the Test mode
"OPEN" for the Maintenance mode
"CLOSED" for the Operational mode
“UNDEFINED” for the Operational mode
This datapoint has no IEC-61850 address.
4.11.2 Setting system information of board

When creating a board (except CPU board) the following mandatory datapoint is implicitly
added.
(1)
FIGURE 110: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A BOARD

(E.G. FOR AIU BOARD)
− Board status MPS (1): this datapoint indicates the status of the board. Addressing
this datapoint can be done:
1) by using SBUS automatic addressing.
FIGURE 111: AUTOMATIC IEC ADDRESSING OF A BOARD STATUS DATAPOINT

2) Manually. In that case, the relevant data object given the IEC address of the
status, must be coherent with the board number (e.g. if AIU board number is 3,
corresponding data object is AIUSt3).
“STATE 0” for board OK
“STATE 1” for self-check failure
“STATE 2” for configured but missing
“STATE 3” for not configured but present
“STATE 4” for board not present
FIGURE 112: MANUAL IEC ADDRESSING OF A BOARD STATUS DATAPOINT

4.11.3 Setting system information of legacy IED

When creating a legacy IED, the following mandatory datapoints are implicitly added.
(1)
(2)
FIGURE 113: MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR A LEGACY IED

− IED communication status SPS (1): is put in ‘SET’ state if communication with the
IED is operational.
“RESET” for communication not OK
“SET” for communication OK
− IED synchronisation status SPS (2): is put in ‘SET’ state if IED is synchronised.
“RESET” for IED not synchronised
“SET” for IED synchronised
At IED level, the following optional datapoint can be added.
(3)
FIGURE 114: OPTIONAL ‘SYSTEM INFOS’ DATAPOINT FOR A LEGACY IED
− IED disturbance status SPS (2): this datapoint indicates the availability of a
disturbance file for the IED (for details, refer to section 4.9.1 Defining management of
disturbance file for IED). This datapoint is put in ‘SET’ state if a disturbance file is
available.
“RESET” for no disturbance file available
“SET” for disturbance file available
4.11.4 Setting system information of serial printer

When creating a serial printer, the following mandatory datapoint is implicitly added.
(1)
FIGURE 115: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A SERIAL PRINTER
− Printer status MPS (1): this datapoint indicates the status of the printer.
“STATE 0” for printer OK
“STATE 1” for self-check failure
“STATE 4” for printer not present
4.11.5 Setting system information of a SCADA network

When creating a SCADA network, the following mandatory datapoints are implicitly added.
(2)
(1)
FIGURE 116: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A SCADA NETWORK
− SCADA communication status SPS (1): this datapoint is put in “SET” state if
communication with the SCADA is operational.
“RESET” for communication with the SCADA not OK
“SET” for communication with the SCADA OK
− SCADA redundancy status SPS (2): this datapoint is put in “SET” state if
redundancy with the SCADA is active.
“RESET” for standby
“SET” for active
5. DEFINING DATAPOINT
5.1 Creating a datapoint
Electrical and system topologies share entities called datapoints. A datapoint corresponds to
an atomic object with real-time value, status or control relevant to electrical or system
process. Moreover, datapoints support extra system functions like forcing, suppression,
filtering, and alarms, logging.
Several kinds of datapoint exist:
• Input datapoints used for supervision:
− SPS (Single Point Status), DPS (Double Point Status), MPS (Multiple Point
Status)
− MV (Measurement Value), Counter
• Output datapoints used for control:
− SPC (Single Point Control), DPC (Double Point Control)

− Setpoint
Input datapoints can be acquired through sensors (input channels), addressed on IED at IED
legacy network level or substation network level. They can also be calculated or deduced by
the system devices. They can be sent to SCADA by addressing them on SCADA networks.
Output datapoints can be controlled through relays (output channels), addressed on IED at
IED legacy network level or substation network level or on SCADA networks. They can also
be managed by built-in functions or user functions.
At SCE level, datapoints belonging to the system topology are called system datapoints, and
those of the electrical topology are named electrical datapoints.
Generally, system datapoint creation is automatic when adding system devices or sub-
components to system devices. They are never wired, except for system datapoint used by
redundancy and more often correspond to system diagnostics (device, printer board status,
control of device mode,…).
Electrical datapoint creation is rarely automatic except when they are required for correct
PACiS system behaviour (for instance, ‘Order running SPS’ at bay level, ‘Computed
switchgear position’ at circuit-break level), or relevant to an electrical built-in function that
imposes their existence.
Be careful:
(Refer to section 4.6.1 Connecting computer to others station-bus sub-systems, for Client /
Server definition).
In the set of all the computers of a SCS, the previous described SPS attributes (except short
name and long name) are only useful and given to the computer that serves the datapoint
because the relevant functions are always done at computer server level.
5.1.1 Overview of binary input processing
Binary input processing is described in section 5.1 of chapter C264/EN FT
By extension, at SCE level:
• System inputs (SI) are seen as particular SPS, DPS or MPS depending on the number
of elementary information they represents (for details about SI, see section4.11
Setting system information for computer components).
• Group binary input is seen as particular SPS.

5.1.2 Defining a SPS datapoint

5.1.2.1 SPS processing
Processing of a SPS is described in section 5.1.2 of chapter C264/EN FT.
5.1.2.2 Creating a SPS datapoint
To create a SPS datapoint:
• Add a SPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of SPS exist. They are
used for specific needs at electrical topology level (for details see relevant section in 6
DEFINING COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE) or
system topology level (for details see section 4.11 Setting system information for
computer components).
• Update the SPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPS.
• Update its relation ‘has for profile’ to point to a specific existing profile (2). See section
5.2 Linking a datapoint to a profile, for details about profile definition and setting.
(1)
FIGURE 117: ADDING A SPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
(2)
FIGURE 118: LINKING A SPS DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
Updating SPS attributes (description for generic SPS)

When adding a generic SPS datapoint, some general attributes must be updated:
1. short name and long name of the datapoint used for logging, alarms ...
2. detection mode (Permanent / Transient / Permanent with computer auto-reset): when
this attribute is set to "Permanent with computer auto-reset" the SPS is reset
automatically after 1 ms.
3. stable state time reference (Start of filtering / End of filtering)
4. reset confirmation delay (range [0 s, 120 s], step 100 ms]: confirmation delay for
stable ‘reset’ state.
5. set confirmation delay (range [0 s, 120 s], step 100 ms]: confirmation delay for
stable ‘set’ state.
6. forcing management (Not automatic / Automatic to reset state / Automatic to set
state): when a SPS goes in invalid state, computer can force or not its status to set or
reset state automatically. This attribute defines the way this forcing management is
done. Automatic forcing management is independent of FSS facility gives at user by
the SPS profile.
7. state panel assignment (No / Yes): set to ‘yes’ to enable SPS state display at
computer local HMI level.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 119: SETTING GENERAL ATTRIBUTES OF A SPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
5.1.3 Defining a DPS datapoint

5.1.3.1 DPS processing
Processing of a DPS is described in section 5.1.3 of chapter C264/EN FT.
5.1.3.2 Creating a DPS datapoint
To create a DPS datapoint:
• Add a DPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of DPS exist. They are
• Update the DPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPS.
(1)
FIGURE 120: ADDING A DPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPS)
(2)
FIGURE 121: LINKING DPS DATAPOINT TO ITS PROFILE

Updating DPS attributes (description for generic DPS)

When adding a generic DPS datapoint, some general attributes must be updated:
2. stable state time reference ( Start motion / End motion): this attribute defines the
time reference for a stable state: at start of motion filtering or end of motion filtering
3. complementary delay jammed (range [0 s, 60 s), step 100 ms): this attribute defines
the delay for the MOTION00 (JAMMED) state filtering. It corresponds to parameter T00
mentioned in § 5.1.3.1 of chapter C264/EN FT
4. complementary delay undefined (range [0 s, 60 s), step 100 ms): this attribute
defines the delay for the MOTION11 (UNDEFINED) state filtering. It corresponds to
parameter T11 mentioned in § 5.1.3.1 of chapter C264/EN FT
5. open confirmation delay (range [0 s, 60 s), step 100 ms): this attribute defines the
confirmation delay for the OPEN state. It corresponds to parameter TO mentioned in §
5.1.3.2 of chapter C264/EN FT
6. closed confirmation delay (range [0 s, 60 s), step 100 ms): this attribute defines the
confirmation delay for the CLOSE state. It corresponds to parameter TC mentioned in
§ 5.1.3.2 of chapter C264/EN FT
7. forcing management (Not automatic / Automatic to reset state / Automatic to set
state): when a DPS is in an invalid state, the computer can force or not its status to set
or reset state automatically. This attribute defines the way this forcing management is
done. Automatic forcing management is independent of FSS facility given to the user
by the DPS profile.
8. state panel assignment (No / Yes): set to ‘yes’ to enable the display of the DPS state
at the computer local HMI level.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 122: SETTING GENERAL ATTRIBUTES OF A DPS DATAPOINT

5.1.4 Defining a MPS datapoint

5.1.4.1 MPS processing
Processing of a MPS is described in section 5.1.4 of chapter C264/EN FT.
5.1.4.2 Creating a MPS datapoint
To create a MPS datapoint:
• Add a MPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of MPS exist. They are
• Update the MPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of MPS.
(1)
FIGURE 123: ADDING A MPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
(2)
FIGURE 124: LINKING MPS DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
-Updating MPS attributes (description for generic MPS)

When adding a generic MPS datapoint, some general attributes must be updated:
2. filtering delay (range [0 s, 6553,5 s), step 10 ms).
3. inhibition delay (range [0 s, 6553,5 s), step 10 ms).
4. forcing management (Not automatic / Automatic to state (i ∈ [0, 15])): when a
MPS goes in invalid state, computer can force or not its status to set or reset state
automatically. This attribute defines the way this forcing management is done.
Automatic forcing management is independent of FSS facility gives at user by the
MPS profile.
5. state panel assignment (No / Yes): set to ‘yes’ to enable MPS state display at
(1)
(2)
(3)
(4)
(5)
FIGURE 125: SETTING GENERAL ATTRIBUTES OF A MPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
5.1.5 Overview of measurement processing

Processing of a measurement is described in section 5.2 of chapter C264/EN FT.
Features of digital measurements are described in section 4.6 of chapter C264/EN FT.
5.1.5.1 Analogue measurement acquisition
Analogue measurements are acquired via input analogue channel (AI) of AIU board. These
AI are voltage or current DC signals (only current for AIU210 board) delivered by
transducers, and representing an external value.
Input characteristics
The saturation value, for each range, is the following:
Range Saturation values

± 10 V -12.6 V / +12.6 V
±5V -6.3 V / +6.3 V
± 2.5 V -3.2 V / +3.2 V
± 1.25 V -1.26 V / +1.26 V
0 - 1 mA 1.26 mA
± 1 mA -1.26 mA / +1.26 mA
0 – 5 mA 6.3 mA
± 5 mA -6.3 mA / +6.3 mA
0 – 10 mA 12.5 mA
± 10 mA -12.5 mA / +12.5 mA
0 – 20 mA 25 mA
± 20 mA -25 mA / +25 mA
4-20 mA 26 mA
Acquisition
Acquisition cycle
The analogue inputs are acquired on a periodical basis. Each channel on a board can be
assigned one of these cycles independently of the others channels (see section 4.4.5
Configuring an AI channel).
There exists two acquisition cycles:
− a short cycle (Nsc x 100 ms, Nsc configurable from 1 to 10 with a default value of 1).
− a long cycle (Nlc x 500 ms, Nlc configurable from 1 to 20, with a default value of 2).
AD conversion
The Analogue to Digital Converter has a 16 bits resolution (15 bits + sign bit).
The zero offset value is computed by the conversion of a 0 V voltage reference.
The gain is adjusted automatically by software by connecting a known voltage reference to
the amplifier.
The zero offset values and the gain are adjusted regularly in order to compensate for the
deviations caused by variations of temperature and ageing.
Self-checks
Two two kinds of self-checks are performed:
• the board address coherency
• the complementarity control of the measured value

These self-checks are performed at each scan (defined during the configuration phase).
Time tagging
An AI is time stamped with the date/time of the scanned value.
5.1.5.2 Adding a MV datapoint
To create a MV datapoint:
• Add a MV from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of MV exist. They are
• Update the MV attributes (see following sections); some attributes can be fixed or
masked depending on the pre-defined kind of MV.
(1)
FIGURE 126: ADDING A MV DATAPOINT

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

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC MV)
5.1.5.3 Setting ‘General’ attributes of a MV datapoint

When adding a generic MV datapoint, some general attributes must be updated:
1. short name and long name: used for logging, alarms ...
2. type: available values are:
− Analogue (used for analogue acquisition, IED acquisition, CT/VT calculation or

system input)
− Digital coded ‘BCD’ (only used for digital acquisition)
− Digital coded ‘pure binary’ (only used for digital acquisition)
− Digital coded ‘gray’ (only used for digital acquisition)
− Digital coded ‘1 among n’ (only used for digital acquisition)
− Digital coded ‘decimal’ (only used for digital acquisition)
For details about digital encoding see section 4.6.3 of chapter C264/EN FT.
3. IDRC: not significant
4. automatic forcing (No / Yes): when a MV goes in invalid state, computer can force or
not its value automatically. Automatic forcing management is independent of FSS
facility gives at user by the MV profile.
5. value for automatic forcing: MV value when automatic forcing
6. transmission on event (Cyclic long period / Cyclic short period / According to a ‰ of
full scale value / According to a ‰ of current value)
7. deadband (‰ variation) (range [0,255], step 1): this attribute is significant only if the
previous parameter is set to ‘According to a ‰ of ...’: this attribute corresponds to ‘p’
parameter described in section 5.2.9.2 of chapter C264/EN FT.
8. MV panel assignment (No / Yes): set to ‘yes’ to enable MV value displayed at
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 128: SETTING GENERAL ATTRIBUTES OF A MV DATAPOINT

5.1.5.4 Setting ‘Value features’ attributes of a MV datapoint

When adding a generic MV datapoint, some ‘Value features’ attributes must be updated:
1. minimum value (range [-3.4e38, 3.4e38]: used for full scale calculation and scaling
2. maximum value (range [-3.4e38, 3.4e38]: used for full scale calculation and scaling.
(Full scale = maximum value - minimum value)
3. zero value suppression (% of full scale value) (range [0,10], step 0.1): this parameter
is used to define the zero suppression area for the zero value suppression processing
(refer to section 5.2.3 of chapter C264/EN FT for details)
4. Hysteresis used for threshold detection (see section 5.2.4 of chapter C264/EN FT for
details)
For each available threshold (see section 5.2.4 of chapter C264/EN FT for details):
5. Threshold usage (No / Yes)
6. Threshold value
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 129: SETTING VALUE FEATURES ATTRIBUTES TO MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
5.1.5.5 Setting ‘Scaling’ attributes of a MV datapoint
When adding a generic MV datapoint, some ‘Scaling’ attributes must be updated:
1. scaling rule: available values are (see section 5.2.2 of chapter C264/EN FT for
details):
− Linear
− Quadratic
− Quadratic with offset
− Linear per pieces
2. minimum acq. value (used for scaling)
3. maximum acq. value (used for scaling)
In case of multi-segment scaling:

4. Ai coefficient
5. Bi coefficient
(1)
(2)
(3)
(4)
(5)
FIGURE 130: SETTING SCALING ATTRIBUTES OF A MV DATAPOINT

5.1.6 Defining a TPI datapoint

5.1.6.1 Overview of Tap Position Indicator processing
Tap Position Indicator (TPI) is described section 5.3 of chapter C264/EN FT
Tap Position Indicator (TPI) must be seen as MV with specific features:
• Its value is an integer in the range [1..64],
• Acquisition can be done via AI channel of AIU board.
• Acquisition can be done on digital channels of DIU board (up to 64 DI channels). In

that case, available digital MV type are: Decimal, Gray, BCD or ‘1 among n’
5.1.6.2 Adding a TPI datapoint
TPI datapoint is automatically created when adding a tap changer built-in function under a
mandatory transformer module of a transformer bay. For details about transformer bay,
module or tap changer function creation see section 6 DEFINING COMPUTER
CONFIGURATION IN ELECTRICAL ARCHITECTURE.
Once a TPI has been created by adding a tap changer built-in function (1):
• Update the TPI attributes (see following sections).
• Update its relation ‘has for profile’ to point to a specific existing MV profile (2). See
section 5.2 Linking a datapoint to a profile, for details about profile definition and
setting.
Bay transformer
Mandatory transformer module
(1) Tap changer built-in function
Mandatory TPI
C0191ENb
FIGURE 131: AUTOMATIC TPI CREATION FOR TAP-CHANGER BUILT-IN FUNCTION
(2)
FIGURE 132: LINKING TPI DATAPOINT TO ITS PROFILE

5.1.6.3 Setting ‘General’ attributes of a TPI datapoint

For a TPI datapoint, some general attributes, similar to MV attributes, must be updated:
2. type: available values are:
− Analogue tap position

− Digital tap position coded ‘1 among N’ (only used for digital acquisition)
− Digital tap position coded ‘decimal’ (only used for digital acquisition)
− Digital tap position coded ‘gray’ (only used for digital acquisition)
− Digital tap position coded ‘BCD’ (only used for digital acquisition)
For details about digital encoding see section 4.6.3 of chapter C264/EN FT.
3. MV panel assignment (No / Yes): set to ‘yes’ to enable MV value display at computer
local HMI level.
(1)
(2)
(3)
FIGURE 133: SETTING GENERAL ATTRIBUTES OF A TPI DATAPOINT

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

("maximum value" − "minimum value" + 1) ∈ [1..64]
5.1.6.5 Setting ‘Tap position’ attributes of a TPI datapoint
For a TPI datapoint, some specific attributes must be updated:
1. Filtering delay (range [0 , 655,35 s], step 10 ms):
− for digital TPI, corresponds to Tstab of digital measurement

(Refer to section 4.6 of chapter C264/EN FT for attribute meaning)
− for analog TPI, corresponds to a delay to filter transient UNDEFINED state (delay
to confirm UNDEFINED state)
2. current valid range (% maximum value) (range [0 , 20 %], step 1 %): only used for
analogue TPI corresponds to N parameter described in section 5.3 of chapter
C264/EN FT.
(1)
(2)
FIGURE 134: SETTING TAP POSITION ATTRIBUTES OF A TPI DATAPOINT

5.1.6.6 Setting ‘Scaling’ attributes of a TPI datapoint
For an analogue TPI datapoint, some ‘Scaling’ attributes appears and must be updated:
1. minimum acq. value: corresponds to Imin parameter described in section 5.3.2 of
chapter C264/EN FT.
2. maximum acq. value: corresponds to Imax parameter described in section 5.3 of
chapter C264/EN FT.
(1)
(2)
FIGURE 135: SETTING SCALING ATTRIBUTES OF A TPI DATAPOINT

5.1.7 Defining a Counter datapoint

5.1.7.1 Overview of counter processing
Single counters and double counters are described in section §4.5 of chapter C264/EN FT.
Continuous register Scaling

From counters
acquisition
+
+1
Accumulator Transmission
= To RCP
To HMI
To archive
Periodic register Scaling To automation
in
24h - FIFO
C0195ENa
FIGURE 136: COUNTER PROCESSING
• The accumulator is incremented at each valid counter pulse.
• The periodic register is used to store the accumulator value of the previous period.
• The continuous register is used to store the accumulator value since the origin.
• The FIFO memory is used to store the periodic register of each period (up to 16
counters), during 24h.
Periodic processing
A period is defined either:
• By an external pulse on a digital input.
• By the internal clock : the period length is settable : 10', 15', 30', 1h to 24h , each
period begins at a regular hour: 12:00 , 12:30 , 13:00 ...
This choice is defined during the configuration phase on a per computer basis. The period
delimiter is also defined at configuration time for each counter.
At each period:
• The content of the accumulator is added to the continuous register.
• The content of the accumulator is transferred to the periodic register.
• The content of the periodic register is inserted into the FIFO queue.
• The accumulator is reset to 0 (a pending pulse is not lost ).
• Either the continuous register or the periodic register is transmitted. The choice is
made by configuration on a per accumulator basis.
If the chosen transmitted register reaches its maximum value (232), the counter status is set
to OVERRANGE. Only a counter modification can re-validate the counter.
Scaling
Scaling is used for printing or displaying a counter. EPI is a parameter giving the amount of
energy in KW-h or KVAR-h equivalent to a pulse. The displayed value is:
N x EPI KW-h
With N = the value of a counter.
Counter resulting states
The state of a counter can be:
State Comment
VALID not in one of the below states
SELFCHECK Due to the SELFCHECK FAULTY of the DI
FAULTY
UNKNOWN If the counter is acquired via a transmission link, the
information is unknown when the link is disconnected.
UNDEFINED Due to a counting failure of DCT (non-complementarity of
the 2 contacts)
OVERRANGE when the maximum value is reached
Transmission
The counters are transmitted on a client-server basis on the IEC-61850 network using the
report mechanism.
During a loss of communication between a client and a server, all server counters are set to
The counter informations transmitted in a report are:
• the number of pulses (i.e. accumulator value before scaling).
• the real value.
• the time stamping (in GMT time) and time quality.
• the resulting state (mapped on the quality field on IEC-61850).
• the reason for change, which could be one of the following values :
− cyclic change (set if the value has changed)

− change of quality (set if the quality has changed)
− change due to control (set if the value or quality change is due to a control)
Counter modification
When an accumulator value is modified, the request is immediately taken into account. The
continuous register is set with the accumulator value.
The modification could be a reset of the counter.
5.1.7.2 Adding a Counter datapoint
To create a Counter datapoint:
• Add a Counter from object entry available at the wished system or electrical object
level (1). Depending on the object level, different pre-defined kinds of counter exist.
They are used for specific needs at electrical topology level (for details see relevant
section in 6 DEFINING COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see section 4.11 Setting
system information for computer components).
• Update the Counter attributes (see following sections).

(1)
FIGURE 137: ADDING A COUNTER DATAPOINT

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

5.1.7.3 Setting ‘General’ attributes of a Counter datapoint
When adding a generic Counter datapoint, some general attributes must be updated:
2. counter type (Standard, Energy import, Energy export): when this attribute is set to
"Standard" associated attributes are Validation duration (3), Invalidity duration (4), IED
value already totalled (5), Cumul period (6) and Reset at cumulative period (7). When
this attribute is set to Energy import or Energy export associated attributes are energy
type (9), Scale factor (10), Transmission period (11) and reset after transmission (12).
3. validation duration (range [0, 10 s], step 1 ms): corresponds to Tcount parameter
described in section 4.5 of chapter C264/EN FT.
4. invalidity duration (range [5, 10 s], step 1 ms): corresponds to Tdef parameter
described in section 4.5 of chapter C264/EN FT.
5. IED value already totalled (No / Yes): attribute must be set to Yes if counter value
acquired on IED must not be totalled periodically (total done at IED level)
6. cumul period (10 mn / 15 mn / 30 mn / N h (N ∈ [1, 24])): corresponds to period

length of internal clock parameter described in section1.
7. reset at cumulative period (No / Yes): when set to ‘Yes’ that the way to transmit the
periodic register, if not the cumulative register is transmitted.
8. MV panel assignment (No / Yes): set to ‘yes’ to enable Counter value display at
9. scale factor.
10. energy type (Activ energy, Reactiv energy).
11. transmission period (10 mn / 15 mn / 30 mn / N h (N ∈ [1, 24])).

12. reset after transmission (No, Yes).
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
FIGURE 139: SETTING GENERAL ATTRIBUTES OF A COUNTER DATAPOINT

5.1.8 Overview of control sequence processing

This section is an introduction to SPC, DPC and SetPoint datapoint definition. It deals with
general control sequence and features associated to these kinds of datapoints, for better
comprehension of their configuration.
There are four types of Binary outputs:
• Single Point Status (SPC): derived from one Digital output.
• Double Point Status (DPC): derived from two Digital outputs.
• System output: control information related to the system, to configurable and built-in
automations or to electrical process but without acquisition possibilities.
• Setpoint (SetPoint): derived from n Digital outputs.

SPC, DPC and SetPoints are mainly controlled via digital output boards (DOU board) or via
IEDs connected by a serial link (for details see section 5.6).
By extension, at SCE level, system outputs are seen as particular SPC or DPC depending
on the number of elementary information they represent (for details about system outputs,
see section 4.11 Setting system information for computer components).
Control sequences are described in section 6 of chapter C264/EN FT (Functional
Description).
5.1.9 Defining a SPC datapoint
To create a SPC datapoint:
• Add a SPC from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of SPC exist. They are
• Update the SPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPC.
(1)
FIGURE 140: ADDING A SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPC)
(2)
FIGURE 141: LINKING A SPC DATAPOINT TO ITS PROFILE

5.1.9.1 Setting ‘General’ attributes of a SPC datapoint
When adding a generic SPC datapoint, some general attributes must be updated:
2. activation mode (Permanent / Transient / Permanent until feedback).
3. order on duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the contact is closed
before re-opening.
4. hold duration (range [0, 10 s], step 10ms): this attribute is only available if the
activation mode is set to Permanent until feedback. It defines the time while the
contact is held in the requested position after reception of the confirmation of the
position of the device.
5. time between two orders (range [0, 10 s], step 100ms): this attribute corresponds to
the inter-control delay defined in section 6.1.6.1 of chapter C264/EN FT and use also
used for execution checks (see section 6.1.8 of chapter C264/EN FT).
6. command panel assignment (No / Yes): set to ‘yes’ to enable SPC control at
(1)
(2)
(5)
(6)
(1)
(2)
(3)
(5)
(6)
(1)
(2)
(4)
(5)
(6)
FIGURE 142: SETTING GENERAL ATTRIBUTES OF A SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC SPC)
5.1.9.2 Setting ‘Dependencies’ attributes of a 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 section 6.1.6
of chapter C264/EN FT and use also for execution checks (see section 6.1.8 of
chapter C264/EN FT), if SPC datapoint is located under a bay.
• substation mode control and substation uniqueness control, if SPC level is higher than
bay level.
Substation/Bay control uniqueness is globally set at substation level (see section 6.1.2
Defining a Substation). When substation uniqueness is set, bay uniqueness is implicitly set
for all bays.
Dependencies for SPC level lower than or equal to bay level

1. Substation mode dependency (No / Yes).
2. bay mode dependency (No / Yes).
3. SBMC mode dependency (No / Yes).
4. bay control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to bay at substation level.
(1)
(2)
(3)
(4)
FIGURE 143: SETTING DEPENDENCIES ATTRIBUTES OF A SPC DATAPOINT

Dependencies for SPC level higher than bay level
1. Substation mode dependency (No / Yes)
2. Substation control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to substation at substation level.
(1)
(2)
FIGURE 144: SETTING DEPENDENCIES ATTRIBUTES OF A SPC DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC SPC)
5.1.9.3 Defining a 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 a SPC feedback:
− Add the relation ‘has for feedback’ at SPC level: choose exclusively one of the two
relations ‘has for feedback: SPS datapoint’ (1) or ‘has for feedback: DPS datapoint’ (2)
depending on the kind of feedback datapoint.
− Fill the relation with the relevant SPS or DPS datapoint.
− If necessary update the relation attributes:

(1)
(2)
FIGURE 145: DEFINING SPC FEEDBACK

3. execution time-out (range [0, 6000 s], step 100 ms): in this given delay, feedback
must change relatively to the control. If not, a negative acknowledgement is sent for
the control (for details see section 5.1.8 Overview of control sequence processing).
4. status check for command (No check / Control authorized only if the device is in the
opposite state / Control authorized only if the device is in the opposite state, jammed
or undefined / Control refused if the device is in the same state) : this attribute
corresponds to the ‘current status check for the device’ described in section 6.1.6.8 of
chapter C264/EN FT and used also for execution checks (see section 6.1.8 of chapter
C264/EN FT).
(3)
(4)
FIGURE 146: SETTING ATTRIBUTES OF A SPC FEEDBACK RELATION

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

To create a DPC datapoint:
• Add a DPC from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of DPC exist. They are
• Update the DPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPC.
5.2.7, for details about profile definition and setting.
(1)
FIGURE 147: ADDING A DPC DATAPOINT

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

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

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC DPC)
5.1.10.2 Setting ‘Dependencies’ attributes of a 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 section
6.1.6 of chapter C264/EN FT) and also used for execution checks if DPC datapoint is
located under a bay.
• substation mode control and substation uniqueness control, if DPC level is higher than
bay level.
for all bays.
Dependencies for DPC level lower than or equal to bay level
(1)
(2)
(3)
(4)
FIGURE 150: SETTING DEPENDENCIES ATTRIBUTES OF A DPC DATAPOINT

Dependencies for DPC level higher than bay level
1. substation mode dependency (No / Yes).
2. substation control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to substation at substation level.
(1)
(2)
FIGURE 151: SETTING DEPENDENCIES ATTRIBUTES OF A DPC DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC DPC)
5.1.10.3 Defining a DPC feedback

For correct execution behaviour and control acknowledgement, a DPC datapoint can be
linked to a SPS or DPS datapoint that corresponds to a feedback. For instance a circuit-
breaker control DPC is linked to the circuit-breaker status DPS.
To define a DPC feedback:
• Add the relation ‘has for feedback’ at DPC level: choose exclusively one of the two
relations ‘has for feedback: SPS datapoint’ (1) or ‘has for feedback: DPS datapoint’ (2)
depending on the kind of feedback datapoint.
• Fill the relation with the relevant SPS or DPS datapoint.
• If necessary update the relation attributes:

3. execution timeout (range [0, 6000 s] step 100 ms): in this given delay, feedback
must change relatively to the control. If not, a negative acknowledgement is sent for
the control (for details see section 5.1.8 Overview of control sequence processing).
4. status check for command (No check / Control authorized only if the device is in the
opposite state / Control authorized only if the device is in the opposite state, jemmed
or undefined / Control refused if the device is in the same state) : this attribute
corresponds to the ‘current status check for the device’ described in section 6.1.6.8 of
chapter C264/EN FT and also used for execution checks (see section 6.1.8 of chapter
C264/EN FT).
(1)
(2)
FIGURE 152: DEFINING A DPC FEEDBACK
(3)
(4)
FIGURE 153: SETTING ATTRIBUTES OF A DPC FEEDBACK RELATION

• For each "DPC", two relations "has for feedback" are available, but they are mutually
exclusive
• For a "DPC" datapoint, if its attribute "activation mode" is set to the "Transient" value,
then the following rule must be respected:"execution timeout"> max ["open duration" ,
"close duration" ]
5.1.11 Defining a SetPoint datapoint
5.1.11.1 Overview of SetPoint processing
Digital setpoints are described in section 4.9 of chapter C264/EN FT.
SetPoints are used to send instruction values to the process or to ancillary devices. MiCOM
Computers manage 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.
• Uniqueness : check user selectable.
• Device Locked : check user selectable.
• Automatism running control: check user selectable.

Digital SetPoints may be configured with digital “refresh DO” (see following topic)
The configuration allows also to define two methods of activation of the SetPoint relays:
• Raw activation: all activated relays which must be open are deactivated, all relays
which must be closed are activated. If a “read inhibit DO” is configured this one must
be deactivated during the relay positioning (see following topic).
• Incremental activation: the restitution of the SetPoint and relays can be done by
successive increments from the initial value to the final one. The value of increments
and the duration of the activation are user selectable. If a “read inhibit DO” is
configured this one must be deactivated during every incremental activation (see
following topic).
Digital SetPoint encoding
Described in section 4.9.1 of chapter C264/EN FT.
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.
Value
RI
C0210ENa
FIGURE 154 : READ INHIBIT SIGNAL FOR DIGITAL SETPOINT

Refresh DO for digital SetPoint
SetPoints can be configured with a refresh period, this means that the SetPoint request must
be sent periodically by the transmitter.
If a request on the SetPoint is not received before the end of the refresh period, the SetPoint
is set to non-refreshed and an alarm is raised but and the last received SetPoint is
maintained.
Once a new SetPoint request is received, the SetPoint is set to refreshed, DO are activated
and the alarm is reset.
SetPoints to IEDs
SetPoints controls towards IEDs are managed in “Direct execute mode”. Execution phase is
identical to the digital SetPoints. The execution is performed via the communication protocol
of the concerned IED.
System SetPoint
SetPoints can be locally managed by computer as a system control for automation for
instance. Execution phase is identical to the digital SetPoints.
5.1.11.2 Adding a SetPoint datapoint

To create a SetPoint datapoint:
• Add a SetPoint from object entry available at the wished system or electrical object
level (1). Depending on the object level, different pre-defined kinds of SetPoint exist.
They are used for specific needs at electrical topology level (for details see relevant
section in 6 DEFINING COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see section 4.11 Setting
system information for computer components).
• Update the SetPoint attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SetPoint.
5.2.8 Defining a SetPoint profile, for details about profile definition and setting.
(1)
FIGURE 155: ADDING A SETPOINT DATAPOINT

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

5.1.11.3 Setting ‘General’ attributes of a SetPoint datapoint
When adding a generic SetPoint datapoint, some general attributes must be updated:
2. type:
− Analogue: SetPoint is managed by IED or is a system output

− Digital coded BCD
− Digital coded ‘Pure binary’
− Digital coded ‘Gray’

− Digital coded ‘1 among N’
− Digital coded ‘decimal’
For details refer to section 4.9.1 of chapter C264/EN FT.
3. progressive step usage: only used for digital SetPoint. No corresponds to Raw
activation, Yes to Incremental Activation, described in section Defining a SetPoint
datapoint.
4. minimum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
5. maximum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
6. command panel assignment (Yes / No): set to ‘yes’ to enable SetPoint control at
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 157: SETTING GENERAL ATTRIBUTES OF A SETPOINT DATAPOINT

• A Setpoint datapoint wired on DO channels of a computer, must be digital and have its
profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute with SBO
popup”.
5.1.11.4 Setting ‘Dependencies’ attributes of a 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 section 6.1.6
of chapter C264/EN FT and use also for execution checks (see section 6.1.8 of
chapter C264/EN FT), if a Setpoint datapoint is located under a bay.
• substation mode control and substation uniqueness control, if SetPoint level is higher
than bay level.
for all bays.
Dependencies for SetPoint level lower than or equal to bay level

(1)
(2)
(3)
(4)
FIGURE 158: SETTING DEPENDENCIES ATTRIBUTES OF A SETPOINT DATAPOINT

Dependencies for SetPoint level higher than bay level
1. substation mode dependency (No / Yes)
2. substation control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to substation at substation level
(1)
(2)
FIGURE 159: SETTING DEPENDENCIES ATTRIBUTES OF A SETPOINT DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC SETPOINT)
5.1.11.5 Defining a 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:

2. execution timeout (range [0, 999 s], step 1 s): in this given delay, feedback must
change relatively to the control. If not, a negative acknowledgement is sent for the
control (for details see section 5.1.8 Overview of control sequence processing).
(1)
FIGURE 160: DEFINING SETPOINT FEEDBACK
(2)
FIGURE 161: SETTING ATTRIBUTES OF A SETPOINT FEEDBACK RELATION

5.2 Linking a datapoint to a profile

Many common characteristics are often shared by a set of datapoints. For instance, all
feeder breaker positions have got the same state labels, alarm and logging behaviour. To
group these common characteristics, profile concept has been embedded in data modelling.
For each kind of datapoints (SPS, DPS,…) there exists a relevant profile (SPSProfile,
DPSProfile, …). Several datapoints of the same kind are link-able to the same profile.
Be careful:
The profile attributes can be seen as the datapoint attributes as soon as this datapoint is
linked to the profile. For ease of explanation, this short-cut will be done in this document.
For input datapoints, the following characteristics are set at profile level:
• state labels and eventual unit label for MV and counter.
• definition of the archived and logged states.
• definition of the alarmed states (gravity, delay, audibility).
• definition of state interlocking values.
• definition of forcing/substitution/suppression (FSS) and SBMC facilities.
• links to printers defined in the system topology for alarm and event logging purpose.
For output datapoints, the following characteristics are set at profile level:
• order labels and eventual unit label for setpoints.
• definition of the significant orders for SPC and DPC.
• definition of the alarmed order failure (gravity, delay, audibility).
• definition of the archived and logged transitions.
• SBO mode facility.
• links to printers defined in the system topology for alarm and event logging purpose.
‘Profile’ objects can be put at any level of the system topology but never in the electrical
topology: they concern only system characteristics. For details about the system topology,
see section 4 DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE.
A profile object can be added at the following levels of the system topology:
• SCS.
• Ethernet network.
• Any instance of computer.
• Any instance of computer board.
• Any computer printer.
• Any SCADA network managed by a computer.
• Any IED managed by a computer.

When configuring a computer, the best practice is to group all profiles relevant to its system
datapoints at computer level or eventually its sub-components. Upper levels (Ethernet
network or SCS) can be used to define profiles if sharing datapoint profile between several
computers is wished.
For electrical datapoints, different approaches can be done:
• Grouping datapoint profiles at computer level per bay basis it manages.
• Grouping datapoint profiles at SCS level by kind of bays/modules managed by the

system.
• Mixing the two previous approaches, particularly for profiles relevant to datapoints
whose level is upper than bay or belonging to same kind of bays fed by several bay
computers.
Be careful:
(Refer to section 4.6.1 Connecting computer to others station-bus sub-systems, for Client /
Server definition)
In the set of all the computers of a SCS:
• the following profile functional characteristics logging, alarm, archiving and FSS, are
only useful and given to the computer that serves the linked datapoints because these
functions are always done at computer server level. So, a computer A using a
datapoint acquired on a computer B will never log, alarm or archive events relevant to
this datapoint.
• the following profile functional characteristics ‘state interlocking values’ are given to
server and client computers using a datapoint, because interlock evaluation is a
distributed function done on every computer that needs it before controlling its own
electrical modules.
• the following profile functional characteristics ‘SBMC facilities’ are given to server or
client computers using a datapoint exchanged on a SCADA network they manage,
because SBMC filtering is a distributed function done on computers managing SCADA
networks.
• the following profile characteristics ‘state/order labels’ are given to server or client
computers using a datapoint but are only used by the server: computer bay mimics,
logging, alarm definitions are reduced to datapoints that the computer is server of.
5.2.1 Defining 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 sections).
• Define if necessary on which printers event logging of linked SPS datapoint is done,
via adding and filling the relation ‘has events logged on’ at profile level (2).
• Define if necessary on which printers alarm event logging of linked SPS datapoint is
done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).
(1)
FIGURE 162: ADDING A SPS PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
(2)
FIGURE 163: DEFINING EVENT LOGGING PRINTER FOR SPS PROFILE
(3)
FIGURE 164: DEFINING ALARM LOGGING PRINTER FOR SPS PROFILE

5.2.1.2 Setting ‘General’ attributes of a SPS Profile

When adding a SPS profile some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE.
And for linked SPS datapoints:
2. enable Force/Subst/Sup (No / Yes).
3. SBMC dependant (No / Yes).
4. SBMC state substitution value (Suppressed / Set / Reset): significant and visible if
SBMC dependant is set to Yes.
5. toggling filtering (No / Yes): useful for a datapoint acquired on a DI board to filter
toggling.
6. initial status (Reset / Set): used for computer software initialisation especially for
system datapoints.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 165: SETTING GENERAL ATTRIBUTES OF A SPS PROFILE

• The profile of a datapoint of the System topology must have its enable
Force/Subst/Sup attribute set to No.
5.2.1.3 Setting ‘State labels’ attributes of a SPS Profile
When adding a SPS profile, some State labels attributes must be updated (1). They are
used for events and alarm management at computer level (logging, display).
(1)
FIGURE 166: SETTING ‘STATE LABELS’ ATTRIBUTES OF A SPS PROFILE

5.2.1.4 Setting ‘State treatment’ attributes of a SPS Profile

When adding a SPS profile, some State treatment attributes must be updated, for each
available state of the linked datapoints (1).
Available attribute values are:
• OI & C264: no archive, no logging:

• OI & C264: archive, logging:
• OI & C264: archive, no logging:
• only C264: no archive, logging:
• only C264: archive, logging:
• only C264: archive, no logging:
• only OI: archive, logging:
• only OI: archive, no logging:
For computer configuration, a more synthetic vision of logging and archiving is deduced from
these attributes: for details refer to sections 5.3 Defining computer local archiving of
datapoint events and 5.5 Defining computer local logging of datapoint events and alarms.
(1)
FIGURE 167: SETTING ‘STATE TREATMENTS’ ATTRIBUTES OF A SPS PROFILE

5.2.1.5 Setting ‘Alarms’ attributes of a SPS Profile
When adding a SPS profile some Alarms attributes must be updated, for each available
state of the linked datapoints.
1. generation condition (Appearance / Appearance and disappearance): this attribute is
common for all the states of each SPS linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable:
2. defined (No / Yes).
3. masking due to control (No / Yes): this attribute must be set to ‘Yes’ to manage
correctly discrepancy (alarm only appears in case of spontaneous change of state
without previous control).
4. delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay.
5. gravity (range [1, 5], step 1).
6. audible (No / Yes): to activate a klaxon.
7. clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
− Manual: users must explicitly clear the alarm ,

− Automatic: no user intervention is needed to clear the alarm,
− Gravity basis: the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For ‘Set’ and ‘Reset’ state, extra attribute spurious is settable ((8) and (9)). This information
is only significant when the user wants to alarm a spurious SPS datapoint on a particular
event Set or Reset. In fact, the datapoint has got no state, but generates an event. It is
useful to alarm trip information of relays for instance. When setting a spurious alarm, only the
relative state must be defined as alarmed; the other states must be set to ‘not defined alarm’.
For computer configuration, all attributes are significant for datapoints it is server of.
(1)
(2)
(8)
(3)
(4)
(5)
(6)
(7)
(9)
FIGURE 168: SETTING ‘ALARMS’ ATTRIBUTES OF A SPS PROFILE

5.2.1.6 Setting ‘Interlocking’ attributes of a SPS Profile

For each possible state of a SPS linked to this profile and belonging to an interlocking
equation the user chooses among three values (Invalid, False, True) which one will be used
for evaluation of the interlocking equation.
FIGURE 169: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A SPS PROFILE

5.2.2 Defining a DPS profile
5.2.2.1 Adding a DPS Profile
To create a DPS profile:
• Add a DPS profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked DPS datapoint is done,
• Defines if necessary on which printers alarm event logging of linked DPS datapoint is
(3).
(1)
FIGURE 170: ADDING A DPS PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)

(2)
FIGURE 171: DEFINING EVENT LOGGING PRINTER FOR DPS PROFILE
(3)
FIGURE 172: DEFINING ALARM LOGGING PRINTER FOR DPS PROFILE

5.2.2.2 Setting ‘General’ attributes of a DPS Profile
When adding a DPS profile, some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE.
And for linked DPS datapoints:
4. SBMC state substitution value (Suppressed / Open / Closed / Jammed), significant
and visible if SBMC dependant is set to Yes.
5. toggling filtering (No / Yes): useful for datapoint acquired on DI board to filter
toggling.
6. initial status (Motion / Open / Closed / Undefined), used for computer software
initialisation especially for system datapoints.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 173: SETTING GENERAL ATTRIBUTES OF A DPS PROFILE

5.2.2.3 Setting ‘State labels’ attributes of a DPS Profile
When adding a DPS profile, some State labels attributes must be updated (1). They are
(1)
FIGURE 174: SETTING ‘STATE LABELS’ ATTRIBUTES OF A DPS PROFILE

5.2.2.4 Setting ‘State treatment’ attributes of a DPS Profile
When adding a DPS profile, some State treatment attributes must be updated, for each

(1)
FIGURE 175: SETTING ‘STATE TREATMENT’ ATTRIBUTES OF A DPS PROFILE

5.2.2.5 Setting ‘Alarms’ attributes of a DPS Profile
When adding a DPS profile some Alarms attributes must be updated, for each available
For each state, following alarm information are settable:
common for all the states of each DPS linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable:
2. defined (No / Yes)
without previous control)
disappears within this delay
6. audible (No / Yes): to activate a klaxon
− Manual: users must explicitly clear the alarm.

− Automatic: no user intervention is needed to clear the alarm.
level for the relevant gravity.
For ‘Open’ and ‘Closed’ states, extra attribute spurious is settable ((8) and (9)). This
information is only significant when the user wants to alarm a spurious DPS datapoint on a
particular event Open or Closed. In fact, the datapoint has got no state, but generates an
event. It is useful to alarm trip information of relays for instance. When setting a spurious
alarm, only the relative state must be defined as alarmed; the other states must be set to ‘not
defined alarm’.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 176: SETTING ‘ALARMS’ ATTRIBUTES OF A DPS PROFILE

5.2.2.6 Setting ‘Interlocking’ attributes of a DPS Profile

For each possible state of a DPS linked to this profile and belonging to an interlocking
FIGURE 177: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A DPS PROFILE

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).
• Defines if necessary on which printers event logging of linked MPS datapoint is done,
• Defines if necessary on which printers alarm event logging of linked MPS datapoint is
(3).
(1)
FIGURE 178: ADDING A MPS PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)

(2)
FIGURE 179: DEFINING EVENT LOGGING PRINTER FOR MPS PROFILE
(3)
FIGURE 180: DEFINING ALARM LOGGING PRINTER FOR A MPS PROFILE

5.2.3.2 Setting ‘General’ attributes of a MPS Profile

When adding a MPS profile, some general attributes must be updated:
1. short name and long name: only used for profile identification in SCE.
And for linked MPS datapoints:
2. enable Force/Subst/Sup (No / Yes)
4. SBMC state substitution value (Suppressed / Open / Closed / Jammed): significant
and visible if SBMC dependant is set to Yes.
(1)
(2)
(3)
(4)
FIGURE 181: SETTING GENERAL ATTRIBUTES OF A MPS PROFILE

5.2.3.3 Setting ‘State labels’ attributes of a MPS Profile
When adding a MPS profile, some State labels attributes must be updated (1). They are
(1)
FIGURE 182: SETTING ‘STATE LABELS’ ATTRIBUTES OF A MPS PROFILE

5.2.3.4 Setting ‘State treatment’ attributes of a MPS Profile

When adding a MPS profile, some State treatment attributes must be updated, for each

(1)
FIGURE 183: SETTING ‘STATE TREATMENT’ ATTRIBUTES OF A MPS PROFILE

5.2.3.5 Setting ‘Alarms’ attributes of a MPS Profile

When adding a MPS profile some Alarms attributes must be updated, for each available
state of the linked datapoints.:
common for all the states of each MPS linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable
without previous control).
6. audible (No / Yes): to activate a klaxon.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 184: SETTING ‘ALARMS‘ ATTRIBUTES OF A MPS PROFILE

5.2.3.6 Setting ‘Interlocking’ attributes of a MPS Profile

For each possible state of a MPS linked to this profile and belonging to an interlocking
FIGURE 185: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A MPS PROFILE

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).
• Defines if necessary on which printers event logging of linked MV datapoint is done,

• Defines if necessary on which printers alarm event logging of linked MV datapoint is

(3).
(1)
FIGURE 186: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A MPS PROFILE
(2)
FIGURE 187: DEFINING EVENT LOGGING PRINTER FOR MV PROFILE

(3)
FIGURE 188: DEFINING ALARM LOGGING PRINTER FOR MV PROFILE

5.2.4.2 Setting ‘General’ attributes of a MV Profile
When adding a MV profile, some general attributes must be updated:
1. short name and long name: only used for profile identification in SCE.
And for linked MV datapoints:
3. SBMC dependant (Yes to suppressed / No).
4. unit :used for display, logging and alarm at computer level.
5. default format: Reserved for Substation control point usage.
(1)
(2)
(3)
(4)
(5)
FIGURE 189: SETTING GENERAL ATTRIBUTES OF A MV PROFILE

5.2.4.3 Setting ‘State labels’ attributes of a MV Profile

When adding a MV profile, some State labels attributes must be updated (1). They are used
for events and alarm management at computer level (logging, display).
(1)
FIGURE 190: SETTING ‘STATE LABELS’ ATTRIBUTES OF A MV PROFILE

5.2.4.4 Setting ‘State treatment’ attributes of a MV Profile
When adding a MV profile, some State treatment attributes must be updated, for each

(1)
FIGURE 191: SETTING ‘STATE TREATMENTS’ ATTRIBUTES OF A MV PROFILE

5.2.4.5 Setting ‘Alarms’ attributes of a MV Profile
When adding a MV profile some Alarms attributes must be updated, for each available state
of the linked datapoints.
For each state, following alarm information are settable:
common for all the states of each MV linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable
5. audible (No / Yes): to activate a klaxon
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 192: SETTING ‘ALARMS’ ATTRIBUTES OF A MV PROFILE

5.2.4.6 Setting ‘Interlocking’ attributes of a MV Profile
For each possible state of a MV linked to this profile and belonging to an interlocking
(1)
FIGURE 193: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A MV PROFILE

5.2.4.7 Setting ‘Mean value’ attributes of a MV Profile

When adding a MV profile, some ‘Mean value’ attributes must be updated. They are
reserved for substation control point usage.
1. computation (No / Yes)
2. reference hour (range [0, 23], step 1)
3. reference day (range [0, 31], step 1)
(1)
FIGURE 194: SETTING ‘MEAN VALUE’ ATTRIBUTES OF A MV PROFILE

5.2.5 Defining a Counter profile

5.2.5.1 Adding a Counter Profile
To create a Counter profile:
• Add a Counter profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked Counter datapoint is

done, via adding and filling the relation ‘has events logged on’ at profile level (2).
• Defines if necessary on which printers alarm event logging of linked Counter datapoint
is done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).
(1)
FIGURE 195: ADDING A COUNTER PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
(2)
FIGURE 196: DEFINING EVENT LOGGING PRINTER FOR COUNTER PROFILE
(3)
FIGURE 197: DEFINING ALARM LOGGING PRINTER FOR COUNTER PROFILE

5.2.5.2 Setting ‘General’ attributes of a Counter Profile

When adding a Counter profile, some general attributes must be updated:
1. short name and long name : only used for profile identification in SCE.
And for linked Counter datapoints:
2. SBMC dependant (Yes to suppressed / No).
3. energy equivalent to a pulse (range [-3.4E38, +3.4E38].
4. unit used for display, logging and alarm at computer level.
5. default format: Reserved for Substation control point usage.
(1)
(2)
(3)
(4)
(5)
FIGURE 198: SETTING GENERAL ATTRIBUTES OF A COUNTER PROFILE

5.2.5.3 Setting ‘State labels’ attributes of a Counter Profile
When adding a Counter profile, some ‘State labels’ attributes must be updated (1). They are
(1)
FIGURE 199: SETTING ‘STATE LABELS’ ATTRIBUTES OF A COUNTER PROFILE

5.2.5.4 Setting ‘State treatment’ attributes of a Counter Profile
When adding a Counter profile, some ‘State treatment’ attributes must be updated, for each


(1)
FIGURE 200: SETTING ‘STATE TREATMENT’ ATTRIBUTES OF A COUNTER PROFILE

5.2.5.5 Setting ‘Alarms’ attributes of a Counter Profile
When adding a Counter profile, some ‘Alarms’ attributes must be updated, for each available
Globally to all Counter states, the attribute ‘generate condition’ (1) defines when alarms are
generated for the datapoint: ‘appearance of the event’ or ‘appearance and disappearance of
the event’.
For each state (Valid, SelfCheckFault, Unknown, Forced, Overrange, Undefined) the
following alarm attributes are settable:
5. audible (No / Yes), to activate a klaxon.

(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 201: SETTING ‘ALARMS’ ATTRIBUTES OF A COUNTER PROFILE

5.2.5.6 Setting ‘Mean value’ attributes of a Counter Profile
When adding a Counter profile, some ‘Mean value’ attributes must be updated (1). They are
reserved for substation control point usage.
(1)
FIGURE 202: SETTING ‘MEAN VALUE’ ATTRIBUTES OF A 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).
• Define if necessary on which printers event logging of linked SPC datapoint is done,
• Define if necessary on which printers alarm event logging of linked SPC datapoint is
(3).
(1)
FIGURE 203: ADDING A SPC PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
(2)
FIGURE 204: DEFINING EVENT LOGGING PRINTER FOR SPC PROFILE
(3)
FIGURE 205: DEFINING ALARM LOGGING PRINTER FOR SPC PROFILE

5.2.6.2 Setting ‘General’ attributes of a SPC Profile

When adding a SPC profile, some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE
And for linked SPC datapoints:
2. SBO mode (for details see section 6.1.2 of chapter C264/EN FT)
Available values are:
− Direct execute
− SBO operate once
− SBO operate many
− Direct execute with SBO control box (reserved to substation control point
usage), similar to ‘Direct execute’ for computer
3. SBO timeout (range [0, 600 s], step 1s), significant if SBO mode is set to ‘SBO
operate once’ or ‘SBO operate many’.
(1)
(2)
(3)
FIGURE 206: SETTING GENERAL ATTRIBUTES OF A SPC PROFILE

5.2.6.3 Setting ‘Order labels’ attributes of a SPC Profile
When adding a SPC profile, some ‘Order labels’ attributes must be updated. They are used
for events and alarm management at computer level (logging, display) and for correct SPC
order management:
1. ‘Order off’ usage (No / Yes)
2. ‘Order on’ usage (No / Yes)
3. ‘Order off’ label
4. ‘Order on’ label
(1)
(2)
(3)
(4)
FIGURE 207: SETTING ‘ORDER LABELS’ ATTRIBUTES OF A SPC PROFILE

5.2.6.4 Setting ‘State treatment’ attribute of a 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).

this attribute: for details refer to sections 5.3 Defining computer local archiving of datapoint
events and 5.5 Defining computer local logging of datapoint events and alarms.
(1)
FIGURE 208: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF A SPC PROFILE

5.2.6.5 Setting ‘Alarms’ attributes of a 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:
3. gravity (range [1, 5], step 1)
4. audible (No / Yes), to activate a klaxon

(1)
(2)
(3)
(4)
(5)
FIGURE 209: SETTING ‘ALARMS’ ATTRIBUTES OF A SPC PROFILE

5.2.6.6 Setting ‘Interlocking and FBD’ attributes of a 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 sections 6.6.1 Defining a FBD fast automation
and 6.6.6 Defining interlocking):
The following attributes are settable:
1. ‘On order’ interlock value (Invalid / False / True): this attribute defines the value
affected to the On order state of the SPC for evaluation of an interlock equation or a
FBD using this SPC.
2. ‘Off order’ interlock value (Invalid / False / True): this attribute defines the value
affected to the Off order state of the SPC for evaluation of an interlock equation or a
FBD using this SPC.
(1)
(2)
FIGURE 210: SETTING ‘INTERLOCKING AND FBD’ ATTRIBUTES OF A SPC PROFILE

5.2.7 Defining a DPC profile

5.2.7.1 Adding a DPC Profile
To create a DPC profile:
• Add a DPC profile from object entry available at the wished system object level (1).
• Define if necessary on which printers event logging of linked DPC datapoint is done,
• Define if necessary on which printers alarm event logging of linked DPC datapoint is
(3).
(1)
FIGURE 211: ADDING A DPC PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
(2)
FIGURE 212: DEFINING EVENT LOGGING PRINTER FOR DPC PROFILE

(3)
FIGURE 213: DEFINING ALARM LOGGING PRINTER FOR DPC PROFILE

5.2.7.2 Setting ‘General’ attributes of a DPC Profile
When adding a DPC profile, some general attributes must be updated:
1. short name and long name: only used for profile identification in SCE
And for linked DPC datapoints:
2. SBO mode
− Direct execute
− SBO operate once
− SBO operate many
usage), similar to ‘Direct execute’ for computer
(1)
(2)
(3)
FIGURE 214: SETTING GENERAL ATTRIBUTES OF A DPC PROFILE

5.2.7.3 Setting ‘Order labels’ attributes of a DPC Profile

‘Order labels’ attributes of a DPC profile are used for events and alarm management at
computer level (logging, display) and for correct SPC order management:
1. ‘Order open’ (set to 01) usage (No / Yes)
2. ‘Order close’ (set to 10) usage (No / Yes)
3. ‘Order open’ (set to 01) label
4. ‘Order close’ (set to 10) label
(1)
(2)
(3)
(4)
FIGURE 215: SETTING ‘ORDER LABELS’ ATTRIBUTES OF A DPC PROFILE

5.2.7.4 Setting ‘State treatment’ attribute of a DPC Profile
When adding a DPC profile the treatment on event attribute must be updated globally for all
available control and acknowledgement steps of the linked datapoints (1).

(1)
FIGURE 216: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF A DPC PROFILE

5.2.7.5 Setting ‘Alarms’ attributes of a DPC Profile

When adding a DPC profile, some ‘Alarms’ attributes must be updated, for the correct alarm
management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm informations are settable:
(1)
(2)
(3)
(4)
(5)
FIGURE 217: SETTING ‘ALARMS’ ATTRIBUTES OF A DPC PROFILE

5.2.7.6 Setting ‘Interlocking and FBD’ attributes of a DPC Profile
When adding a DPC profile, some ‘Interlocking and FBD’ attributes can be updated for
boolean evaluation of interlocking equation, if the SPC belongs to an interlock equation or if
the DPC is an input of FBD automation (see sections 6.6.1 Defining a FBD fast automation
and 6.6.6 Defining interlocking):
The following attributes are settable:
1. ‘Open order’ interlock value (Invalid / False / True): this attribute defines the value
affected to the Open order state of the DPC for evaluation of an interlock equation or a
FBD using this DPC
2. ‘Close order’ interlock value (Invalid / False / True): this attribute defines the value
affected to the Close order state of the DPC for evaluation of an interlock equation or
a FBD using this DPC
(1)
(2)
FIGURE 218: SETTING ‘INTERLOCKING AND FBD’ ATTRIBUTES OF A DPC PROFILE

5.2.8 Defining a SetPoint profile
5.2.8.1 Adding a SetPoint Profile
To create a SetPoint profile:
• Add a SetPoint profile from object entry available at the wished system object level
(1).
• Define if necessary on which printers event logging of linked SetPoint datapoint is

done, via adding and filling the relation ‘has events logged on’ at profile level (2).
• Define if necessary on which printers alarm event logging of linked SetPoint datapoint
is done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).
(1)
FIGURE 219: ADDING A SETPOINT PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)

(2)
FIGURE 220: DEFINING EVENT LOGGING PRINTER FOR SETPOINT PROFILE
(3)
FIGURE 221: DEFINING ALARM LOGGING PRINTER FOR SETPOINT PROFILE

5.2.8.2 Setting ‘General’ attributes of a SetPoint Profile
When adding a SetPoint profile, some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE
And for linked SetPoint datapoints:
2. SBO mode: available values are:
− Direct execute
− SBO operate once, reserved for future use
− SBO operate many, reserved for future use
usage), similar to ‘Direct execute’ for computer, reserved for future use
4. unit used for display, logging and alarm at computer level.
(1)
(2)
(3)
(4)
FIGURE 222: SETTING GENERAL ATTRIBUTES OF A SETPOINT PROFILE

5.2.8.3 Setting ‘treatment on event’ attribute of a SetPoint Profile
When adding a SetPoint profile, the ‘treatment on event’ attribute must be updated globally
for all available control and acknowledgement steps of the linked datapoints (1).
The available values for this attribute are:

(1)
FIGURE 223: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF A SETPOINT PROFILE

5.2.8.4 Setting ‘Alarms’ attributes of SetPoint Profile

When adding a SetPoint profile, some ‘Alarms’ attributes must be updated, for the correct
alarm management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm informations are settable:
(1)
(2)
(3)
(4)
(5)
FIGURE 224: SETTING ‘ALARMS’ ATTRIBUTES OF A SETPOINT PROFILE

5.3 Defining computer local archiving of datapoint events
A computer manages only archiving of the datapoints it is server of (Refer to section 4.6.1
Connecting computer to others station-bus sub-systems, for Client/Server definition).
For computer, archiving is available or not for all the events appearing on a given datapoint.
Archiving is activated as soon as one ‘state treatment’ attribute is set to ‘Archive and logging’
or ‘archive only’ at datapoint profile level (see relevant section of 5.2 Linking a datapoint to a
profile).
5.4 Defining computer local archiving of datapoint alarms
A computer manages only archiving of the datapoints it is server of (Refer to section 4.6.1
Alarm archiving at computer level is defined globally for all the computers at Scs object level
(see section 4.1 Setting general system configuration relevant to computers - point (6))
5.5 Defining computer local logging of datapoint events and alarms
A computer manages only logging of the datapoints it is server of (Refer to section 4.6.1
For computer, event logging is available or not for all the events appearing on a given
datapoint.
Event logging is activated as soon as the datapoint profile is linked to the local printer of the
computer via the relation ‘has events logged on’. To link a datapoint profile to a printer, see
relevant section of 5.2 Linking a datapoint to a profile.
Alarm logging is activated as soon as the datapoint profile is linked to the local printer of the
computer via the relation ‘has alarm events logged on’. To link a datapoint profile to a printer,
see relevant section of 5.2 Linking a datapoint to a profile.
To create a computer printer, see section 4.4.6 Adding a printer.
5.6 Defining acquisition source for input datapoints
Input datapoints have real-time values, fed by several ways exclusive each other:
• Acquisition via input channel(s)
• Acquisition via IED legacy network
• Acquisition via non-PACiS IEC61850 communicant IED
• (virtual) acquisition via software production:
− diagnostic and control of system components
− datapoints relevant to built-in function and user’s function
− MV or counter datapoint relevant to CT/VT board computation

5.6.1 Acquiring input datapoint via input channels
At SCE level, linking datapoint to specific channels (DI or AI channels) belonging to PACiS
computer’s DIU200-210, CCU200, AIU201 or AIU210 boards does input datapoint wiring.
5.6.1.1 Wiring a SPS datapoint, via one DI channel
A wired SPS is in the SET or in the RESET state, depending on the state of the associated
Digital Input and of the mode, normal or inverted (defined in configuration), of the SPS.
DI state Mode SPS state

ON Normal SET
OFF Normal RESET
ON Inverted RESET
OFF Inverted SET
Faulty * SELFCHECK FAULTY
To wire a SPS datapoint on a DI channel:
• Add the relation ‘wired on’ (1) at SPS datapoint level.
• Fill the relation with the relevant DI channel:

When datapoint level is lower than or equal to bay level, only DI channels from DIU
boards belonging to the computer that manages the bay, are available. To define the
computer that manages a bay, refer to section 6.1.4 Defining a Bay.
• If necessary update the relation attribute ‘inverted value’ (2), whose meaning is given
previously.
(1)
FIGURE 225: WIRING ONE SPS DATAPOINT VIA ONE DI CHANNEL
(2)
FIGURE 226: UPDATING THE WIRING OF A SPS DATAPOINT

5.6.1.2 Wiring a DPS datapoint via two DI channels
To wire a DPS datapoint on two DI channels:
• Add the relations ‘closed' wired on (1) and 'open' wired on (2) at DPS level.
• Fill the relations with the relevant DI channels:

When datapoint level is lower than or equal to bay level, only DI channels from DIU
boards belonging to the computer that manages the bay are available. To define the
computer that manages a bay, refer to section 6.1.4 Defining a Bay.
(1)
(2)
FIGURE 227: WIRING A DPS DATAPOINT VIA TWO DI CHANNELS

5.6.1.3 Wiring a MPS datapoint via n DI channels
MPS datapoint wiring is done via 3 or more DI channels (up to 16) for each state, and an
optional DI channel for ‘read inhibit’ indication.
To wire a MPS datapoint on n DI channels (n <=16):
• Add the relations ‘state wired on’ (1) at MPS datapoint level, for each available
state of the MPS (i begins from 0).
• Fill the relations with the relevant DI channels: when datapoint level is lower than or
equal to bay level, only DI channels from DIU boards belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
• If a read inhibit signal exists for the MPS, add the relations ‘read inhibit wired on’ (2) at
MPS datapoint level.
(2)
(1)
FIGURE 228: WIRING A MPS DATAPOINT VIA N DI CHANNEL

5.6.1.4 Wiring MV and TPI datapoint

MV and TPI datapoint wiring is done via 1 AI channel (analogue measurement) or via up to
64 DI channels (for digital measurements) and two optional DI channels for ‘read inhibit’
indication and sign bit.
To wire a MV or TPI datapoint on AI channel:
• Add the relation ‘wired on’ (1) at MV or TPI datapoint level.
• Fill the relation with the relevant AI channel: when datapoint level is lower than or
equal to bay level, only AI channels from AIU boards belonging to the computer that
• To define sensor range of the AI channel, refer to section 4.4.5 Configuring an AI

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

To wire a MV or TPI datapoint on n DI channels (n <=64):
• Add the relations ‘bit wired on’ (1) at MV or TPI datapoint level, for each available
bit channel of the MV or TPI (i begins from 0).
• Fill the relations with the relevant DI channels: when datapoint level is lower than or
• If a read inhibit signal exists for the MV or TPI, add the relations ‘read inhibit wired on’
(2) at MV or TPI datapoint level.
• If a sign bit exists for the MV, add the relations ‘sign bit wired on’ (3) at MV datapoint
level.
(1)
(2) (3)
FIGURE 230: WIRING MV OR TPI DATAPOINT, VIA N DI CHANNEL

5.6.1.5 Wiring a Counter datapoint
A "standard" Counter datapoint ("counter type" attribute set to "standard") wiring is done via
one DI channel (simple standard counter) or two DI channels (double standard counter).
To wire a Counter datapoint on DI channel:
• Add the relation ‘primary input wired on’ (1) at Counter datapoint level.
• If it is a double counter, add the extra relation ‘secondary input wired on’ (2) at
Counter datapoint level.
• Fill the relations with the relevant DI channel: when datapoint level is lower than or
• When the counter is used as an energy counter ("counter type" attribute set to "Energy
import" or "Energy Export") no wiring is needed but the relation "integrate: MV
electrical datapoint" (3) must be added to define the input of the counter. This relation
must be filled with the relevant MV datapoint.
(1) (2)
(3)
FIGURE 231: WIRING COUNTER DATAPOINT, VIA DI CHANNEL

5.6.2 Acquiring input datapoint via an IED legacy network

At SCE level, IED wiring is not described. Acquiring input datapoint issued from IED is done
by giving it a communication address in the relay’s legacy network mapping. This addressing
can be seen as a virtual wiring regardless to channel wiring.
Addressing a MPS datapoint on an IED legacy network is not available.
Depending on legacy network type, addressing information can be different.
See section 4 DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE for
further details about IED legacy network creation and addressing mapping definition.
To link an input datapoint to an existing IED address in an IED mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level. Generally, only one
relation adding is available for datapoint, except for DPS datapoint where up to 2
relations can be added, corresponding to each elementary bit of the DPS if the legacy
protocol does not support the DPS feature. In that case, the DPS is split in two SPS
regarding to the legacy protocol.
• Fill the relation with the relevant IED address: when datapoint level is lower than or
equal to bay level, only IED addresses from IEDs belonging to the computer that
(1)
FIGURE 232: ACQUIRING INPUT DATAPOINT VIA IED LEGACY NETWORK

(E.G. SPS DATAPOINT)
• A "DPS" datapoint can have one or two relation(s) "has for IED address":
- In the case of one IED address, the attribute "contact type" of the IED address must
be set to the "Unused" value.
- In the case of two IED addresses, the attribute "contact type" of one of the IED
addresses must be set to the "open" value, and the attribute "contact type" of the other
IED address must be set to the "close" value.
5.6.3 Acquiring input datapoint via non-PACiS IEC61850 communicant IED

At SCE level, IED wiring is not described. Acquiring input datapoint issued from IEC61850
IED is done by giving it a communication address in the relay’s IEC61850 mapping. This
addressing can be seen as a virtual wiring regardless to channel wiring (implicit association
is done at IED level).
See relevant application guide for further details about IED creation and corresponding
UCA2/IEC addressing mapping definition (nevertheless, similar UCA2/IEC addressing
mapping is described in section 4.6.2 Defining addressing mapping of station-bus network of
the present guide).
To link an input datapoint to an existing IEC61850 IED address in the IED mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level
• Fill the relation with the relevant IEC61850 address

Do not confuse:
• Give an IEC61850 address to a datapoint, still wired on a computer, via ‘has for IEC
address’ relation adding.
• Give an IEC address to a datapoint on an IEC IED. In that case the datapoint can not
be wired, because it is seen as produced or managed by the IEC IED.
(1)
FIGURE 233: ACQUIRING INPUT DATAPOINT VIA NON-PACIS IED

(E.G. SPS DATAPOINT)
5.6.4 Producing input datapoint

Another way to produce input datapoint real-time values is to allow software functions to
generate them.
This is done at several software levels:
• Supervision of IEC61850 PACiS system device, where system datapoints are produced
to indicate mode device, synchro device, database status,…
• Supervision of IEC61850 PACiS system device board (board status diagnostics).
• Supervision of legacy network and IED managed by PACiS computers (communication
status diagnostics).
• Supervision of redundancy between two PACiS computers (redundancy status
diagnostics).
• Supervision of logging printers managed by OI server or PACiS computer (printer status
diagnostics).
• Supervision of archiving managed by OI server (archiving status diagnostics).
• Facilities given by built-in electrical and grouping functions or user’s function, in PACiS
computers.
5.6.4.1 Implicit system input datapoint via system decomposition
In data modelling many components of the system topology own input datapoints. Their
creation is generally implicit when creating the component: they belong to its hierarchy.
Most of system input datapoints when transmitted on station bus network are addressed in
IEC61850 diagnostics bricks.
The list of such system datapoints are given in section 4.11 Setting system information for
computer components.
5.6.4.2 Implicit electrical input datapoint via built-in function
Implicit input datapoints can be embedded in built-in function creation. For details refer to the
following sections:
• 6.2 Defining a Synchrocheck function,
• 6.3 Defining an Auto-recloser built-in function,
• 6.4 Defining a Tap changer built-in function,
• 6.5 Defining an Automatic Voltage Regulation (AVR) built-in function.

Generally, these electrical datapoints are transmitted on station bus network in a specific
IEC61850 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 section 6.6.1 Defining a FBD fast automation).
So can slow automation when it manages electrical datapoints or owns management input
datapoints (see section 6.6.2 Erreur ! Source du renvoi introuvable.).
For group needs, an electrical SPS containing the group result must be created (see section
6.6.3 Defining a group).
For SPS-DPS association, the resulting DPS is the product of the two SPS associations (see
section 6.6.5 Producing a DPS ).
To define (open or close) interlocking equation on SPC or DPC datapoint, an extra (open or
close) SPS should be produced, whose result is interlocking equation computation (see
section 6.6.6 Defining interlocking).
5.6.4.4 Explicit electrical input datapoint via CT/VT computation

Another way to produce a MV electrical datapoint is to link it to a CT/VT computer board.
Then, a specific link attribute must be filled to precise which MV computation is concerned
(power, harmonic ...).
Data produced by CT/VT board computation concern:
• RMS Values of phase voltage
• RMS values of busbar voltage
• RMS values of phase current
• RMS values of residual voltage and current
• Fundamental sequence components
• Active Power
• Reactive Power
• Apparent Power
• Frequency
• Harmonics levels ( expressed as a ratio of the magnitude of the fundamental voltage

or fundamental current)
To link a MV datapoint to a CT/VT computation:
• Add the relation ‘is computed by’ (1) at datapoint level.
• Fill the relation with the relevant CT/VT board. When datapoint level is lower than or
equal to bay level, only the CT/VT board belonging to the computer that manages the
bay, is available. To define the computer that manages a bay, refer to section 6.1.4
Defining a Bay.
• Update the relation attribute ‘measure type’ (2), giving the computation type.
(1)
FIGURE 234: DEFINING CT/VT COMPUTATION FOR A MV DATAPOINT

5.7 Defining control source for output datapoints

Output datapoints have real-time control values, managed by several ways exclusive each
other:
• control via output channel(s)
• control via IED legacy network
• control via non-PACiS IEC61850 communicant IED
• (virtual) control via software production:
− control of system components
− datapoints relevant to built-in function and user’s function

5.7.1 Controlling output datapoint via output channels
At SCE level, linking datapoint to specific channels (DO channels) belonging to PACiS
computer’s DOU200 or CCU200 boards does output datapoint wiring.
5.7.1.1 Wiring a SPC datapoint via one DO channel
To wire a SPC datapoint on a DO channel:
• Add the relation ‘wired on’ (1) at SPC datapoint level.
• Fill the relation with the relevant DO channel: when datapoint level is lower than or
equal to bay level, only DO channels from DOU boards belonging to the computer that
(1)
FIGURE 235: WIRING A SPC DATAPOINT VIA ONE DO CHANNEL

5.7.1.2 Wiring DPC datapoint via two or four DO channels
To wire a DPC datapoint on two or four DO channels:
• Add the relations ‘closed wired on’ (1) and ‘open wired on’ (2) at DPC datapoint level
(these relations can be added twice in case of 4 DO channels use).
• Fill the relations with the relevant DO channels: when datapoint level is lower than or
(1)
(2)
FIGURE 236: WIRING A DPC DATAPOINT VIA TWO 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 wired on’ (1) at SetPoint datapoint level, for each available bit
channel of the SetPoint (i begins from 0)
• Fill the relations with the relevant DO channels: when datapoint level is lower than or
• If a read inhibit signal exists for the SetPoint (see section 5.1.11.1 Overview of
SetPoint processing), add the relations ‘read inhibit wired on’ (2) at SetPoint datapoint
level.
• If a refresh signal exists for the SetPoint (see section 5.1.11.1 Overview of SetPoint
processing), add the relations ‘refresh wired on’ (3) at SetPoint datapoint level.
• If a sign bit exists for the SetPoint, add the relations ‘sign bit wired on’ (4) at SetPoint
datapoint level.
(1)
(2)
(3) (4)
FIGURE 237: WIRING A SETPOINT DATAPOINT VIA N DO CHANNEL

• A Setpoint datapoint wired on DO channels of Computer, must be digital and have its
profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute with SBO
popup”
5.7.2 Controlling output datapoint via an IED legacy network

At SCE level IED wiring is not described. Controlling output datapoint issued from IED is
done by giving it a communication address in the relay’s legacy network mapping. This
addressing can be seen as a virtual wiring regardless to channel wiring (implicit association
is done at IED level).
Depending on legacy network type, addressing information can be different.
See section 4 DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE for
further details about IED legacy network creation and addressing mapping definition.
To link an output datapoint to an existing IED address in an IED mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level. Generally, only one
relation adding is available for a datapoint, except for a DPC datapoint where up to
two relations can be added, corresponding to each elementary bit of the DPC if the
legacy protocol does not support the DPC feature. In that case, the DPC is split in two
SPC regarding to the legacy protocol.
• Fill the relation with the relevant IED address: when datapoint level is lower than or
equal to bay level, only IED addresses from IEDs belonging to the computer that
(1)
FIGURE 238: ACQUIRING OUTPUT DATAPOINT VIA IED LEGACY NETWORK

(E.G. SPC DATAPOINT)
• A "DPC" datapoint can have one or two relation(s) "has for IED address":
- In the case of one IED address, the attribute "contact type" of the IED address must
be set to the "Unused" value.
- In the case of two IED addresses, the attribute "contact type" of one of the IED
addresses must be set to the "open" value, and the attribute "contact type" of the other
IED address must be set to the "close" value.
5.7.3 Controlling output datapoint via non-PACiS IEC61850 communicant IED

At SCE level, IED wiring is not described. Controlling output datapoint issued from IED is
done by giving it a communication address in the relay’s IEC61850 mapping. This
addressing can be seen as a virtual wiring regardless to channel wiring.
See relevant application guide for further details about IEC61850 IED creation and
corresponding IEC addressing mapping definition (nevertheless, similar IEC addressing
mapping is described in section 4.6.2 Defining addressing mapping of station-bus network of
the present guide).
To link an output datapoint to an existing IED address in the IED IEC mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level
• Fill the relation with the relevant IEC address

Do not confuse:
• Give an IEC address to a datapoint, still wired on a computer, via ‘has for IEC
address’ relation adding.
• Give an IEC address to a datapoint on an IEC IED. In that case the datapoint can not
be wired, because it is seen as produced or managed by the IEC IED.
(1)
FIGURE 239: ACQUIRING OUTPUT DATAPOINT VIA NON-PACIS IEC IED

5.7.4 Producing output datapoint

Another way to produce output datapoint real-time control values is to allow software
functions to generate them.
This is done at several software levels:
• Supervision of IEC61850 PACiS system device, where system datapoints are

produced to control mode device, database switch.
These output system datapoints are only used by System Management Tool.
• Supervision of redundancy between two PACiS computers (redundancy controls).
• Facilities given by built-in electrical and grouping functions or user’s function, in PACiS
computers.
5.7.4.1 Implicit system output datapoint via system decomposition
In data modelling, only PACiS devices of the system topology own output datapoints for
device mode management and database switch. Their creation is implicit when creating the
device: they belong to its hierarchy.
Computer redundancy needs specific output typed datapoints that must be manually added
in computer’s hierarchy.
Most of system output datapoints when transmitted on station bus network are addressed in
IEC61850 diagnostics bricks.
The list of such system datapoints are given in section 4.11 Setting system information for
computer components.
5.7.4.2 Implicit electrical output datapoint via built-in function
Implicit output datapoints can be embedded in built-in function creation. For details refer to
the following sections:
• 6.2 Defining a Synchrocheck function,
• 6.3 Defining an Auto-recloser built-in function,
• 6.4 Defining a Tap changer built-in function,
• 6.5 Defining an Automatic Voltage Regulation (AVR) built-in function.

Generally, these electrical datapoints are transmitted on station bus network in a specific
IEC61850 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 section 6.6.1 Defining a FBD fast automation).
So can slow automation when it manages electrical output datapoints or owns management
output datapoints (see section 6.6.2 Erreur ! Source du renvoi introuvable.).
For xPS-xPC association, an electrical output SPC or DPC linked to the SPS or DPS must
exist and sometimes be created (see section 6.6.4 Controlling xPC ).
5.7.5 ACKnowledgement definition in case of simultaneous orders
When two opposite orders (Open/Close or Close/Open) are simultaneous and from different
origins, the acknowledgment management is described on the following table:
Cmd1 Cmd2 Action Ack

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

PSL PSL Cmd 2 Ignored NA
PSL Operator Cmd 2 Ignored CO_REQUEST_IN_PROGRESS (ACK 6)
Operator PSL Cmd 2 Ignored NA
Operator Operator Cmd 2 Ignored CO_REQUEST_IN_PROGRESS (ACK 6)
5.8 Defining datapoint association

This functionality allows to create a link between two datapoints so that the state of one
datapoint (called the target datapoint) is defined by the state of the other datapoint (called
the original datapoint).
Target datapoints can be one of the following types: SPS or DPS. They are available with
default name Mapping SPS and Mapping DPS at each level of the Electrical topology. In
the example given here after these two "target" datapoints are shown at the Substation level
(1).
(1)
FIGURE 240: THE TWO TARGET DATAPOINTS OF THE SUBSTATION LEVEL

Original datapoints can be one of the following types: SPS, DPS, MPS, MV.
5.8.1 Adding a target datapoint
Addition of a target datapoint is done via the “Objects entry” area associated to the
required electrical level ( Substation in our example) by double clicking the Mapping xPS ( or
right-clicking it and then clicking Add).
5.8.2 Linking the target datapoint to the original datapoint

To link the target datapoint to the original datapoint a relation 'is mapped on' (1) must be
added to the selected "original" datapoint (order running at generic bay level in our
example). When added the undefined relation is present in the "Contents of" window
associated to the order running datapoint (2).
(1)
(2)
FIGURE 241: LINKING THE TARGET DATAPOINT OF THE ORIGINAL DATAPOINT

To select the target datapoint double-click the undefined relation "is mapped on:" (3). In the
Relation link editor dialog box are displayed all the available Mapping DPS datapoints (4).
Click the Mapping DPS datapoint you want to be associated to the order running datapoint
( Subs Mapping DPS in our example) then click the OK button.
(3)
(4)
FIGURE 242: SELECTING THE TARGET DATAPOINT

5.8.3 Defining the states associations

For every possible state of the original datapoint the user can define the corresponding state
of the target datapoint. To perform this association click the now defined relation "is mapped
on:" (5) in the "Contents of:" window associated to the "order running" datapoint. In the
"Attributes of:" window associated to this relation are listed all the possible states of the
original datapoint (6) and for each one the user has to select the corresponding state of the
target datapoint (7).
(5)
(6)
(7)
FIGURE 243: DEFINING THE STATES ASSOCIATIONS

• Up to 10 target datapoints can be associated to an original datapoint
• Up to 100 datapoints can be defined as original datapoints
• The original datapoint and the target datapoint can belong to different computers. In
this case the states of the original datapoints are transmitted through GOOSE
messages
• A target datapoint is managed as any other datapoint: transmission, used in

automation, alarms, …
• A SPS original datapoint can be associated to a SPS or a DPS
• A DPS original datapoint can be associated to a SPS or a DPS
• A MPS original datapoint can only be associated to a SPS ( the relation "is mapped
on: Mapping DPS Electrical datapoint" is not available in the "Object entry" window
associated to a MPS)
• A MV original datapoint can only be associated to a SPS ( the relation "is mapped on:
Mapping DPS Electrical datapoint" is not available in the "Object entry" window
associated to a MV)
6. DEFINING COMPUTER CONFIGURATION IN ELECTRICAL

ARCHITECTURE
6.1 Defining an electrical topology
At SCE data modelling level, the entry point of electrical topology is the ‘Site’ object. At the
moment, a ‘Site object’ (1) can be composed of only one ‘Substation’ object.
A substation (2) is constituted of ‘Voltage level’ objects, each of them corresponding to an
electrical partitioning of the substation by voltage level value (in kV).
A voltage level (3) is an aggregation of ‘Bay’ object (4), grouping of electrical devices, called
module (5). Generally this grouping is electrically self-safety, i.e. can be isolated from others
bays by switchgears for maintenance and managed by only one PACiS computer. There are
different kinds of bays: feeder, transformer, busbar, bus coupler, bus section, capacitor bank
and generic bay.
Coupling two voltage levels is commonly done via transformer. To respect SCE data
modelling electrical partitioning, this transformer must belong to a transformer bay (6)
arbitrary put in one of both voltage levels (generally its primary). An extra relation on
transformer defines to which voltage level its secondary (or primary) belongs.
Final electrical components are modules composing bays. There are different kinds of
modules: circuit breaker, switchgear, transformer, motor, generator, battery, capacitor,
inductor, converter and generic module. An extra module exists to describe substation
external connection (external line).
Every level of the electrical topology, except Site level, can own datapoints whose features
and configuration are described in section 5 DEFINING DATAPOINT.
(1) : Site
(2): Substation
n
(3) : Voltage level
(4) : Bay 'Feeder'
datapoints
(5) : Module 'Circuit breaker'
(6): Bay 'Transformer'
C0211ENb
FIGURE 244: ELECTRICAL TOPOLOGY DEFINITION (E.G.)

Feeder bay
Bus coupling bay
Transformer bay
Busbar bay
Bus section bay
C0212ENa
FIGURE 245: BAY SAMPLES
Switchgear
module
Q1
Circuit-breaker
module
Q0
Switchgear
module Q9
Switchgear Q8
Module (earth)
External line
module
C0213ENa
FIGURE 246: MODULE SAMPLES

6.1.1 Defining a Site

When creating a new configuration with the SCE, the electrical topology is automatically
instantiated via a ‘Site’ root object, containing a mandatory ‘Substation’ object.
A Site object corresponds to customer project identification: its attributes short name and
long name (1) can be entered at SCE level. At the moment, these attributes are not used.
(1)
FIGURE 247: SETTING ATTRIBUTES OF A SITE

6.1.2 Defining a Substation
When creating a new configuration using SCE, the electrical topology is automatically
instantiated via ‘Site’ root object, containing a mandatory ‘Substation’ object.
A Substation object corresponds to customer substation identification: its attributes short
name and long name (1) must be entered at SCE level, for proper logging formatting and
datapoint identification, at computer and operator interface levels.
At substation level, the attribute ‘default uniqueness’ (2) defines the way control uniqueness
is managed for the whole substation. Available values are:
• None: no control uniqueness is provided by PACiS system for the substation.
• Substation level: control uniqueness is provided by PACiS system for the whole
substation, i.e. two simultaneous controls are refused within the substation, except for
control datapoints configured as substation uniqueness independent (see sections
5.1.9.2 Setting ‘Dependencies’ attributes of a SPC datapoint, 5.1.10.2 Setting
‘Dependencies’ attributes of a DPC datapoint, 5.1.11.4 Setting ‘Dependencies’
attributes of a 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 sections 5.1.9.2 Setting
‘Dependencies’ attributes of a SPC datapoint, 5.1.10.2 Setting ‘Dependencies’
attributes of a DPC datapoint, 5.1.11.4 Setting ‘Dependencies’ attributes of a SetPoint
datapoint).
(1)
(2)
FIGURE 248: SETTING ATTRIBUTES OF A SUBSTATION

Bay and substation uniqueness are managed by computer by synthesis of mandatory SPS
datapoints ‘Order running’, automatically added under a bay at its creation (see section 6.1.4
Defining a Bay).
• When control uniqueness is set to substation, all computers of substation must be

IEC-61850 client of all ‘order running’ SPS datapoints defined for all the bays. So,
proper IEC-61850 configuration must be done for all computers to insure that feature.
For details about IEC-61850 configuration, refer to section 4.6 Networking computer
on the station-bus network.
6.1.2.1 Adding a substation generic datapoint
The addition of a substation typed datapoint is done via the “Objects entry” window at
substation level by clicking on mouse’s right button. Here are listed generic datapoint
(standard usage) out of scope of the specific substation functions:
• Local/remote for substation (see section 6.1.2.2 Defining Local/Remote for substation)
• Taking Control for substation and SCDA links (see section 6.1.2.3 Defining Taking
Control for substation and SCADA links)
For more details about datapoints and their configuration, refer to section 5 DEFINING
DATAPOINT.
(2)
(1)
FIGURE 249: ADDING GENERIC DATAPOINT TO A SUBSTATION

NOTE: A Global alarm ack SPS (1) can be added to the substation level in
order to automatically acknowledge the new alarms in the C264 and
also in the OI. The detection mode attribute of this SPS must be set
to "Permanent" or "Permanent with computer auto-reset". This SPS
may be any wired SPS or SPS activated by a control ( by using the
Glb alm ack ctrl SPC(2)) from the SCADA or generated by any PSL.
It is also possible to launch a global alarm acknowledment at a fixed
time by using a cyclic SPS ( described in section 6.1.4.1 Adding bay
generic datapoint)
6.1.2.2 Defining Local/Remote for substation

A substation can be in remote or local control mode.
The Remote mode indicates that the substation is controlled from Remote Control Point
(RCP), via gateway. No controls can be sent from Substation Control Point level (except if
the concerned bay is in SBMC mode, see section 6.1.4.3 Defining SBMC for bay).
The Local mode indicates that the substation is controlled from PACiS Operator Interface
(Substation Control Point). The controls issued from RCP are not taken into account by the
system, they are refused.
Some controls, defined during the configuration phase, can be independent of the substation
control mode : it means they can be issued from SCP or RCP whatever the current control
mode is. Controls from configurable automation (see section 6.6 Defining an electrical
regulation by user function) are accepted whatever was the mode. For details about the
configuration of this dependency attribute, refer to sections:
• SPC: 5.1.9.2 Setting ‘Dependencies’ attributes of a SPC datapoint,
• DPC: 5.1.10.2 Setting ‘Dependencies’ attributes of a DPC datapoint,
• SetPoint: 5.1.11.4 Setting ‘Dependencies’ attributes of a SetPoint datapoint.

In Local or Remote mode the information acquired by computers and IEDs are always sent
to RCP and PACiS Operator Interface.
The automatic “Forcing of Invalid BI” function is used to avoid processing of invalid states of
the substation mode (the local or remote replacement state is defined in configuration). The
“Forced Local” state is processed as the “Local” state. The “Forced Remote” state is
processed as the “Remote” state.
Moreover, all IEC61850 clients (i.e. Operator Interface, gateway, computers) will
automatically forced the substation mode to “Forced Local” or “Forced Remote” if it takes the
UNKNOWN state (due for example to the loss of communication between the computer
which manages the substation mode and the IEC61850 clients).
To activate Local/remote substation facilities:
• add the optional datapoints ‘Local/remote DPS’ (1) and/or ‘Loc/rem ctrl DPC’ (2), via
the “Objects entry” window at substation level by clicking on mouse’s right button,
• configure them (see section 5 DEFINING DATAPOINT),
• if necessary, do not forget to link via ‘has for feedback’ relation, the control of the
Local/remote with the Local/remote status datapoint.
(2)
(1)
FIGURE 250: DEFINING LOCAL/REMOTE FOR SUBSTATION


Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
computer.
• If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback).
• If "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is mandatory.
• If "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.
• If, under a Substation, a "DPC" or "SPC" datapoint has its attribute "Substation mode
dependency" set to "Yes", then the Substation "Local/remote DPS" datapoint must be
present.
• If the two datapoints "Local/remote DPS" and "Loc/rem ctrl DPC" are present, they
must have the same Server device.
• "Loc/rem ctrl DPC" datapoint must have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”.
6.1.2.3 Defining Taking Control for substation and SCADA links
This facility allows a Remote Control Point (RCP) to force the mode of the substation from
LOCAL to REMOTE and to define on which link the SCADA controls must be accepted.
To activate Taking control facilities for a given SCADA network:
• add the optional datapoints ‘Taking Control’ (2) and ‘Taking status’ (1), via the
“Objects entry” window at substation level by clicking on mouse’s right button.
• configure them (see section 5 DEFINING DATAPOINT).
• add the relation ‘is taken control of’ at ‘Taking status’ datapoint level (3), and fill it with
the relevant given SCADA network.
• do not forget to link via ‘has for feedback’ relation, the control with the status
datapoint.
(2)
(1)
(1)
FIGURE 251: DEFINING TAKING CONTROL FOR A SCADA LINK

• If, at least, one SCADA network is linked to a Taking Control function, all the SCADA
Networks of the system must be linked to a Taking Control function.
• If a "Taking Status" datapoint is linked to a SCADA Network, it must also be linked to a

"Taking Control" datapoint through the relation "has for feedback".
• A "Taking Control" datapoint must be linked to a "Taking Status" datapoint through the
relation "has for feedback".
• The "Taking Control" datapoint must have its "activation mode" attribute set to a
"Permanent…" value. The "Taking Status" datapoint must have its "detection mode"
attribute set to the "Permanent" value.
• Both "Taking Control" and "Taking Status" datapoints must be linked to a SCADA
address in the mapping of their SCADA network.
• If a Taking-Control function is defined then, the "Loc/rem ctrl DPC" for substation must
be present and not wired.
• The Server of the Local/Remote datapoints is the Server of each datapoints couple
"Taking Status" / "Taking Control".
• All the devices having a SCADA network linked to a Taking-Control function are:
- Clients of each datapoints couple "Taking Status" / "Taking Control".
- Clients of the datapoints couple "Local/remote DPS" / "Loc/rem ctrl DPC".
6.1.2.4 Adding a user function to a substation
The addition of a substation user function is done via the “Objects entry” window at
substation level by clicking on mouse’s right button.
For more details about user function usage and their configuration, refer to section 6.6
Defining an electrical regulation by user function.
FBD user function
ISAGRAF user function
C0214ENb
FIGURE 252: ADDING USER FUNCTION TO SUBSTATION

6.1.3 Defining a Voltage level

At substation level, several ‘voltage level’ objects can be added. A voltage level corresponds
to a substation area whose electrical bays and sub-modules refer to the same nominal
voltage. There is an exception for transformer bay, coupling 2 different voltage levels, that
must be arbitrary located on one of the both.
To create a voltage level, add it from object entry available at substation level, as following:
FIGURE 253: ADDING A VOLTAGE LEVEL

When adding a voltage level, some general attributes must be updated:
2. nominal value in kV
3. ATCC existence (No / Yes): when set to ‘yes’, an extra tab-pane appears for the
voltage level, to enter specific ATCC regulation feature for the voltage level. For
details about ATCC configuration and this attribute, refer to section 6.5 Defining an
Automatic Voltage Regulation (AVR) built-in function
(1)
(2)
(3)
FIGURE 254: SETTING GENERAL ATTRIBUTES OF A MV DATAPOINT

6.1.3.1 Adding voltage level generic datapoint

The addition of a voltage level typed datapoint is done via the “Objects entry” window at
voltage level by clicking on mouse’s right button. Here are listed the generic datapoints
(standard usage).
For more details about datapoints and their configuration refer to section 5 DEFINING
DATAPOINT.
FIGURE 255: ADDING VOLTAGE LEVEL GENERIC DATAPOINT

6.1.3.2 Adding user function to voltage level
The addition of a voltage level user function is done via the “Objects entry” area at voltage
level by clicking on mouse’s right button.
FBD user function
C0214ENb
FIGURE 256: ADDING A USER FUNCTION TO VOLTAGE LEVEL

6.1.4 Defining a Bay

At ‘voltage level’ level, several ‘bay’ objects can be added. A voltage level corresponds to a
substation area whose electrical bays and sub-modules refer to the same nominal voltage.
There is an exception for transformer bay, coupling two different voltage levels that must be
arbitrary located on one of the both.
To create a bay:
• Add a typed one from object entry available at voltage level (1).
• Update the bay attributes.
• Update its ‘is managed by’ relation, to define which computer manages the bay (2).
(1)
FIGURE 257: ADDING A TYPED BAY
(2)
FIGURE 258: DEFINING COMPUTER MANAGING A BAY

When adding a bay, some general attributes must be updated:
1. short name and long name of the bay used for logging, alarms ...
2. control uniqueness used for output datapoints under the bay.
− None: no control uniqueness is provided by PACiS system for output datapoints

under the bay.
− See substation definition: control uniqueness is inherited from attribute ‘default

uniqueness’ at substation level (see section 6.1.2 Defining a Substation).
(1)
(2)
FIGURE 259: SETTING GENERAL ATTRIBUTES OF A BAY

(SAMPLE GIVEN FOR BAY TYPE ‘FEEDER’)
When adding a bay, a mandatory SPS datapoint ‘order running’ is automatically created at
bay level. This datapoint allows PACiS system to manage control uniqueness at substation
and bay level: it is set when a control is in progress on a bay.
• When control uniqueness is set to substation, all computers of substation must be

IEC61850 client of all ‘order running’ SPS datapoints defined for all the bays. So,
proper IEC61850 configuration must be done for all computers to insure that feature.
For details about IEC61850 configuration, refer to section 4.6 Networking computer on
the station-bus network.
Typed bay features
Using typed bay allows implicit sub-component creation. Hereafter are listed all typed bays
with their sub-component features:
• Feeder: a circuit-breaker and external line modules are mandatory and implicitly
created,
• Transformer: a transformer module is mandatory and implicitly created,
• Bus coupler: a circuit-breaker module is mandatory and implicitly created,
• Bus section: a circuit-breaker module is mandatory and implicitly created,
• Capacitor bank: a capacitor module is mandatory and implicitly created,
• Shunt: a circuit-breaker module is mandatory and implicitly created,
• Busbar: no module is available. This typed bay must be seen as a single electrical
node. A specific attribute ‘node reference’ used for electrical topology definition for
ATCC function can be entered for a busbar. For details about ATCC configuration and
this attribute, refer to section 6.5 Defining an Automatic Voltage Regulation (AVR)
built-in function.
• Generic bay: no sub-component constraint. Used for general usage outside the scope
of other previous typed bays.
6.1.4.1 Adding bay generic datapoint

The addition of a bay typed datapoint is done via the “Objects entry” window at bay level by
clicking on mouse’s right button. Here are listed generic datapoint (standard usage) out of
scope of the specific bay functions:
• Local/remote for bay (see section 6.1.4.2 Defining Local/Remote for bay)
• SBMC for bay (see section 6.1.4.3 Defining SBMC for bay)
• Group computation (see section 6.6.3 Defining a group)

DATAPOINT.
(1)
(2)
FIGURE 260: ADDING GENERIC DATAPOINT TO A BAY

NOTE: In a C264, up to eight transient SPS ( 1) can be defined as cyclic (day
cycle). They can be used to activate a periodic treatment. For these
SPS the user has to configure, in addition to the usual attributes of a
SPS (previously listed in section 5.1.2.2 Creating a SPS datapoint)
two specific attributes (2) which define the time when activation of the
SPS will occur.
6.1.4.2 Defining Local/Remote for bay

Each bay can be independently in Remote or Local mode.
The Remote mode indicates that the bay is controlled from the upper level, i.e. Remote
Control Point (RCP) or Substation Control Point (SCP) depending on the current substation
control mode. No controls can be sent from Bay Control Point (BCP) level, i.e. operator
interface at the computer that manages the bay.
The Local mode indicates that the bay is controlled from BCP. The controls issued from
upper level are not taken into account by the bay.
Some controls, defined during the configuration phase, can be independent of the bay
control mode: it means they can be issued from any control points whatever was the current
control mode. Controls from configurable automation (ISAGRAF) are accepted in remote
mode. For details about the configuration of this dependency attribute, refer to sections:

In Local or Remote mode, the information issued from the bay is always sent to SCP and
RCP.
The automatic “Forcing of Invalid BI” function is used to avoid processing of invalid states of
the bay mode (the local or remote replacement state is defined in configuration). The
“Forced Local” state is processed as the “Local” state. The “Forced Remote” state is
processed as the “Remote” state.
To activate Local/remote bay facilities:
• add the optional datapoints ‘Local/remote DPS’ (1) and/or ‘Loc/rem ctrl DPC’ (2), via
the “Objects entry” window at bay level by clicking on mouse’s right button
• if necessary, do not forget to link via ‘has for feedback’ relation, the control of the
Local/remote with the Local/remote status datapoint.
(2)
(1)
FIGURE 261: DEFINING LOCAL/REMOTE FOR BAY


Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
computer
• If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback).
• If "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must not be wired.
• If "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.
• If, under a Bay, a "DPC" or "SPC" datapoint has its attribute "bay mode dependency"
set to "Yes", then the Bay "Local/remote DPS" datapoint must be present.
• "Loc/rem ctrl DPC" datapoint must have its profile attribute “SBO mode” set to "Direct
If the "GHU200" board of a computer has its attribute "HMI type" set to the "Simple" value,
then the "Local/remote DPS" datapoints of the bays managed by this computer must be all
be "Wired" or all "System".
6.1.4.3 Defining SBMC for bay
Each bay can be set in SBMC mode (Site Based Maintenance Control mode).
In SBMC mode, a bay does not take into account the commands issued from Remote
Control Point (RCP), even if the substation is in remote control (see section 6.1.4.2 Defining
Local/Remote for bay). Some controls, defined during the configuration phase, can be
independent of the SBMC mode. For details about the configuration of this dependency
attribute, refer to sections:

This function provides a facility to control selected bays from the Substation Control Point
(SCP) and optionally to suppress or force to a pre-defined state, datapoint for the RCP while
the substation is in Remote mode. If configured as SBMC dependant at its profile level, a
datapoint belonging to a bay in SBMC mode takes the state defined in the profile
configuration for the RCP, but is still processed normally in the SCS (e.g. all processes
inside the system are unaffected by the state modification of an information at the RCP
interface).
The state of a datapoint sent to RCP is defined in its profile configuration. For each type of
datapoint, they are:
SPS SUPPRESSED, SET, RESET

DPS SUPPRESSED, OPEN, CLOSE, JAMMED
MPS SUPPRESSED, UNDEFINED
MV, TPI and Counter SUPPRESSED
To activate SBMC facilities at bay level:
• add the optional datapoints ‘SBMC SPS’ (1) and ‘SBMC control SPC’ (2), via the
“Objects entry” window at bay level by clicking on mouse’s right button,
• do not forget to link via ‘has for feedback’ relation, the control of the SBMC with the
SBMC status datapoint.
(2)
(1)
FIGURE 262: DEFINING SBMC FOR BAY

• If "SBMC SPS" is present, then "SBMC control SPC" must be present.
• If "SBMC control SPC" is present, then "SBMC SPS" must be present.
• If "SBMC control SPC" is present, then its attribute "bay mode dependency" must be
set to "No".
• If a "DPC" or "SPC" datapoint has its attribute "SBMC mode dependency" set to "Yes",
then the "SBMC SPS" datapoint must be present.
• If a "DPS" or "SPS" datapoint has the attribute "SBMC dependant" of its profile set to
"Yes", then the "SBMC SPS" datapoint must be present.
6.1.4.4 Adding a user function to a bay
The addition of a bay user function is done via the “Objects entry” window at bay level by
clicking on mouse’s right button.
FBD user function
C0216ENb
FIGURE 263: ADDING USER FUNCTION TO BAY

6.1.5 Defining Module

This section deals with general module configuration. Configuring specific typed module is
described in following relevant section.
At ‘bay’ level, several ‘module’ objects can be implicitly or explicitly added. A module
corresponds generally to a substation electrical device.
To create explicitly a module:
• Add a typed one from object entry available at bay (1)

For implicit or explicit module:
• Update the module attributes (see following sections)
(1)
FIGURE 264: ADDING EXPLICITLY A TYPED MODULE

When adding a module, some general attributes must be updated:
1. short name and long name of the module used for logging, alarms ...
2. ‘node reference’, used for electrical topology definition for ATCC function. For details
about ATCC configuration and this attribute, refer to section 6.5 Defining an Automatic
Voltage Regulation (AVR) built-in function
(1)
(2)
FIGURE 265: SETTING GENERAL ATTRIBUTES OF A GENERIC MODULE

Typed module features

Using typed module specialises module configuration. Hereafter are listed all typed modules
with their main configuration features:
• Capacitor, Inductor:
− Specific attribute ‘reactive power value’ (in MVA), used for ATCC regulation. For
details about ATCC configuration and this attribute, refer to section 6.5 Defining
an Automatic Voltage Regulation (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 section 6.5 Defining an Automatic Voltage Regulation (AVR)
built-in function.
• Circuit-breaker module:
− Supports synchrocheck and autorecloser built-in functions.
− May support withdrawing if it exists.
• Switchgear module
− May support withdrawing if it exists.
• External line:
− Only support SPS and DPS attribution.
• Generic module:
− Used for general usage outside the scope of other previous typed modules.
6.1.5.1 Adding a module generic datapoint
The addition of a module typed datapoint is done via the “Objects entry” window at module
level by clicking on mouse’s right button. Here are listed generic datapoint (standard usage)
out of scope of the specific module functions:
• Group computation (see section 6.6.3 Defining a group).
• Locking module (see section 6.1.5.3 Defining a lockable module).
• Specific features and configuration of typed modules (see following sections).

DATAPOINT.
FIGURE 266: ADDING A MODULE GENERIC DATAPOINT

(E.G. FOR GENERATOR MODULE)
6.1.5.2 Adding a user function to a module
The addition of a module user function is done via the “Objects entry” window at module
Module does not support ISAGRAF function.
FBD user
FIGURE 267: A USER FUNCTION TO A MODULE (E.G. FOR GENERATOR MODULE)

6.1.5.3 Defining a lockable module
According to PACiS system, locking module is a system function running on the computer
that manages the bay containing the module.
When a module is locked, any subsequent control acting on it, is refused. Locking is checked
during control sequence processing at computer level (see section 5.1.8 Overview of control
sequence processing).
At SCE level, only following types modules are lockable:
• Circuit-breaker,
• Switchgear,
• Transformer,
• Generic module.
To configure such a module as lockable:
• Add the pre-defined SPS datapoint ‘Lock SPS’ at module level (1) and configure it
(see section 5 DEFINING DATAPOINT),
• Add the pre-defined SPC datapoint ‘Lock control SPC’ at module level (2) and
configure it (see section 5 DEFINING DATAPOINT),
• Define the ‘Lock SPS’ as feedback of the ‘Lock control SPC’ by adding and filling ‘has
for feedback’ relation at the SPC level (see section 5.1.9.3 Defining a SPC feedback).
(2)
(1)
FIGURE 268: DEFINING A LOCKABLE MODULE

Lock SPS and Lock control SPC are datapoints fed and controlled directly by the computer
that manages the module. They can not be wired.
• For “Lock control SPC“, the feedback to “Lock SPS“ is mandatory

6.1.5.4 Defining withdrawable circuit-breaker or switchgear
To define a withdrawable circuit-breaker or switchgear:
• add the pre-defined SPS ‘withdraw’ at module level
• configure it (see section 5 DEFINING DATAPOINT)

Withdraw information is useful for bay mimic animation at computer LCD level. For more
details see section 7.3 Defining a computer bay mimic.
(1)
FIGURE 269: DEFINING A WITHDRAWABLE MODULE

(E.G. FOR CIRCUIT BREAKER)
6.1.5.5 Defining a circuit-breaker
This section deals with general circuit-breaker features and available associated input and
output datapoints at computer level.
If the circuit-breaker is synchronised by internal or external synchrocheck, extra datapoints

exist. For more details refer to section 6.2 Defining a Synchrocheck function.
General module features described in section 6.1.5 Defining Module are applicable to circuit-
breaker module and not reviewed here.
When adding a circuit-breaker module, the following specific general attribute must be
updated:
1. Circuit-breaker type:
− Single phase circuit-breaker, where the 3 phases can be managed independently
− Triple phase circuit-breaker, where the 3 phases can only be managed together.
− Other circuit-breaker: obsolete
(1)
obsolete
C0218ENb
FIGURE 270: SETTING CIRCUIT-BREAKER TYPE

The following tables give inputs and outputs circuit breaker’s features controlled by the
computer for triple phase and single phase circuit-breaker. For each datapoint its SCE
identification is given by a number, referenced in the following figure.
When creating a circuit breaker module implicitly or explicitly (cf. section 6.1.4 Defining a
Bay), the mandatory pre-defined DPS datapoint ‘computed switch position’ (20) is
automatically created.
To configure correctly a circuit-breaker module:
• Add the relevant datapoints, relatively to the following tables,
• do not forget to link via ‘has for feedback’ relation, the control(s) (1), (11) or (10) of the
breaker with the computed switch position (20) datapoint.
Triple phase circuit-breaker

OUTPUTS CB TYPE A OUTPUTS CB TYPE B (iv) INPUTS CB ALL TYPES
DEVICE (1) DPC control for (11) SPC control for open of (8) DPS or (19) SPS physical
CONTROL open/close 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

DEVICE (1) DPC control for (2) DPC or (11) SPC control (16) SPS or (5) DPS physical
CONTROL open/close of device for open phase A position of phase A
(3) DPC or (12) SPC control (17) SPS or (6) DPS physical
for open phase B (pulse) position of phase B
(4) DPC or (13) SPC control (18) SPS or (7) DPS physical
for 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)
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
(ii) The computed “phases not together” is equal to “false” if all phases are in the same
(iii) The computed signal is equal to the phase A status if the phase not together status is
(iv) Only the “DPC close“ is known by the other IEC61850 devices :
- For open the device they send the “DPC close” with “open” request
- For close the device they send the “DPC close” with “close” request
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(21)
(21)
FIGURE 271: AVAILABLE PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER

• The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive.
None is mandatory
• If physical position of the device is given by an SPS (19), phase not together
information (14) is mandatory
• Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}
If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then :
- in a set, if one datapoint is present for a phase, then the two others must be present
as well.
- the datapoints of the two sets (1) and (2) are mutually exclusive.
- if the datapoint "Switchgear pos." is present, but none of the three datapoints "Switch
PhA pos", "Switch PhB pos", and "Switch PhC pos" then the SPS datapoint "Ph not
together" is mandatory.
If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then :
- 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 section 5.1.8 Overview of control sequence processing.
Control sequence of synchronised circuit breakers
Refer to section 6.2 Defining a Synchrocheck function.
6.1.5.6 Defining a switchgear
This section deals with general switchgear features and available associated input and
General module features described in section 6.1.5 Defining Module are applicable to
switchgear module and not reviewed here.
When adding a switchgear module, the following specific general attribute must be updated:
1. Switchgear type:
− Busbar disconnector
− Disconnector
− Bypass disconnector
− Transfer busbar disconnector
− Earth switch
(1)
obsolete
C0219ENb
FIGURE 272: SETTING SWITCHGEAR TYPE

The following tables give inputs and outputs switchgear’s features controlled by the
computer. For each datapoint its SCE identification is given by a number, referenced in the
following figure.
To configure correctly a switchgear module:
• do not forget to link via ‘has for feedback’ relation, the control (3) of the switchgear (if it
exists) with the switch position (1) or (5) datapoint.
Switchgear
OUTPUTS TYPE A INPUTS CB ALL TYPES
DEVICE (3) DPC control for (1) DPS or (5) SPS physical
CONTROL open/close of device position of the device (1
phase) (v)
DEVICE (2) SPC (optional) control of (4) SPS (optional) device

SELECTION device selection selection position information
(HARDWARE)
(1)
(2)
(3)
(4)
(5)
FIGURE 273: AVAILABLE PRE-DEFINED DATAPOINTS FOR SWITCHGEAR

Control sequence of switchgears
Switchgear devices are managed in “direct execute mode” and in “SBO once mode”. Refer
to the generic description in section 5.1.8 Overview of control sequence processing.
6.1.5.7 Defining a transformer
This section deals with general transformer features and available associated input and
General module features described in section 6.1.5 Defining Module are applicable to
transformer module and not reviewed here.
When adding implicitly a transformer module via transformer bay creation (refer to 6.1.4
Defining a Bay), the following general attribute must be updated:
1. transformer type:
− Double wound: a double wound (or two winding transformer) is a transformer with
galvanic isolation between primary and secondary coil. Tap Changer (with
additional winding) is usually located at HV-neutral side for economic reasons.
Tapping-up (raise order) reduces primary winding and increase LV tension.
− Auto transformer: an auto transformer (or Auto-wound or single wound) is a

transformer without galvanic isolation between primary and secondary. Secondary
coil follows primary coil, (winding are serial). Tap Changer (with tap of additional
winding) is serial. Increasing tap position (raise order) acts simultaneously on
primary and secondary, it reduces transformer ratio then voltage at LV side. So for
this type of transformers the raise order must be inverted (consider as low order).
2. power value (range [1 to 300 MVA), useful for ATCC regulation
(refer to section 6.5 Defining an Automatic Voltage Regulation (AVR) built-in function)
3. impedance, whose unit is a percent of value for S=100 MVA (range [0,01 to 24,99 by
step 0,01) , useful for ATCC regulation (refer to section 6.5 Defining an Automatic
Voltage Regulation (AVR) built-in function)
(1)
(2)
(3)
FIGURE 274: SETTING TRANSFORMER TYPE

Transformer is used for coupling two voltage levels. To respect SCE data modelling
electrical partitioning, this transformer must belong to a transformer bay arbitrary put in one
of both voltage levels (generally its primary). An extra relation must be set on transformer
refining which voltage level its secondary (or primary) belongs to.
To create such a relation:
• Add the correct relation at transformer level
• Fill the relation with the relevant voltage level
(1)
FIGURE 275: COMPLETING PRIMARY/SECONDARY OF TRANSFORMER

When adding a transformer, some optional datapoints can be created at module level and
must be configured (see section 5 DEFINING DATAPOINT):
1. MCB position DPS: used for AVR function (see section 6.5 Defining an Automatic
Voltage Regulation (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 section 6.5 Defining an Automatic
Voltage Regulation (AVR) built-in function), to give Mini Circuit-Breaker position of
associated tap-changer, via SPS datapoint
(1)
(2)
FIGURE 276: TRANSFORMER OPTIONAL DATAPOINTS

When it exists, tap position of transformer is controlled by a specific built-in function ‘Tap
changer’ available at transformer module level. For details about transformer control via tap
changer function, refer to section 6.4 Defining a Tap changer built-in function.
6.2 Defining a Synchrocheck function

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

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

DEVICE (1) DPC control for (11) SPC control for open (8) DPS or (19) SPS
CONTROL 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)
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
Single phase circuit-breaker with synchrocheck

DEVICE (1) DPC control for (2) DPC or (11) SPC control (16) SPS or (5) DPS
CONTROL 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
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 (optional) control of on/off (optional) control of on/off (optional) on/off
synchrocheck synchrocheck synchrocheck information
OFF (v)
(i) The computed double signal is equal to the physical status if the phase not together
(ii) The computed “phases not together” is equal to “false” if all phases are in the same
(iii) The computed signal is equal to the phase A status if the phase not together status is
(iv) Only the “DPC close“ is known by the other IEC61850 devices :
- For open the device they send the “DPC close” with “open” request
- For close the device they send the “DPC close” with “close” request
(v) Wired SPC and SPS for external synchrocheck and system SPC and SPS for internal
synchrocheck. If is not configured the external synchrocheck module or the
synchrocheck automatism is considered always “set on”. DPC and DPS are used only
for manual synchrocheck.
(1)
(2)
(3)
(4)
(22)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(23)
(14)
(15)
(16)
(17)
(18)
(19)
(21)
(20
)
FIGURE 277: AVAILABLE PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER BREAKER

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

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

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

synchrocheck automatism in the computer.
Close control sequence can be configured with:
• Manual set on of the external synchrocheck module or internal synchrocheck

automatism.
• Automatic set on of the external synchrocheck module or internal synchrocheck

automatism.
Furthermore, waiting closes the CB by the external module the initiator of the request can:
• Cancel the request.
• Close the device by forcing request.

6.2.2 External synchrocheck behaviour

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

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

with Vline and Vbusbar TRUE if the measured voltage is above the threshold V> (param 15 and
param 17), and not(Vline) and not(Vbusbar) TRUE if the measured voltage is below the threshold
V< (param 16 and param 18). These threshold are given in % of the nominal voltage value,
updated at TMU200 board level (refer to section 4.4.2.3 Setting specific attributes of a
TMU200 board).
The selection of the voltage control is made during the configuration phase.
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 278: VLINE AND NOT(VBUSBAR) VOLTAGE CONTROL
Vbusbar
T2 0
Not(Vline)
C0228ENa
FIGURE 279: 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
Not(Vbusbar)
C0229ENa
FIGURE 280: 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 fulfilled:
• 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.
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 281: LOCKING SCHEME

Coupling scheme
In the coupling scheme, the CB can be closed only when the ∆ϕ is equal to 0.
But, in order to authorise the closing, it is first necessary that the following conditions are
fulfilled:
• 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 282: COUPLING SCHEME
Then, since a CB has a response time, it is necessary to wait a known ∆ϕ in order to

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

Synchrocheck function can be created at several levels of the electrical topology:
• Substation level, in case of the synchrocheck function is shared by several breakers,
• Bay level, in case of the synchrocheck function dedicated to a particular breaker of the
bay, or shared by two breakers in two different bays managed by the same computer.
The addition of a synchrocheck is done via the “Objects entry” window at substation or bay
For more details about bay creation, refer to section 6.1.4 Defining a Bay.
Several types of synchrochecks exist:
1. External automatic synchrocheck
2. External manual synchrocheck
3. Internal automatic synchrocheck
4. Internal manual synchrocheck
At substation level, only ‘external manual synchrocheck’ is available.
Only following typed bays allows synchrocheck creation:
• Busbar,
• Bus coupler,
• Bus section,
• Feeder,
• Transformer,
• Generic bay.
(1)
(2)
(3)
(4)
FIGURE 283: ADDING A SYNCHROCHECK AT BAY LEVEL (E.G. FOR FEEDER)

(2)
FIGURE 284: ADDING A SYNCHROCHECK AT SUBSTATION LEVEL

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

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

(E.G. FOR EXTERNAL MANUAL SYNCHROCHECK AT BAY LEVEL)
6.2.5.1 Setting default settings of internal synchrocheck
Default settings of internal synchrocheck are relevant to parameters of automation
description (see section6.2.4 Automation description of internal synchrocheck)
When adding an internal synchrocheck, the following specific attributes must be updated:
General attributes
• absence deltas test duration (ms)
• presence test duration (ms)
• presence deltas test duration (ms)
• close time of the Circuit Breaker (ms)

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

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

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

(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)
(par am 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 35) (param 34)
C0237ENb
FIGURE 287: SETTING ‘DEFAULT SETTINGS’ ATTRIBUTES OF AN INTERNAL SYNCHROCHECK

When adding an internal synchrocheck, some mandatory system datapoints are

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

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

• 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 computer, or linked to an IED
address
Substation
Ext manual CS
on/off ctrl DPC
mutually exclusive + wired
on/off ctrl SPC
on/off DPS
on/off SPS mutually exclusive
Feeder
Ext auto CS
on/off ctrl DPC
on/off ctrl SPC mutually exclusive
on/off DPS
Ext manual CS
on/off ctrl DPC mutually exclusive + wired
on/off ctrl SPC
on/off DPS
(A) automatic out of service - Yes

Int synchrocheck
on/off ctrl DPC - No
mutually exclusive
on/off ctrl SPC
on/off SPS
S0280ENa
• For an "Int synchrocheck" function, having its "automatic out of service" attribute set to
the "Yes" value, the "on/off ctrl DPC" or "on/off ctrl SPC" datapoint must be present.
• "on/off ctrl DPC" or "on/off ctrl SPC" datapoint of "Int synchrocheck" synchrocheck
must have its profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute
with SBO popup”
6.3 Defining an Auto-recloser built-in function
6.3.1 Auto-recloser behaviour
The auto–Recloser built-in function is described in section 3.1.2 of chapter C264/EN FT.
6.3.2 Creating an auto-recloser function
The addition of an auto-recloser is done via the “Objects entry” window at bay level by
Only following typed bays allows auto-recloser creation:
• Busbar,
• Bus coupler,
• Bus section,
• Feeder,
• Transformer,
• Generic bay.
FIGURE 290: ADDING AN AUTO-RECLOSER AT BAY LEVEL

Once added, auto-recloser general features must be set at SCE level:
1. Fill the relation ‘is auto-recloser of’, giving which circuit-breaker module is concerned
by the function.
2. short name and long name of the auto-recloser used for logging, alarms ...
3. functioning mode (1 ph trip) (Not used / 1P / 1P-3P / 1P-3P-3P / 1P-3P-3P-3P):
useable only for single phase circuit-breaker. Up to 4 cycles where the first one is
single phase and the others three phase.
4. functioning mode (3 ph trip) (Not used / 3P / 3P-3P / 3P-3P-3P / 3P-3P-3P-3P):
useable for single and triple phase circuit-breaker. Up to 4 cycles where all are three
phase.
5. unlocking way (Not used / Reinitialisation / Manual close / Both ways). For details
refer to previous description of ‘lock of auto-recloser’ in section 6.3.1 Auto-recloser
behaviour.
6. Fast 3 P reclose enable (No, Yes): if a synchrocheck exists for the breaker, auto-
recloser can bypass it during the 3-phases first cycle if the attribute is set to ‘Yes’.
7. 1st period monophased (range [100 ms, 5 s], step 10 ms): timer of the first single-
phase cycle.
8. 1st period triphased (range [1 s, 60 s], step 10 ms): timer of the first 3-phases cycle.
9. 2nd period triphased (range [1 s, 3600 s], step 1 s): timer of the second 3-phases
cycle.
10. 3rd period triphased (range [1 s, 3600 s], step 1 s): timer of the third 3-phases cycle.
11. 4th period triphased (range [1 s, 3600 s] step 1 s): timer of the fourth 3-phases cycle.
12. reclaim delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimc recovering timer’
previously described in ‘launch recovering timer’ of section 6.3.1 Auto-recloser
behaviour.
13. unlock delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimml recovering
timer’ previously described in ‘lock of auto-recloser’ of section 6.3.1 Auto-recloser
behaviour.
14. manual close delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimmc
recovering timer’ previously described in ‘lock of auto-recloser’ of section 6.3.1 Auto-
recloser behaviour.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
obsolete (12)
(13)
)
(14)
FIGURE 291: SETTING AUTO-RECLOSER FEATURES

• The two attributes "functioning mode (1 ph trip)" and "functioning mode (3 ph trip)"
must not be both set to "Not used" value
• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P-3P", then the following rules
must be respected :
- "1st period monophased" < "2nd period triphased"
- "1st period monophased" < "3rd period triphased"
- "1st period monophased " < "4th period triphased"
• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P", then the following rules
must be respected :
- "1st period monophased" < "3rd period triphased"
• If "functioning mode (1 ph trip)" value is set to "1P-3P", then the following rule must be
respected :
• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P-3P", then the following rules
must be respected :
- "1st period triphased" < "2nd period triphased"
- "1st period triphased" < "3rd period triphased"
- "1st period triphased" < "4th period triphased"
• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P", then the following rules
must be respected :
- "1st period triphased" < "3rd period triphased"
• If "functioning mode (3 ph trip)" value is set to "3P-3P", then the following rule must be
respected :
• If "functioning mode (1 ph trip)" value is different from "Not used", then the "circuit-
breaker type" must be set to "Single phase CircuitBreaker"
• If "functioning mode (3 ph trip)" value is set to "Not used", then the "circuit-breaker
type" must be set to "Single phase CircuitBreaker"
To assume previous described behaviour, when adding an auto-recloser, some mandatory
datapoints are automatically created at function level and must be configured (see section 5
DEFINING DATAPOINT):
1. Autorecloser flt: is a MPS datapoint, given the failure reason of auto-recloser
function. This a system datapoint whose available states are:
− State0: failure due to the synchrocheck
− State1: failure to hardware, lock of device or another running automation linked to

the device
− State2: failure due to interlocking function
− State3: no failure
2. Auto-recloser st: is a MPS datapoint which gives the status of the auto-recloser
function. This is a system datapoint whose available states are:
− State0: auto-recloser is in service, unlocked and no cycle is in progress
− State1: auto-recloser is waiting CB opening
− State2: the first single-phase cycle is in progress
− State3: the first 3-phases cycle is in progress
− State4: the second 3-phases cycle is in progress
− State5: the third 3-phases cycle is in progress
− State6: the fourth 3-phases cycle is in progress
− State7: the auto-recloser is waiting CB closing
− State8: the Reclaimc timer is launched
− State9: auto-recloser locking due to a max number of reclosing cycles
− State10: an auto-recloser locking
− State11: the reclaimml timer is launched
− State12: the reclaimmc timer is launched

3. Force trip 3 P: is a SPC, used during a 3 phase cycle as mentioned in ‘Waiting CB
opening’ in section 6.3.1 Auto-recloser behaviour
4. on/off : is a status DPS, corresponding to in / out of service status of the auto-recloser
5. Trip 3 phases: is a SPS, giving information 3-phase trip provided by a relay
(1)
(2)
(3)
(4)
(5)
FIGURE 292: AUTO-RECLOSER MANDATORY DATAPOINTS

To assume previous described behaviour, when adding an auto-recloser, some optional

datapoints can be created at function level and must be configured (see section 5 DEFINING
DATAPOINT):
1. blocking SPS: corresponds to the ‘AR_BLOCKING’ BI described in section 6.3.1
Auto-recloser behaviour
2. lock/reinit: is a SPS used to lock / unlock the auto-recloser via SPS. Corresponds to
the ‘AR_LOCK’ signal described in section 6.3.1 Auto-recloser behaviour
3. Trip PhA: is a SPS corresponding to trip status for pole A
4. Trip PhB: is a SPS corresponding to trip status for pole B
5. Trip PhC: is a SPS corresponding to trip status for pole C
6. lock/reinit SPC: Signal to lock/unlock the auto-recloser via SPC. Corresponds to the
‘AR_LOCK’ signal described in section 6.3.1 Auto-recloser behaviour
7. on/off ctrl DPC: to control in/out of service of the auto-recloser via DPC
8. on/off ctrl DPS: to control in/out of service of the auto-recloser via DPS
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 293: AUTO-RECLOSER OPTIONAL DATAPOINTS

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

6.4 Defining a Tap changer built-in function

6.4.1 Tap changer behaviour
The control sequence of a transformer is described in section 6.5 of chapter C264/EN FT.
The control of a transformer is done via tap changer built-in function and can be performed in
the three modes “Direct Execute”, ”SBO once” and “SBO many mode” (refer to section 5.1.8
Overview of control sequence processing).
TCIP feature:
The TCIP input information is used to confirm the right execution of the low/raise execution.
When adding a TCIP at tap changer level, the two configurable delays must be set at TCIP
datapoint level for the correct TCIP management:
1. reset confirmation delay (range [0 s, 120 s], step 100 ms]: this delay corresponds to
time-out TR given in section 5.1.2.1 Persistence filtering of chapter C264/EN FT.
2. set confirmation delay (range [0 s, 120 s], step 100 ms]: this delay corresponds to
time-out TS given in section 5.1.2.1 Persistence filtering of chapter C264/EN FT.
3. start confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must
appear before the time-out of this delay
4. stop confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must
disappear before the time-out of this delay
(1)
(2)
(3)
(4)
FIGURE 295: SETTING TCIP GENERAL ATTRIBUTES OF A TCIP

TPI feature:
Because the TCIP input information is not always configured, the tap control is performed by
using only the Tap Position Indication (TPI) value to verify the right execution of the request.
The TPI value must change in the given delay.
Control of a transformer with TCIP
This functionality is described in section 6.5.2.1 of chapter C264/EN FT.
Control of a transformer without TCIP
Suppression, Forcing or Substitution of the TPI

6.4.2 Creating a tap changer built-in function
Tap changer is considered as a function because it verifies maximal and minimal useable
positions of tap position indicator. It is like a sub-module of transformer module and owns the
tap position indicator and optional controls (Raise/Lower, Goto Min/Max).
To create a tap-changer built-in function, add it from object entry available at transformer
module level (1).
(1)
FIGURE 296: ADDING A TAP CHANGER BUILT-IN FUNCTION TO TRANSFORMER

When adding a tap changer function, the following general attributes must be updated:
1. short name and long name of the tap changer used for logging, alarms ...
2. minimal usable position (range [1, 64], step 1).
3. maximal usable position (range [1, 64], step 1): must be greater than attribute (2).
4. execution timeout (range [0, 60 s], step 100 ms): It is the maximum delay in which
tap position must have changed relatively to the current tap control in progress. If
delay expired bad acknowledgement is sent for tap control.
(1)
(2)
(3)
(4)
obsolete
C0244ENb
FIGURE 297: SETTING TAP CHANGER ATTRIBUTES

When adding a tap changer function, the mandatory datapoint ‘Tap position indicator’ (TPI)
is automatically created at function level (8).
The following table gives inputs and outputs tap changer’s features controlled by the
computer. For each datapoint its SCE identification is given by a number, referenced in the
following figure.
To configure correctly the tap changer of a transformer module:
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 added at transformer module level and configured as
feedback of SPC transformer selection (4).
1. Goto min/max DPC: this datapoint is not managed by the tap changer built-in
function. If it is needed an ISAGRAPH automation has to be used.
2. Raise/lower DPC: this datapoint is managed by the tap changer built-in function.
3. MCB open SPC: this datapoint is managed by the tap changer built-in function.
4. TAP Select SPC: this datapoint is managed by the tap changer built-in function
5. Higher position: this SPS is not taken into account by the tap changer built-in
6. Lower position: this SPS is not taken into account by the tap changer built-in
7. Tap in progress: this SPS is taken into account by the tap changer built-in function.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 298: AVAILABLE PRE-DEFINED DATAPOINTS FOR TAP CHANGER

• "Raise/lower DPC" datapoint must have its profile attribute “SBO mode” set to "SBO
Operate Many"
6.5 Defining an Automatic Voltage Regulation (AVR) built-in function

6.5.1 AVR behaviour
The AVR built-in function is described in section 7.1.4 of chapter C264/EN FT.
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-sections, required datapoints for AVR function are prefixed with an
identifier, refered in section 6.5.1.1 of chapter C264/EN FT.
• 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 ATCC function needs at substation level
The entry point of ATCC configuration is done at substation level.
This is done via the “Objects entry” window at substation level by clicking on mouse’s right
button.
(1)
FIGURE 299: ADDING AN AVR FUNCTION AT SUBSTATION LEVEL

Once added, ATCC features must be set at SCE level:
1. Fill the relation ‘is managed by’, giving which computer runs and supervises AVR
function at substation level.
2. short name and long name of the AVR used for logging, alarms ...
‘General’ attributes:
‘calculation’ attributes
3. calculation period: corresponds to parameter “period of AVR calculation” listed in
section 7.1.4.7 (List of configurable parameters) of chapter C264/EN FT.
4. calculation mode: corresponds to parameter “calculation mode” listed in section
7.1.4.7 of chapter C264/EN FT.
‘Homing’ attributes
5. active homing: corresponds to parameter “Homing ON/OFF” listed in section 7.1.4.7
(List of configurable parameters) of chapter C264/EN FT.
6. homing deadband: corresponds to parameter “percentage of the Homing deadband”
listed in section 7.1.4.7 of chapter C264/EN FT.
‘ATCC mode changing’ attributes
7. mode on group interconnection: corresponds to parameter “mode group
interconnexion” listed in section 7.1.4.7 of chapter C264/EN FT.
8. mode on bay in local: corresponds to parameter “mode if bay in local“listed in section
‘Compounding’ attributes
9. compounding method: corresponds to parameter “compounding method” listed in
section 7.1.4.7 of chapter C264/EN FT.
Delays’ attributes:
‘Nominal’ attributes
10. fixed initial tap delay: corresponds to parameter “initial tap time delay fixed/or not”
11. initial tap delay (in ms): corresponds to parameter “initial tap time delay:T1” listed in
12. inter tap delay (in ms): corresponds to parameter “inter tap time delay:T2 listed in
‘Homing’ attributes
13. homing initial tap delay (in ms): corresponds to parameter “Initial tap time delay:T3”
14. homing inter tap delay (in ms): corresponds to parameter “Inter tap time delay:T4”
listed in section 7.1.4.7 of chapter C264/EN FT
‘Hunting’ attributes
15. hunting window (in ms): corresponds to parameter “Hunting window : T5” listed in
16. opposite max tap changes: corresponds to parameter “Maximal number of
successive taps in opposite direction for hunting (default value: 4 )” listed in section
7.1.4.7 of chapter C264/EN FT
‘Inhibition’ attributes
‘Inhibition conditions’ attributes

17. max voltage difference (ratio): corresponds to parameter “Percentage of accepted
difference between secondary voltages for transformers in the same group. (default
value: +2%)” listed in section 7.1.4.7 of chapter C264/EN FT
18. tolerable nominal under voltage (ratio): corresponds to parameter “Under-voltage:
percentage of nominal voltage under which AVR or Homing is inhibited (default value:
80%)” listed in section 7.1.4.7 of chapter C264/EN FT
19. tolerable nominal over voltage (ratio): corresponds to parameter “Over-voltage:
percentage of nominal voltage over which AVR or Homing is inhibited (default value:
120%)” listed in section 7.1.4.7 of chapter C264/EN FT.
‘Busbar voltage’ attributes
Coefficients for busbar voltage calculation attributes: correspond to parameter “Coefficients
for 1, 2, 3 and 4 transformers (default value: 1)” listed in section 7.1.4.7 of chapter C264/EN
FT
20. voltage coefficient for 1 transfo
21. voltage coefficient for 2 transfos
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 300: SETTING GENERAL FEATURES OF AN AVR

(10)
(11)
(12)
(13)
(14)
(15)
(16)
FIGURE 301: SETTING ‘DELAYS’ ATTRIBUTES OF AN AVR
(17)
(18)
(19)
FIGURE 302: SETTING ‘INHIBITION’ ATTRIBUTES OF AN AVR
(20)
(21)
(22)
(23)
FIGURE 303: SETTING BUSBAR VOLTAGE ATTRIBUTES OF AN AVR

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

6.5.2.2 Defining ATCC 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).
Then an extra ‘ATCC’ tab-pane appears with the following attributes to update:
‘voltage targets’ attributes
2. voltage target by default: corresponds to (param 40) listed in section 7.1.4.7 of
chapter C264/EN FT.
3. voltage target 1: corresponds to parameter “Target voltage 1” listed in section 7.1.4.7
of chapter C264/EN FT.
‘regulation’ attributes
8. voltage target ramping rate (kV/mn): corresponds to parameter “Target voltage
ramping rate” listed in section 7.1.4.7 of chapter C264/EN FT.
9. max tap change rate (kV/min): corresponds to parameter “Max voltage change rate”
10. voltage deadband to end tapping: corresponds to parameter “Voltage deadband1”
11. voltage deadband to initiate tapping: corresponds to parameter “Voltage
deadband2” listed in section 7.1.4.7 of chapter C264/EN FT.
When a voltage level is concerned by an AVR function, do not forget to set correctly its
attribute ‘nominal value (kV)’ (refer to section 6.1.3 Defining a Voltage level). It is used for
transformer nominal ratio computation.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
FIGURE 305: SETTING AVR FUNCTION ATTRIBUTES AT VOLTAGE LEVEL

6.5.2.3 Defining ATCC 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 section 6.1.4 Defining a Bay.
This is done via the “Objects entry” window at busbar level by clicking on mouse’s right
button.
(1)
FIGURE 306: ADDING AVR FUNCTION NEEDS AT BUSBAR LEVEL

Once added, AVR busbar features must be set at SCE level:
1. setpoint ponderation: corresponds to parameter “SetPoint value” listed in section
2. priority: corresponds to parameter “Priority“listed in section 7.1.4.7 of chapter
C264/EN FT.
‘line drop compensation (if setpoint adjustement)’ attributes
3. resistive coefficient: corresponds to parameter “Resistive multiplier” listed in section
4. reactive coefficient: corresponds to parameter “Reactive multiplier” listed in section
‘line drop compensation (if voltage adjustement)’ attributes
5. transfo-busbar resistive coefficient: corresponds to parameter “Resistive multiplier“
6. transfo-busbar reactive coefficient: corresponds to parameter “Reactive multiplier“
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 307: SETTING GENERAL BUSBAR FEATURES OF AN AVR

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

C0348ENa
FIGURE 308: MANDATORY DATAPOINTS FOR AVR AT BUSBAR LEVEL

6.5.2.4 Defining ATCC function needs at transformer level

For details about transformer bay (and subsequent transformer module) creation, refer to
sections 6.1.4 Defining a Bay.
For each transformer concerned by an AVR function, extra AVR configuration must be done
at several levels:
• Set properly the following features for transformer module:
− ‘Transformer type’ attribute: corresponds to parameter “AVR transformer type“

− ‘Power value’ attribute: (range [1, 300 MVA]): corresponds to parameter “AVR
transformer rating” listed in section 7.1.4.7 of chapter C264/EN FT.
− ‘Impedance’ attribute, whose unit is a percent of value for S=100 MVA (range
[0,01 to 24,99 by step 0,01): corresponds to parameter “AVR transformer
impedance on nominal tap on 100 MVA base” listed in section 7.1.4.7 of chapter
C264/EN FT.
− MCB position SPS or DPS is mandatory
• Add and configure a Tap-changer built-in function for the transformer module (refer to
section 6.4 Defining a Tap changer built-in function), with the following features:
− Raise/Lower DPC is mandatory
− Tap in progress SPS is mandatory
− MCB open SPC is mandatory
• Add and configure an ‘ATCC fct needs’ object for transformer, via the “Objects entry”
window at transformer module level by clicking on mouse’s right button (1):
(1)
FIGURE 309: ADDING AVR FUNCTION NEEDS AT TRANSFORMER LEVEL

Once added, the features of AVR function needs for transformer must be set at SCE level:
‘Tpi range’ attributes
1. up range: corresponds to parameter “AVR tapping range – upper value” listed in
2. down range: corresponds to parameter “AVR tapping range – lower value” listed in
‘Inhibition conditions’ attributes:
3. Overcurrent ratio: corresponds to parameter ”Overcurrent setting” listed in section
(1)
(2)
(3)
FIGURE 310: SETTING GENERAL TRANSFORMER FEATURES OF AN AVR

When adding AVR function needs at transformer level, the following mandatory datapoints
are automatically created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Trf 1) ATCC on/off
(DPT_Trf 2) ATCC homing
(DPT_Trf 3) ATCC hunting
(DPT_Trf 4) TAP bad TCIP
(DPT_Trf 5) TAP long TCIP
(DPT_Trf 6) TAP invalid
(DPT_Trf 7) Run away
(DPT_Trf 8) ATCC disc eqpt
(DPT_Trf 9) ATCC local bay
(DPT_Trf 10) MCB trip
(DPT_Trf 11) ATCC overcurrent
(DPT_Trf 12) ATCC overvoltage
(DPT_Trf 13) ATCC low-voltage
(DPT_Trf 14) ATCC inv voltage
(DPT_Trf 15) Second. voltage
(DPT_Trf 16) Second. current
(DPT_Trf 17) Second. active P
(DPT_Trf 18) Second. react. Q
(DPT_Trf 1) (DPT_Trf 2)
C0349ENa
FIGURE 311: MANDATORY DATAPOINTS FOR AVR AT TRANSFORMER LEVEL

6.5.2.5 Defining an 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 three 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 312: IDENTIFYING NODES IN ELECTRICAL DIAGRAM (E.G.)

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 references must be filled
(3),
• “Transformer” module, where at least two node references must be filled, and a extra
one in case of neutral compensation (4),
• “Capacitor” 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 313: SETTING BUSBAR NODE REFERENCE (AVR FUNCTION)

(2)
FIGURE 314: SETTING EXTERNAL LINE NODE REFERENCE (AVR FUNCTION)
(3)
FIGURE 315: SETTING CIRCUIT-BREAKER NODE REFERENCES (AVR FUNCTION)
(4)
FIGURE 316: SETTING TRANSFORMER NODE REFERENCES (AVR FUNCTION)
(5)
FIGURE 317: SETTING CAPACITOR NODE REFERENCES (AVR FUNCTION)

6.6 Defining an electrical regulation by user function

PACiS allows the user to configure specific control sequences or automations (e.g. switching
sequences, busbar transfer, load shedding, GIS-pressure supervision, etc …) during the
configuration phase.
To do that, there are two main solutions:
• Using ISaGRAF workbench for slow automations, where the execution of the
automation is cyclic, based on a cycle that can not be less than 50 ms.
• Using extended logical function modelling (boolean, timer, bistable functions) via FBD
workbench, where the execution is event-driven.
User function can be put at any level of the electrical topology except Site. Moreover, slow
automation is unavailable at module level. User function must always specify on which
computer it runs.
Extra solutions for simpler needs exist at configuration level (they could be seen as
restriction of particular FBD functions):
• Group modelling: SPS production based on a pre-defined boolean function working on

a set of datapoint.
• xPS-xPC association: on a particular state of xPS, ability to control a given xPC.
• SPS-DPS association: DPS production based on the synthesis of 2 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

6.6.1.1 Creating a FBD fast automation (header definition)
The addition of a FBD fast automation is done via the “Objects entry” window at any level of
the electrical topology (except Site) by clicking on mouse’s right button.
For more details about electrical topology creation, refer to section 6.1 Defining an electrical
topology.
FIGURE 318: 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 computer PLC will manage the automation. This
relation is automatically filled by SCE if FBD automation is located under a bay whose
computer manager has ever been entered (for details about computer manager of a
bay refer to section 6.1.4 Defining a Bay).
2. short name and long name of the fast automation used for internal SCE
identification.
(1)
(2)
FIGURE 319: SETTING FBD FAST AUTOMATION FEATURES

6.6.1.2 Creating FBD input plug (header definition)
The addition of a FBD input plug is done via the “Objects entry” window at the FBD
automation level by clicking on mouse’s right button.
FIGURE 320: ADDING A FBD INPUT PLUG

Once added, FBD input plug features must be set at SCE level:
1. short name and long name of the fast automation used for identification in FDB
editor
(1)
FIGURE 321: SETTING GENERAL FBD INPUT ATTRIBUTES

6.6.1.3 Creating FBD output plug (header definition)
The addition of a FBD output plug is done via the “Objects entry” window at the FBD
FIGURE 322: ADDING A FBD OUTPUT PLUG

Once added, FBD output plug features must be set at SCE level:
1. short name and long name: used for identification in FDB editor
(1)
FIGURE 323: 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 click).
(1)
FIGURE 324: LAUNCHING FBD EDITOR

Once launched, FBD editor allows diagram edition of the automation. For details about FBD
user manual refer to <the PACiS-SCE Documentation>
FIGURE 325: 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 326: LINKING A FBD INPUT TO A DATAPOINT

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)
(1)
FIGURE 327: LINKING A FBD OUTPUT TO A DATAPOINT

Several datapoints can be assigned to the same FBD output.
• For one "FBD input" plug, only one relation is allowed.
• For one "FBD output" plug:

- the count of relations towards DPC or SPC datapoints must be ≤ 4
- the count of relations towards SPS datapoints must be ≤ 4
• A "DPC" or "SPC" datapoint can be linked to an Output plug of a FBD Automation

through the relation "controls DPC" or "controls SPC". These relations are not
compatible with the following ones:
- relations defining the Control Source, except the "…wired on" relation(s)
- relation "has for 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".
6.6.2 Defining an ISaGRAF slow automation

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"
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 shedding automation can have a
control to put it in/out of service and a relevant status.
They also reference via links datapoints located in system or electrical topologies. There are
two kinds of link:
• ‘client’ link, that means that the slow automation uses the datapoint that is acquired or
managed outside the ISaGRAF automation. For instance, the load shedding
automation can be client of some ‘circuit-breaker status’ input datapoints and some
‘circuit-breaker control’ output datapoints.
• ‘server’ link, that means that the slow automation produces or manages the datapoint.
For instance, a slow automation can be used to produce the sum of feeder
measurements. This sum is also a measurement located at voltage level for instance.
To define a slow automation, 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.

6.6.2.1 Creating an ISaGRAF slow automation (header definition)

The addition of an ISaGRAF slow automation is done via the “Objects entry” window at any
level of the electrical topology (except Site and module) by clicking on mouse’s right button.
topology.
FIGURE 328: ADDING AN ISAGRAF SLOW AUTOMATION 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 computer PLC will manage the automation. This
relation is automatically filled by SCE if slow automation is located under a bay whose
computer manager has ever been entered (for details about computer manager of a
bay refer to section 6.1.4 Defining a Bay)
2. short name and long name of the slow automation used for logging and alarm
(1)
(2)
FIGURE 329: SETTING ISAGRAF SLOW AUTOMATION FEATURES

6.6.2.2 Adding specific datapoints to slow automation (interface definition)

The addition of a slow automation datapoint is done via the “Objects entry” window at slow
DATAPOINT.
FIGURE 330: ADDING DATAPOINTS TO SLOW AUTOMATION

Slow automation datapoint is integrally produced or managed by the slow automation and
subsequently by ISaGRAF. It can not be linked to another acquisition or control source and
the ISaGRAF project must update/run its value changes or controls.
Slow automation input datapoints are stored in a non-volatile memory at computer level to
restart on their last known values in case of computer reboot.
6.6.2.3 Creating ISaGRAF client link (interface definition)

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

6.6.2.4 Linking a datapoint to an ISAGRAF client link

To link a datapoint to an ISAGRAF client link the relation 'is client of' must be defined. For
that double click this relation (1). The Relation Link Editor is then displayed. By expanding
the tree view all the available SPS datapoints are listed. Click the one you want to link (2)
then click the Ok button. (In the example given hereafter the link has be done with the
VoltageLevel SPS datapoint). The relation is then displayed as 'defined' (3).
(1)
(2)
(3)
FIGURE 332
6.6.2.5 Defining Isagraf IO prefix for an input

By clicking this 'is client of' relation the associated attributes window is displayed. Only the
'Isagraf IO prefix' attribute (4) can be modified by the user. This attribute defines the prefix
of the identifier of this datapoint when used in ISAGRAF workbench as an input signal of this
automation. It is built by concanetating the prefix, an underscore (if the prefix exists) and the
input IO reference automatically given by the SCE: In the example given hereafter the
identifier of this link will be: MY_INPUT_PREFIX_in_2
(4)
FIGURE 333: DEFINING ISAGRAF IO PREFIX FOR AN INPUT

• The first character must be a letter
• The following characters must be either a letter in upper case, either a digit or an
underscore.
• The maximum length is 80 characters

6.6.2.6 Creating ISaGRAF server link (interface definition)
The addition of an ISaGRAF server is done via the “Objects entry” window at the slow
automation level by clicking on mouse’s right button and adding a ‘manages’ relation.
Choose the correct relation depending on datapoint kind that will be managed.
FIGURE 334: ADDING AN ISAGRAF CLIENT LINK

6.6.2.7 Linking a datapoint to an ISAGRAF server link

To link a datapoint to an ISAGRAF server link the relation 'manages' must be defined. For
that double click this relation (1). The Relation Link Editor is then displayed. By expanding
the tree view all the available DPS datapoints are listed. Click the one you want to link (2)
then click the Ok button. (In the example given hereafter the link has be done with the
Substation DPS datapoint).
The relation is then displayed as 'defined' (3).
(1)
(2)
(3)
FIGURE 335: LINKING A DATAPOINT TO AN ISAGRAF SERVER LINK

6.6.2.8 Defining Isagraf IO prefix for an output

By clicking this manages' relation the associated attributes window is displayed. Only the
'Isagraf IO prefix' attribute (4) can be modified by the user. This attribute defines the prefix
of the identifier of this datapoint when used in ISAGRAF workbench as an output signal of
this automation. It is built by concanetating the prefix, an underscore (if the prefix exists) and
the output IO reference automatically given by the SCE: In the example given hereafter the
identifier of this link will be: My_Output_Prefix_out_1
(4)
FIGURE 336: DEFINING ISAGRAF IO PREFIX FOR AN OUTPUT

• The following characters must be either a letter in upper case, either a digit or an
underscore.
• The maximum length is 80 characters

6.6.2.9 Using ISaGRAF editor (body definition)
The launching of the ISaGRAF editor is done at slow automation level via its contextual
menu (right click).
(1)
FIGURE 337: LAUNCHING ISAGRAF EDITOR

Once launched, ISaGRAF editor allows diagram edition of the automation. For details about
ISaGRAF workbench and SCE datapoint coupling, refer to section 8 Annex A: Coupling SCE
data model and ISaGRAF.
FIGURE 338: USING ISAGRAF EDITOR

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 belong to bays or modules. The computer that manages the bay (of
eventually the bay of the module) always computes it. Its composition description is done via
linking it to SPS, DPS, or Group SPS.
A group SPS can be seen as a particular fast automation reduced to one boolean function
with one implicit output plug (the group SPS itself) and input plugs corresponding to each
component of the group.
The addition of a group SPS is done via the “Objects entry” window at bay or module level of
the electrical topology by clicking on mouse’s right button.
topology.
FIGURE 339: ADDING A GROUP SPS (E.G. FOR FEEDER BAY LEVEL)
Once added, Group SPS features must be set at SCE level, as SPS datapoint. For details
about SPS datapoint configuration, refer to section 5.1.2 Defining a 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.
(1)
FIGURE 340: SETTING ‘GROUP TYPE’ ATTRIBUTE OF A GROUP SPS

To assign a component to a group (SPS, DPS or group):
• Add the relation ‘contains the <XXX>’ (1) at Group SPS level, where XXX corresponds
to the datapoint kind (SPS or DPS)
(1)
FIGURE 341: ADDING A COMPONENT TO A GROUP

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 342: CONTROLLING XPC THROUGH XPS (E.G.)

6.6.5 Producing a DPS from two 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 two SPS:
• Create the three datapoints and configure them (see section 5 DEFINING
DATAPOINT)
• At the DPS level, add the relations ‘has open state given by’ (1) and ‘has closed state
given by’ (2)
• Fill the two relations with the previously created SPS datapoint
(1)
(2)
FIGURE 343: 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

The addition of an interlock SPS is done via the “Objects entry” window at SPC/DPC
datapoint level by clicking on mouse’s right button (1).
topology.
(1)
FIGURE 344: ADDING AN INTERLOCK SPS (E.G. FOR MODULE DPC LEVEL)
Once added, interlock SPS features must be set at SCE level, as SPS datapoint. For details
about SPS datapoint configuration, refer to section 5.1.2 Defining SPS datapoint.
To define interlocking equation for an interlock SPS:
• Add at interlock SPS level, a FBD interlock object (1)
• Configure this FBD interlock (refer to section 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.
(1)
FIGURE 345: DEFINING INTERLOCKING EQUATION FOR AN INTERLOCK SPS

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 346: DEFINING AN AUTOMATIC/MANUAL DEPENDENCY (E.G.)

• For each "DPC", "SPC" or "Setpoint" datapoint, 2 relations "has for AutoManu
dependency" are available, but they are mutually exclusive.
6.7 Defining a Fast Load shedding application

6.7.1 General Architecture
GTW OI
Standard PACiS system - Network 1

C264
C264
client
C264 Reports
IEC/IEC GTW
Reports
server
,
xPS for topology GOOSE
T101 GTW
measurements OI-FLS
C264-M2
C264-M1
Dedicated PACiS for FLS - Network 2
C264-F1
C264-F2 C264-F47 C264-F48
C0427ENa
The 2 networks are fully independent; IEC61850/IEC61850 PC Gateway do not support IP

routing function.
The IEC/IEC Gateway can be redundant. It is used to transfer the topology information (i.e.
the device positions) and all necessary measurements useful for the FLS from the network 1
to the network 2.
No information is sent from network 2 to network 1 through this gateway. If needed, an
additional T101 gateway can be added to network 2 to send information from network 2 to
network 1.
The C264-M is (or can be) a redundant C264. It supports the ISAGRAF automation which
allows defining FLS preselections and also automations (ISAGRAF and/or PSL) which allow
to test / simulate the FLS.
It is client from the IEC/IEC gateway and receives the topology (device positions) and
measurements from it through reports.
C264-M is server of the OI-FLS and is used to re-transmits the datapoints coming from
C264-Fi to OI-FLS uses datapoint associations mechanisms. The FLS preselection are
transmitted to C264-Fi using the LSP datapoints, transmitted by GOOSE. C264-M is
dedicated to FLS.
The various C264-Fi manages the feeder and the breaker trip.
In order to secure performance time of breaker trip, C264-Fi are not servers of the OI-FLS
and C264-M. They only manage the PSL which allows to trip the feeder regarding the cause
and the preselection (LSP). They are dedicated to the acquisition of datapoints used for the
Fast Load Shedding function (only FLS triggers as input and breaker trip as output).
The C264-Fi can be redundant. To avoid time performance limitation, the client/server
mechanism used in case of C264 redundancy (to exchange the FailSt information) will be
replaced by a GOOSE transmission of this information.
The OI-FLS is used to display the single line diagram, to perform the test control, to define
the priority. It is not equipped with other functions (alarms, SOE, historian, trend, …).
6.7.2 FLS Data Flow summary
C264 Mx
is_connected_to TOPOLOGY
(node, node 2 Module
state)
OI-FLS IEC/IEC GTW

ISAGRAF
and PSL
LSP - 1 per CB
Priority Setpoints (GOOSE)
(SP) - 1 per DJ
LSP - 1 per CB
(Report) Trigger test control xPS for topology and
(xPC) - 10 max Trigger - 16 max
(GOOSE) measurement (report)
Trigger test fe edback

(report) - 1 per DJ C264 F48 (max)
C264 F1
PSL PSL
(per CB) (per CB)
Control DJ trigger X Control DJ trigger Y

(= 12) (= 12)
C0428ENa
6.7.3 Priority Setpoints

Priority are standard setpoints. They have to be associated to a measurement feedback to
insure the value saving in the non-volatile memory.
6.7.4 Load Shedding Preselection (LSP)
LSP is a 16 bit word in which several bit can be simultaneously set. This dedicated PACiS
object is mapped on an IEC61850 BSTR16 type.
The LSP can be created under a module object or a breaker object.
The LSP is a sub-type of the MPS object. The SCE attributes of this object are:
• Short name
• Long name
• Meaning: fixed to “load shedding preselection”
• Spare
• Relation to profile – The profile is only used to define the printing / archiving status at
OI level (alarms, interlocking values are not used).
No wiring, no SCADA address can be associated to this object.
A LSP cannot be forced, suppressed or substituted (FSS).
The LSP are not saved in C264-Mx non-volatile memory.
In case of C264-Mx re-initialisation (or, in case of C264-M redundancy, when the Standby
becomes Active), the LSP are initialized to 0.
The owner of the LSP is the C264-Mx (and its redundant if exist) : it is the GOOSE publisher
and the server of the LSP. So this computer must be clearly identified in the configuration : a
relation “has for LSP manager” is defined at Site level to define this computer. Dedicated
GOOSE message is used to transmit LSP (i.e. measurement GOOSE / status GOOSE are
not used): in this GOOSE, only the LSP status is transmitted : the quality and time-stamp are
not transmitted.
6.7.5 Graphical animation with LSP

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

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

database. The PSL limitations are applicable on this operator.
6.7.7 Use of LSP in ISAGRAF scheme

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

The triggers are standard xPS. As soon as they will be used in a PSL, they will be
automatically GOOSE-defined using the SBUS automatic addressing.
6.7.9 Topology calculation
An ISAGRAF function allows to define if 2 devices are connected:
is_connected_to (node1, node2, state) with state = connected, unconnected, uncertain, and
node1 / node2 the reference of the nodes of the 2 devices.
The FORCED <state> and SUBSTITUTED <state> status are taken into account as the
normal <state> of the datapoint in the topology calculation. The SUPPRESSED status is
taken into account as the UNKNOWN status.
Two nodes are connected if it exists at least one chain of devices between the 2 nodes
which are closed, forced closed or substituted closed. Two nodes are unconnected if all
chains of devices between the 2 nodes are open, forced open or substituted open. In all
others cases, the status between two nodes is uncertain.
7. DEFINING COMPUTER LOCAL HMI

All kinds of computers (except C364), can have a GHU200 board for led managing and
possible local bay mimic panel animations in case of complete GHU200 board (refer to
section 4.4.2.2 Setting specific features of a GHU200 board),.
7.1 Defining a bitmap table
To define computer bay mimics, bitmaps are used. Their definition is located at graphic root
of the data modelling.
At computer bay mimic definition level, objects only reference these bitmaps. So it is an
easier way to propagate a bitmap change for instance to all objects that reference it.
At SCE level, bitmap object definition is extended to embed animation: up to 5 elementary
static bitmaps can be grouped in a bitmap object:
• one (mandatory) for default representation
• one for ‘open’ (or reset) representation
• one for ‘closed’ (or set) representation
• one for ‘open withdrawn’ representation
• one for ‘closed withdrawn’ representation

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

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

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

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

Via a complete GHU200 board (refer to section 4.4.2.2 Setting specific features of a
GHU200 board), each computer with local HMI references a workspace that groups its bay
mimic definitions. Computer workspaces can not be shared by several computers because
mimics are local to bays managed by a specific computer.
Up to 24 bay mimics can be put in a computer workspace, and up to 2 mimics can be linked
to the same bay.
Usual labels are used by computer local HMI (LHMI). They are located for all computers
LHMI in one object grouping all translatable labels, located in “computer workspaces” folder
in Graphic topology.
7.2.1 Settings LHMI labels
To modify a usual label used at computer LHMI level, just select and update the
corresponding attribute at LHMI labels object.
FIGURE 350: SETTINGS LHMI LABELS

7.2.2 Creating a workspace
The addition of a workspace is done via the “Objects entry” window at graphic level by
FIGURE 351: ADDING A COMPUTER WORKSPACE

Once added, 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 section 4.4.2.2 Setting
specific features of a GHU200 board).
• Setting the short and long name (1) attributes of the workspace used for internal SCE
identification,
• Setting ‘local/remote password usage’ (No / Yes) attribute (2), to precise if password is
required to set Local/remote for bays managed by the computer.
(1)
(2)
FIGURE 352: SETTING COMPUTER WORKSPACE ATTRIBUTES

7.3 Defining a computer bay mimic
7.3.1 Creating a computer bay mimic
The addition of a computer bay mimic is done via the “Objects entry” window at computer
workspace level by clicking on mouse’s right button.
FIGURE 353: ADDING A COMPUTER BAY MIMIC

Once added, bay mimic general attributes must be set at SCE level:
1. short name of the bay mimic used for internal SCE identification.
2. bargraph representation ( none / Horizontal / Vertical): this attributes defines which
representation is used for bargraph associated to a MV datapoint assigned to a bay
mimic (refer to section 7.3.4 Assigning MV to bay mimic).
3. module name display (No / Yes) this attribute defines if module short names are
displayed at mimic level when a module is represented on bay mimic (refer to section
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation,
transformer representation).
4. Fill the relation ‘represents’, giving which bay is represented by the mimic (for details
about bay refer to section 6.1.4 Defining a Bay).
5. If necessary, set the attribute ‘mimic rank’ of the ‘represents’ relation to correct value.
This attribute is used when 2 mimics are configured to display an entire bay: as bay is
split in 2 representations, the ‘mimic rank’ attribute gives their display rank at computer
LHMI level (1 or 2).
(1)
(2)
(3)
(4)
(5)
FIGURE 354: SETTING BAY MIMIC FEATURES

When adding a bay mimic at workspace level, its core structure (canvas) is automatically
created and displayed at SCE level, via bay mimic editor and in SCE tree browser. Its core
structure consists of:
1. Reserved zone for bay name display
2. Reserved zone for bay local/remote display ((2’) in tree browser)
3. Reserved zone for ‘interlocking bypass in progress’ information ((3’) in tree browser)
4. Reserved zone for ‘synchrocheck bypass in progress’ information ((4’) in tree browser)
5. Configurable zone for graphical representation of the bay (static and dynamic parts)
6. Reserved zone for message
(1)
(2)
(3)
(4)
(5)
(3’)
(2’)
(4’)
FIGURE 355: CORE STRUCTURE OF BAY MIMIC

For more details about computer LCD usage, refer to document User Interface (coded HI for
Human Interface) of MiCOM C264 documentation binders.
The configurable zone of a bay mimic can be split in two parts:
• A static part with no real-time animation
• A dynamic part with real-time animated representations.

• The computer managing a bay represented by a "Bay mimic" must be the same as the
one linked to the "Comp. workspace" (computer workspace) of this "Bay mimic".
• A bay can be represented by 0, 1 or 2 "Bay mimic". Each "represents" relation has an

attribute "mimic rank for the set of bay mimic". In the case of 2 relations, each attribute
value must be unique.
• For a Computer, the maximum count of managed bays (relation "is managed by")
which are linked to a "Bay mimic" (relation "represents"), is 12.
• Limits of the count of symbols:
Graphic
Comp. workspace
Bay mimic max = 24 / Comp. workspace
LHMI Transformer max = 9 / Bay mimic
LHMI Gen module
LHMI bitmap max = 5 / Bay mimic
LHMI line max = 30 / Comp. workspace max = 18 / Bay mimic
LHMI text max = 5 / Bay mimic (1 is reserved for the Bay name) + 1 reserved
… for the Bay name
S0285ENa
7.3.2 Defining static part: line, bitmap, fixed text

The static part of a computer bay mimic is described via graphical basic shapes:
• LHMI line: horizontal or vertical line with configurable thickness and length
• LHMI bitmap: bitmap that references a bitmap object in the bitmap table (see 7.1
Defining a bitmap) where default representation is only taken into account
• Fixed text: multi-lingual fixed text

Once added, these elements automatically appear in the window of the bay mimic editor at
SCE level.
• The coordinates (x, y) of a symbol must not be located outside the mimic area.
7.3.2.1 Adding a line
The addition of a line in bay mimic is done via the “Objects entry” window at bay mimic level
by clicking on mouse’s right button.
FIGURE 356: ADDING A LINE IN COMPUTER BAY MIMIC

Once added, line attributes must be set at SCE level:

1. short name of the line used for internal SCE identification
2. x ( range [0, 127 pixels], step 1 pixel): abscissa
3. y ( range [0, 127 pixels], step 1 pixel): ordinate
4. length ( range [1 pixel, 127 pixels], step 1 pixel)
5. orientation ( Horizontal / Vertical)
6. thickness ( range [1 pixel, 8 pixels], step 1 pixel)
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 357: SETTING LINE ATTRIBUTES

Abscissa, ordinate, length and thickness of a LHMI line can be directly adjusted with the
mouse in bay mimic editor (for detail, refer to SCE user’s manual)
7.3.2.2 Adding a bitmap
The addition of a bitmap in bay mimic is done via the “Objects entry” window at bay mimic
FIGURE 358: ADDING A BITMAP IN COMPUTER BAY MIMIC

Once added, bitmap attributes must be set at SCE level:

1. short name of the line used for internal SCE identification
4. bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1
Defining a bitmap table)
(1)
(2)
(3)
(4)

Abscissa and ordinate of a bitmap can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE user’s manual)
• The link from an element to its bitmap is defined with the attribute "bitmap reference".
The value of this attribute must refer to an existing bitmap in the "Bitmap table".
7.3.2.3 Adding a fixed text
The addition of a fixed text in bay mimic is done via the “Objects entry” window at bay mimic
FIGURE 360: ADDING A FIXED TEXT IN COMPUTER BAY MIMIC

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

1. fixed text value: text to display at mimic level
(1)
(2)
(3)

Abscissa and ordinate of a fixed text can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE user’s manual). Text area length at bay mimic is automatically
deduced from text value length (attribute (1)).
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation, transformer
representation
To define dynamic part of computer bay mimics, 3 kinds of objects are available:
• Pre-defined dynamic text, used:
− to display local/remote and SBMC status of the bay

− to manage Synchrocheck and interlock bypass during control sequence on the
bay
− to display time and synchronisation status
Generic module representation: used to display module status, linked to a specific SPS or
DPS electrical datapoint. Implicit link to possible xPC associated datapoint is given to
computer for command purpose at local HMI level, via the existence of the relation ‘is
feedback of’ between the xPS and the xPC.
• A generic module is composed of 2 sub-objects:
− a name for display (mandatory)
− a ‘xPS muti-state’ for dynamic module state display (mandatory), referencing a

dynamic bitmap object in the bitmap table, and whose relation to a xPS
datapoint (SPS or DPS) has to be filled up to precise animation datapoint
• Transformer representation: used to display transformer module; linked to a optional

Tap Position Indicator. Transformer is composed of 5 sub-objects:
− a name for display (mandatory)
− a ‘TPI muti-state’ for transformer display (mandatory), referencing a dynamic

bitmap object in the bitmap table, and whose relation to a TPI datapoint can be
filled up to precise the concerned datapoint for the following animation
− an optional ‘current TPI value’ object to display dynamically the current value of
the TPI,
− an optional ‘max TPI value’ object to display upper available value for the TPI
− an optional ‘min TPI value’ object to display lower available value for the TPI
7.3.3.1 Adding time information

The addition of the time information in bay mimic is done via the “Objects entry” window at
bay mimic level by clicking on mouse’s right button.
FIGURE 362: ADDING TIME INFORMATION IN COMPUTER BAY MIMIC

Once added, time information attributes must be set at SCE level:
1. short name of the time information area used for internal SCE identification
(1)
(2)
(3)
FIGURE 363: SETTING TIME INFORMATION ATTRIBUTES

Abscissa and ordinate of time information can be directly adjusted with the mouse in bay
mimic editor (for detail, refer to SCE user’s manual)
7.3.3.2 Positioning Local/Remote status, Synchrocheck bypass or Interlock bypass
When creating a bay mimic, the following objects are implicitly created in the mimic at a pre-
defined location:
1. Interlock bypass ‘button’
2. Local/remote status
3. Synchrocheck bypass ‘button’
Depending on customer’s need, these data can be positioned at a different location:
• directly by using mouse drag and drop in bay mimic editor
• by editing the abscissa and ordinate attributes of the object

(1)
(2)
(3)
FIGURE 364: POSITIONNING PRE-DEFINED TEXT INFORMATION IN BAY MIMIC

7.3.3.3 Adding SBMC information
The addition of the SBMC information in bay mimic is done via the “Objects entry” window at
bay mimic level by clicking on mouse’s right button.
FIGURE 365: ADDING SBMC INFORMATION IN COMPUTER BAY MIMIC

Depending on customer’s need, SBMC information can be positioned at any location in bay
mimic:
• by editing the coordinates of the object

7.3.3.4 Adding a generic module representation
In bay mimic, ‘LHMI Gen module’ is used for module dynamic representation. A ‘LHMI Gen
module’ is a graphical group constituted of:
• the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS
datapoint and to a dynamic bitmap in bitmap table
• the graphical name of the module (Name), always located on the right of the module
representation
The addition of a generic module representation in bay mimic is done via the “Objects entry”
window at bay mimic level by clicking on mouse’s right button.
FIGURE 366: ADDING A GENERIC MODULE IN COMPUTER BAY MIMIC

Once added, the representation features must be set at SCE level:
1. short name of the representation used for internal SCE identification
4. control availability (No / Yes): attribute to precise if control of the module can be
directly done via bay mimic. This attribute is significant if SPS/DPS linked to the
generic module representation (via (5) relation) is feedback of a control SPC or DPC.
If so, control availability concerns this SPC/DPC
5. Relation ‘is managed by’ that must be filled to precise which SPS or DPS is used for
bitmap animation
6. multi-bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1
Defining a bitmap table)
7. module name value: text displayed on LCD (up to 4 characters)
(1)
(2)
(3)
(4)
(5) (7)
(6)
FIGURE 367: SETTING FEATURES OF GENERIC MODULE REPRESENTATION

Coordinates (x and y) of a generic module can be directly managed by using mouse in bay
mimic editor (for detail, refer to SCE user’s manual).
• The link from an element to its bitmap is defined with the attribute : "bitmap reference".
• The "Bitmap" linked to a "LHMI xPS MultiSt" MultiState must be defined as follows:
- its "type" attribute must be set to "5-uple" value
-its 3 first file names { "file name by default", "file name for 'open' state", "file name for
'closed' state" } are mandatory and each one must be unique.
Furthermore, if the MultiState is linked to a SPS or DPS datapoint of a module
containing a "Withdrawn" SPS datapoint, through the "is managed by" relation, then
the following constraints are added to the "Bitmap" definition :
- its 2 file names { "file name for 'withdrawn open' state", "file name for 'withdrawn
closed' state" } are both mandatory and each one must be unique.
7.3.3.5 Adding a transformer representation

In bay mimic, ‘LHMI Transformer’ is used for dynamic transformer representation. A ‘LHMI
transformer’ is a graphical group constituted of:
• the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS
datapoint and to a dynamic bitmap in bitmap table
• the graphical name of the module (Name), always located on the right of the module
representation
The addition of a transformer representation in bay mimic is done via the “Objects entry”
window at bay mimic level by clicking on mouse’s right button.
FIGURE 368: ADDING A GENERIC MODULE IN COMPUTER BAY MIMIC

Once added, the representation features must be set at SCE level:
1. short name of the representation used for internal SCE identification.
4. control availability (No / Yes): attribute to precise if control of the transformer can be
directly done via bay mimic. This attribute is significant if Raise/Lower DPC control
exists for Tap changer built-in function containing the TPI datapoint used for
transformer animation (via (5) relation). If so, control availability concerns this DPC.
5. Relation ‘is managed by’ that must be filled to precise which TPI is used for
transformer animation.
6. bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1
Defining a bitmap table).
7. module name value: name of the transformer: text displayed on LCD (up to 4
characters).
(1)
(2)
(3)
(4)
(5) (7)
(6)
FIGURE 369: SETTING FEATURES OF TRANSFORMER REPRESENTATION

Abscissa and ordinate of a transformer can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE user’s manual)
When adding a transformer representation, extra values about associated TPI datapoint can
be placed in the bay mimic:
• Current TPI value (dynamic)
• Maximal TPI value
• Minimal TPI value

The addition of such TPI information in bay mimic is done via the “Objects entry” window at
transformer representation level by clicking on mouse’s right button.
FIGURE 370: ADDING A TPI INFORMATIION IN COMPUTER BAY MIMIC

Once added, TPI information can be positioned at a different location:
• by editing the X-coordinate and Y-coordinate attributes of the object

• The link from an element to its bitmap is defined with the attribute : "bitmap reference".
7.3.4 Assigning MV to bay mimic
A MV datapoint is assigned to a specific bay mimic by adding the relation ‘visualizes’ at bay
mimic level and filling it with the MV.
FIGURE 371: ASSIGNING MV DATAPOINT TO BAY MIMIC

Once the relation added and filled, its attributes ‘scale’ must be set at SCE level:
1. scale (120% / 200% / No bargraph), to precise which representation is used for the
MV in the bay mimic
(1)
FIGURE 372: SETTING MV REPRESENTATION IN BAY MIMIC

• A MV datapoint visualized in a "Bay mimic" (relation "visualizes") must belong to the

bay represented by the "Bay mimic" (relation "represents").
• For each visualized MV datapoint, the "transmission on event" attribute must be set
neither to "Cyclic short period" value nor to "Cyclic long period" value to avoid overflow
of the Bay mimic input buffer.
7.4 Displaying datapoint status with Led

SPS and DPS datapoint status can be displayed via leds of GHU200 board by adding the
relation ‘has state displayed on’ at datapoint level (1). Only datapoint managed by computer
can be displayed via the Leds of its GHU200 board.
(1)
FIGURE 373: DISPLAYING DATAPOINT STATUS WITH LED (E.G. FOR BAY SPS DATAPOINT)
Once added at SPS (resp. DPS) level, the relation must be filled with the relevant associated
led and the following relation attributes should be updated:
1. Led status for ‘Set’ state (resp 'Closed'): ( Off / On / Blinking slow / Blinking fast)
2. Led status for ‘Reset’ state (resp 'Open'): ( Off / On / Blinking slow / Blinking fast)
3. Led status for ‘Invalid’ state : ( Off / On / Blinking slow / Blinking fast)
(1)
(2)
(3)
FIGURE 374: SETTING LED STATUS FOR A DATAPOINT (E.G. FOR SPS DATAPOINT)
• 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).
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.
Hardware
platform
PROJECT
CONFIGURATION TARGET
RESOURCE KERNEL
Exchange PRJLIBRARY.MDB file *.STF files

diagrams
POU
Dictionary
Graphical
Dictionary Language Editors
C0251ENa
FIGURE 375: 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.
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.
8.2 Usage of SCE datapoints in ISaGRAF

The DataPoints (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 DataPoints.
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 lik (interface definition)
• The function is client of the Data Point (Client relationship):

see chapter 6.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 parents 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.
• 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
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,
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.
• 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

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
The function serves the DP whatever DP read/write input/output
(the function provides values) Threshold, alarm read control
The 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
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 section 8.2.6
ISaGRAF dictionary data structure ).
Within the calculators ISaGRAF kernel, the output DPs are reached by C functions, using an
ID (see section 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 following characters must be, either a letter, either a digit or an underscore
So the identifier of I/O symbols is made by concatenation of a prefix given by the user, a
prefix automatically given by the SCE (in, out, in_out) and an identifier number ( refer to
sections 6.6.2.5 Defining Isagraf IO prefix for an input and 6.6.2.8Defining Isagraf IO prefix
for an output).
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.
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 DPS
• MOTION 00 = 3
• OPEN / FORCED OPEN / SUBSTITUTED OPEN = 4
• CLOSED / FORCED CLOSED / SUBSTITUTED CLOSED = 5
NOTE: UNDEFINED state is seen as INVALID (see Quality attribute)
Status attribute for MPS
• State1 / FORCED state1 / SUBSTITUTED state1 = 7

• State6 / FORCED state6 / SUBSTITUTED state6 =12
• State7 / FORCED state7 / SUBSTITUTED state7 =13
Quality attribute
• VALID = 0
• INVALID ≠ 0 (TOGGLING, UNKNOWN, SELFCHECK FAULTY, SUPPRESSED,
UNDEFINED)
If Quality attribute is INVALID, Status attribute is non-significant.
Alarm attribute
Unusable
8.2.6.2 SPC, DPC
SCE ISaGRAF
Status Status DINT
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
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 attribute
• VALID = 0
• SELFCHECK FAULTY = 1
• UNKNOWN = 2
• FORCED = 4
• SUPPRESSED = 8
• SUBSTITUTE = 16
• SATURATED = 64
• UNDEFINED = 128
• 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 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.
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 ‘is client of’ or ‘manages’ relations:
• SPC, DPC
• Select part for SBO on SetPoint
Name Comment Parameter/return Acces C Type Available values

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_cmd Identifier of the Parameter Output Long (DINT) Use a locale variable
command
Prototype C:
unsigned char Send_Binary_Order(char Order, long Bypass, long Ref_DP ,long Ref_Cmd )
8.2.7.2 Send_Digital_Order
This function concerns SetPoints used in ‘is client of’ or ‘manages’ relations.
Select for SBO is done via function Send_Binary_Order.
Name Comment Parameter/retur Acces C Type Available values

n code (CEI Type)
char (BOOL) TRUE : OK
Order Value order Parameter Input Float (REAL)
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 ‘is client of’ or ‘manages’ relations.
Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
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
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)
8.2.7.4 Send_Quality_Order
This function concerns SPS, DPS, MPS, MV, TPI, COUNTER used in ‘is client of’ or
‘manages’ relations for Forcing/Suppression/Substitution functionality.

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
command
Prototype C:
unsigned char Send_Quality_Order(char Quality, char Binary_Value, float Digital_Value,
long Ref_DP, long Ref_cmd)
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".

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

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

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

(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)
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".

(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)
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.
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".

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

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)
BLANK PAGE
MiCOM C264/C264C
LEXICAL
CONTENT
2. LEXICAL 4
C264/EN LX/C40 Lexical
BLANK PAGE

This document is a chapter of MiCOM C264 documentation binders. It is the lexical.
2. LEXICAL
AC Alternating Current
A/D Analog/Digital
ADC Analogue to Digital Converter
AI Analogue Input (Measurement Value including state attribute)
Commonly Voltage or current DC signals delivered by transducers,
and representing an external value (refer to CT/VT for AC).
AIS Air Insulated Substation
AIU Analogue Input Unit
Computer C264 Board name for DC Analogue Input
Alarm An alarm is any event tagged as an alarm during configuration phase
AO Analogue Output
Value corresponding to a desired output current applied to a DAC.
API Application Programming Interfaces
AR Auto-Reclose
ARS Auto-Recloser
ASCII American Standard Code for Information Interchange
ASDU Application Specific Data Unit
Name given in OSI protocol for applicative data (T103, T101..)
ATCC Automatic Tap Change Control
Same as AVR, automation charged to regulate secondary voltage
AVR Automatic Voltage Regulator
Automatism used to regulate secondary voltage by automatic tap
changer control (see ATCC). Set of features can be added, see
chapter C264 FT
Bay Set of LV, MV or HV plants (switchgears and transformers) and
devices (Protective, Measurement…) usually around a Circuit
Breaker and controlled by a bay computer.
BCD Binary Coded Decimal
One C264 supported coding on a set of Digital Inputs, that determine
a Digital Measurement, then Measurement value (with specific invalid
code when coding is not valid). Each decimal digit is coded by 4
binary digits.
BCP Bay Control Point
Name given to the device or part used to control a bay. It can be
Mosaic Panel, C264 LCD ‘Local Control Display),… Usually associate
with Remote/Local control.
BI Binary Input (or Information)
Name given into Computer C264 of information already filtered,
before it becomes a SPS, DPS… with time tag and quality attributes
BIU Basic Interface Unit
Computer C264 Board for auxiliary power supply, watchdog relay,
redundancy I/O
BNC A connector for coaxial cable.
B-Watch Monitoring and control device for GIS substation.
CAD Computer Aided Design
Computer application dedicated to design like wiring, protective
setting…
CAS CASe
Computer C264 rack
CB Circuit Breaker
Specific dipole switch with capability to make line current and break
fault current. Some have isolation capability (nominal-earth at each
side)
CC Complemented Contact
CCU Circuit breaker Control Unit
Computer C264 Board dedicated to switch control with 8DI, 4 DO
CDM Conceptual Data Modelling
Is the modelisation of system/devices data using a hierarchy of
structured data (called object of class) with their attributes, method or
properties and the relations between themselves.
It maps common data to devices or components of devices, with
guaranty of interoperability.
CM
CMT Computer Maintenance Tool
COMTRADE Common Format For Transient Data Exchange ( international
standard IEC 60255-24)
CPU Central Processing Unit
Computer C264 main Board based on PowerPC
CRC Cyclic Redundancy Check
Coding result send with packet of transmitted data to guarantee their
integrity. Usually result of a division of transmitted data by polynomial.
CSV Character Separate Values
ASCII values separated by predefined character or string like in Excel
or ASCII Comtrade.
CT Current Transformer
Basically the electric device connected to process and extracting a
current measurement. By extension part of a device (C264) that
receives AC values and convert it to numerical measurement value.
CT/VT Current and Voltage transformers
(Conventional) By extension, it is the C264 TMU board.
CT/VT Current and Voltage transformers
(Non-Conventional or New generation of captor based for example on light diffraction under
intelligent) electric field, without transformer, that give s directly numerical
measurement of voltage and current like communicating IED.
DAC Digital to Analogue Converter
Used to generate analogue signals (usually DC) from a digital value.
DB DataBase
Tool or set of data that define all configuration of a system or specific
device like computer. Opposed to setting or parameter DB has a
structure that can not be modified on line. DB are always versioned.
DB-9 A 9-pin family of plugs and sockets widely used in communications
and computer devices.
DBI Don’t Believe It
Term used for undefined state of a double point when input are not
complementary. DBI00 is state motion or jammed. DBI11 is
undefined.
DC Direct Current
DC, DPC Double (Point) Control
Two digit and/or relays outputs used for device control with
complementary meaning (OPEN, CLOSE).
DCF77 External master clock and protocol transmission

LF transmitter located at Mainflingen, Germany, about 25 km south-
east of Frankfurt/Main, broadcasting legal time on a 77.5 kHz
standard frequency.
DCP Device Control Point
Located at device level (electric device or IED). It should have its own
Remote/Local switch.
DCS Digital Control System
Generic name of system based on numeric communication and
devices, to be opposed to traditional electrically wired control.
DCT Double CounTer
Counter based on 2 DI with complementary states (counting
switchgear manoeuvre for example)
DE Direct Execute
Device Term used for one of the following unit:
Protective relays, metering units, IED, switchgear (switching device
such as CB, disconnector or earthing switch), disturbance or quality
recorders.
DI Digital Input:
Binary information related to the presence or to the absence of an
external signal, delivered by a voltage source.
DIN Deutsche Institut für Normung
The German standardisation body.
DIU DC Input Unit
Computer C264 Board name for Digital Input
DM Digital Measurement
Is a measurement value which acquisition is done by DI and a
specific coding BCD, Gray, 1 among N…
DNP3.0 Distributed Network Protocol
DNP3 is a set of communication protocols used between components
in process automation systems.
DO Digital Output
Used to apply a voltage to an external device via a relay, in order to
execute single or dual, transient or permanent commands.
DOU Digital Output Unit
Computer C264 Board name for Digital Output
DP Double Point
Information/control derived from 2 digital inputs/output; usually used
for position indication of switching devices (OPEN, CLOSE).
DPC Double Point Control
DPS Double Point Status
Position indication of switching devices (OPEN, CLOSE).
ECU Extended Communication Unit.
External module connected to the CPU board. This module converts
non-insulated RS232 into optical signal or insulated RS485/RS422.
EH90 Transmission protocol dedicated to time synchronisation and
standardised by EDF. Specification document: D.652/90-26c, March
1991.
EMC Electro-Magnetic Compatibility
Event An event is a time tagged change of state/value acquired or
transmitted by a digital control system.
FAT Factory Acceptance Test

Validation procedures execution with the customer at factory.(i.e.
SAT)
FBD Functional Block Diagram
One of the IEC61131-3 programming languages (language used to
define configurable automation).
FIFO First In First Out
FO Fibre Optic
FP Front Panel
FTP Foil Twisted Pair
Gateway Level 6 session of OSI, the gateway is any device transferring data
between different networks and/or protocol. The RTU function of the
C264 gives a gateway behaviour to SCADA or RCP level. PACIS
Gateway is separate PC base device dedicated to this function.
GHU Graphic Human interface Unit
Computer C264 Front Panel digital part (LCD, buttons, Front RS)
GHU Graphical Human Unit
Front panel of C264 with LCD and buttons
GIS Gas Insulated Substation
GMT Greenwich Mean Time
Absolute time reference
GPS Global Positioning System
Based on triangulation from satellite signal, that transmit also
absolute GMT time used to synchronise a master clock
GOOSE Generic Object Oriented Substation Event
Group Logical combination of BI (i.e. SP, DP, SI or other groups).
Hand Dressing Facility for an operator to set manually the position of a device
(acquired by other means) from the HMI at SCP level; e.g. from
OPEN to CLOSE (without any impact on the “physical ” position of
the electrical switching device).
HMGA Horizontal Measurement Graphical Area
HMI Human Machine Interface
Can be PACIS OI (Operator Interface) or C264 LCD (Local Control
Display) or Leds, mosaic...
HSR High Speed auto-Recloser
First cycles of AR
HTML Hyper Text Mark-up Language
Used as standard for formatting web display
HV High Voltage (for example 30kV to 150kV)
I/O Input/Output
IEC International Electro-technical Commission
IED Intelligent Electronic Device
General expression for a whole range of microprocessor based
products for data collection and information processing
IP Internet Protocol
IRIG-B Inter-Range Instrumentation Group standard format B. This is an
international standard for time synchronisation based on analogue
signal.
JAMMED Invalid state of a Double Point:

Occurs when the two associated digital inputs are still in state 0 after
an user-selectable delay (i.e. when the transient state “ motion ” is
considered as ended).
Kbus Term used for the protocol Courier on K-Bus network (kind of
(Kbus Courier) RS422).
LAN Local Area Network
L-BUS Legacy Bus
Generic name of Legacy or field networks and protocols used to
communicate between C264 (Legacy Gateway function) and IED on
field bus. Networks are based on (RS232,) 422, 485. Protocols are
IEC 60850-5-103 (T103 or VDEW), Modbus AREVA or MODICON
LCD Liquid Crystal Display
Local Control Display
On C264
LD Ladder Diagram
LSB Least Significant Bit
LED Light Emitting Diode
LF Low Frequency
LOC Local Operator Console
Dedicated to maintenance operation
L/R Local / Remote
Local / Remote When set to local for a given control point it means that the
Control Mode commands can be issued from this point, else in remote control are
issue for upper devices.
LV Low Voltage
MAFS Marketing And Functional Specification
MC Modular Computer
MCB Mini Circuit Breaker. Its position is associated to tap changer.
MDIO Management Data Input/Output
A standard driven, dedicated-bus approach that is specified in
IEEE802.3
Measurements Values issued from digital inputs or analogue inputs (with value, state
and time tag).
Metering Values computed depending on the values of digital or analogue
(non-tariff) inputs during variable periods of time (time integration).
Metering Values computed depending on the values of digital or analogue
(tariff) inputs during variable periods and dedicated to the energy tariff.
These values are provided by dedicated “tariff computer ” which are
external to the MiCOM Systems.
MIDOS AREVA Connector: Used for CT/VT acquisition
MMC Medium Modular Computer
ModBus Communication protocol used on secondary networks with IED or
with SCADA RCP. 2 versions exist with standard MODICON or
AREVA one.
Module Word reserved in PACIS SCE for all electric HV devices. It groups all
switch-gears, transformer, motors, generators, capacitors, …
MOTION Transient state of a Double Point

Occurs when the two associated digital inputs are momentarily in
state 0 (e.g. position indication when an electrical device is
switching). The concept of “momentarily” depends on a
user-selectable delay.
MPC Protection Module for Computer
MV Medium Voltage
MVAR Mega Volt Ampere Reactive
NBB Numerical Busbar Protection
NC Normally Closed (for a relay)
NO Normally Open (for a relay)
OBS One Box Solution
Computer that provides protection and control functions with local
HMI. The prime application of this device is intended for use in
substations up to distribution voltage levels, although it may also be
used as backup protection in transmission substations. Likewise, the
OBS may be applied to the MV part of a HV substation that is being
controlled by the same substation control system.
OI Operator Interface
OLE Object Linking and Embedding
OLE is a Microsoft specification and defines standards for interfacing
objects.
OLTC On Line Tap Changing
OPC OLE for process control
OPC is a registered trademark of Microsoft, and is designed to be a
method to allow business management access to plant floor data in a
consistent manner.
Operation hours Sum of time periods, a primary device is running under carrying
energy, e.g. circuit breaker is in Close state and the current is
unequal 0 A.
OSI Open System Interconnection
Split and define communication in 7 layers : physical, link, network,
transport, session, presentation, application
PACiS Protection, Automation and Control Integrated Solutions
PLC Programmable Logic Control
Within the PLC-programs are defined the configurable control
sequences or automations taken into account by the MiCOM
Systems.
POW Point On Wave
Point on wave switching is the process to control the three poles of
an HV-circuit breaker in a way, to minimise the effects of switching.
PSL Programmable Scheme Logic
PSTN Public Switched Telephone Network
PT100 Probes of temperatures providing analogue signals.
RCC Remote Control Centre
Is a computer or system that is not part of MiCOM system. RCC
communicates with and supervises MiCOM system using a protocol.
RCP Remote Control Point

Name given to the device or part used to control remotely several bay
or sub-station. Usually associate with Remote/Local sub-station
control. It is a SCADA interface managed by the MiCOM system
through Telecontrol BUS. Several RCP’s can be managed with
different protocols.
Remote Control Mode When set for a control point it means that the commands are issued
from an upper level and are not allowed from this point.
Remote HMI Remote HMI is a client of the substation HMI server. The client may
provide all or part of functions handled by the substation HMI.
RI Read Inhibit
This output indicates the availability of an analogue output (e.g.
during DAC converting time)
RJ-45 Registered Jack-45
A 8-pin female connector for 10/100 Base-T Ethernet network
RMS Root Mean Square
RRC Rapid ReClosure
RS-232 Recommended Standard 232
A standard for serial transmission between computers and peripheral
devices.
RS-422 A standard for serial interfaces that extends distances and speeds
beyond RS-232. Is intended for use in multipoint lines.
RS-485 A standard for serial multipoint communication lines. RS-485 allows
more nodes per line than RS-422
RSVC Relocatabled Static Var Compensator
RTC Real Time Clock
RTU Remote Terminal Unit
Stand alone computer that acquires data and transmit them to RCP
or SCADA. Typically it is the C964. RTU link is the TBUS.
SAT Site Acceptance Test
Validation procedures executed with the customer on the site.
SBMC Site Based Maintenance Control mode
A bay in SBMC mode does not take into account the commands
issued from RCP; moreover, some of its digital points and
measurements (defined during the configuration phase) are not sent
anymore to the RCP (they are “ automatically ” suppressed).
SCADA Supervisory Control And Data Acquisition
SCE System Configuration Editor
SBO Select Before Operate
A control made in two steps, selection and execution. Selection
phase give a feedback. It can be used to prepare, reserve during
time, configure circuit before execution.
Controls are done into a protocol, or physical (DO select with DI
Select then DO execute).
S-BUS Station Bus
Federal network between PACIS devices.
SCADA Supervisory Control And Data Acquisition
Equivalent to RCC
SCP Substation Control Point
Name given to the device or part used to control locally several bays
or sub-station. Usually associate with Remote/Local sub-station
control. It is commonly PACIS Operator Interface.
SCS Substation Control System

SCT Single Counter
Setpoints (analogue) Analogue setpoints are analogue outputs delivered as current loops.
Analogue setpoints are used to send instruction values to the process
or to auxiliary devices.
Setpoints (digital) Digital values sent on multiple parallel wired outputs Each wired
output represent a bit of the value. Digital setpoints are used to send
instruction values to the electrical process or to auxiliary devices.
SFC Sequential Function Chart
SI System Indication
Binary information that do not come from external interface. It is
related to an internal state of the computer (time status, hardware
faults…). It is the result of all inner function (AR, …), PSL, or
ISaGRAF automation.
SICU 4 Switchgear Intelligent Control Unit
Control unit of an intelligent circuit breaker (fourth generation)
SINAD Signal-plus-Noise-plus-Distorsion to Noise-plus-Distorsion ratio.
SINAD is fully expressed in dB.
SOE Sequence Of Events
Other term for the event list.
SP Single Point
SPS Single Point Status
SPC Single Point Control
ST Structured Text
STP Shielded Twisted Pair
Substation computer Bay computer used at substation level.
Suppression A binary information belonging to a bay in SBMC mode will be
(Automatic) automatically suppressed for the remote control. However changes of
state will be signalled locally, at SCP.
Suppression (Manual) A binary information can be suppressed by an order issued from an
operator. No subsequent change of state on a “suppressed
information ” can trigger any action such as display, alarm and
transmission.
SWR Switch Redundant
Computer C264 board Ethernet switch with redundant Ethernet
SWU Switch Unit
Computer C264 board Ethernet switch
T101 Term used for IEC60870-5-101 protocol
TBC To Be Completed
TBD To Be Defined
T-BUS Telecontrol Bus
Generic name of networks and protocols used to communicate
between PACIS Gateway or C264 Telecontrol Interface function and
the RCP. Networks are based on RS232, 485, or Ethernet (T104).
Protocols are IEC 60850-5-101 (T101), Modbus MODICON
TC True Contact
TCIP Tap Changer in Progress
TCU Transformer Current Unit
Computer C264 CT/VT Board : Current acquisition
TDD Total Demand Distorsion
The total demand distortion is similar to the THD but applied to
currents and with a rated current (In) as reference
THD Total Harmonic Distorsion
The total harmonic distortion represents the sum of all voltage
harmonics
TMU Transducerless Measurement Unit
Topological Interlocking algorithm, based on evaluation of topological information
interlocking of the switchgear arrangement in the HV network, the switchgear kind
and position, and defined rules for controlling this kind of switch (e.g.
continuity of power supply)
TPI Tap Position Indication (for transformers).
Frequently acquired via a Digital Measurement
TVU Transformer Voltage Unit
Computer C264 CT/VT Board : Voltage acquisition
UCA Utility Communications Architecture
Communication standard (mainly US) used for PACIS SBUS
communication
UPI Unit Per Impulse
Parameter of counter to convert number of pulse to Measurement
value. Both data (integer and scaled float) are in common class
UCA2 Accumulator.
UTC Universal Time Co-ordinates (or Universal Time Code)
Naming that replace GMT (but it is the same)
VDEW Term used for IEC60870-5-103 protocol
VMGA Vertical Measurement Graphical Area
Voltage level Set of bays whose plants and devices are dealing with the same
voltage (e.g. 275kV, 400 kV).
VT Voltage Transformer
Basically the electric device connected to process and extracting a
voltage measurement. By extension part of a device (C264) that
receives this AC value and convert it to numerical measurement
value. VT are wired in parallel.
WYE Three phases + neutral AI values
Publication: C264/EN O/C40
AREVA T&D's Automation & Information Systems Business www.areva-td.com

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

c264 en Op c40 Global

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

c264 en Op c40 Global

Diunggah oleh

Hak Cipta:

Format Tersedia

MiCOM

MiCOM C264/C264C Page 1/2

Safety & Handling C264/EN SA/C40

Introduction C264/EN IT/C40

Technical Data C264/EN TD/C40

Functionnal Description C264/EN FT/C40

Hardware Description C264/EN HW/C40

Connection C264/EN CO/C40

Human Machine Interface C264/EN HI/C40

Application C264/EN AP/C40

Lexical C264/EN LX/C40

Page 2/2 MiCOM C264/C264C

SAFETY & HANDLING

MiCOM C264/C264C Page 1/12

2. HEALTH AND SAFETY 4

3. DECOMMISSIONING AND DISPOSAL 6

4. TECHNICAL SPECIFICATIONS FOR SAFETY 7

5. HANDLING OF ELECTRONIC EQUIPMENTS 8

6. PACKING AND UNPACKING 9

8. COPYRIGHTS & TRADEMARKS 11

9. WARNINGS REGARDING USE OF AREVA T&D EAI PRODUCTS 12

Page 2/12 MiCOM C264/C264C

MiCOM C264/C264C Page 3/12

Page 4/12 MiCOM C264/C264C

2. HEALTH AND SAFETY

2.1 Health and Safety

• Voltage rating and polarity;

• CT circuit rating and integrity of connections;

• Integrity of earth connection (where applicable)

MiCOM C264/C264C Page 5/12

Insulation and dielectric strength testing

Page 6/12 MiCOM C264/C264C

3. DECOMMISSIONING AND DISPOSAL

MiCOM C264/C264C Page 7/12

4. TECHNICAL SPECIFICATIONS FOR SAFETY

Protective class: IEC 60255-27: 2005 Class I This equipment requires

Product Safety: 73/23/EEC Compliance with the

Page 8/12 MiCOM C264/C264C

5. HANDLING OF ELECTRONIC EQUIPMENTS

MiCOM C264/C264C Page 9/12

6. PACKING AND UNPACKING

Page 10/12 MiCOM C264/C264C

MiCOM C264/C264C Page 11/12

8. COPYRIGHTS & TRADEMARKS

Page 12/12 MiCOM C264/C264C

9. WARNINGS REGARDING USE OF AREVA T&D EAI PRODUCTS

MiCOM C264/C264C Page 1/8

2. INTRODUCTION TO MiCOM GUIDES 4

3. INTRODUCTION TO MiCOM APPLICATIONS 6

Page 2/8 MiCOM C264/C264C

MiCOM C264/C264C Page 3/8

• P range protection relays;

• C range control products;

• M range measurement products for accurate metering and monitoring;

• S range versatile PC support and substation control packages.

Page 4/8 MiCOM C264/C264C

2. INTRODUCTION TO MiCOM GUIDES

MiCOM C264/C264C Page 5/8

2.1.10 Chapter Communications (CT)

Page 6/8 MiCOM C264/C264C

3. INTRODUCTION TO MiCOM APPLICATIONS

MiCOM C264/C264C Page 7/8

C264C WEB access

Cubicle/ Switchboard MV FEEDER BAYS