Communications C264/EN CT/C30

MiCOM C264/C264C

COMMUNICATIONS
Communications C264/EN CT/C30

MiCOM C264/C264C Page 1/92

CONTENT

1. SCOPE OF THE DOCUMENT 5

2. SCP COMMUNICATION 6
2.1 Communication on Station bus 6
2.1.1 Finality 6
2.1.2 Inputs 6
2.1.3 Supported services 7
2.1.4 Supported data objects 7

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

Page 2/92 MiCOM C264/C264C

3.7 Slave Modbus (MODICON) profile 44

3.7.1 Introducing MODBUS 44
3.7.2 Slave responses 45
3.7.3 Serial transmission mode 46
3.7.4 MODBUS Functions 47
3.7.5 Function 01 / 02: Read Coil Status – Read Input Status 48
3.7.6 Function 03 / 04: Read Holding Registers / Input Registers 49
3.7.7 Function 05: Force Single Coil 51
3.7.8 Function 06: Preset single register 51
3.7.9 Function 08: Diagnostic [Sub-function 0 only] 52
3.7.10 Function 15: Force Multiple Coils 52
3.7.11 Function 16: Preset multiple registers 52

4. IED COMMUNICATION 53
4.1 Overview 53
4.2 IED Common functionality 53
4.2.1 Interface to IEDs 53
4.2.2 Behaviour 54
4.2.3 Data received from IEDs 58
4.2.4 Data sent to IEDs 58
4.2.5 Tunnelling 59
4.2.6 Limits and Performances 62
4.3 MODBUS communication 62
4.3.1 Finality 62
4.3.2 Interface to IEDs 62
4.3.3 Behaviour 63
4.3.4 Data received from IEDs 63
4.3.5 Data sent to IEDs 64
4.3.6 Error management 64
4.3.7 Limits and Performances 64
4.4 DNP 3.0 Communication 65
4.4.1 Finality 65
4.4.2 Interface to IEDs 65
4.4.3 Behaviour 66
4.4.4 Data received from IEDs 67
4.4.5 Data sent to IEDs 67
4.4.6 Master DNP3.0 Profile 68
4.4.7 DNP.3 Level 3 IMPLEMENTATION TABLE 71
Communications C264/EN CT/C30

MiCOM C264/C264C Page 3/92

4.5 IEC 60870-5-103 Communication 75

4.5.1 Finality 75
4.5.2 Interface to IEDs 75
4.5.3 Behaviour 76
4.5.4 Data received from IEDs 77
4.5.5 Data sent to IEDs 79
4.6 IEC 60870-5-101 Communication 80
4.6.1 Finality 80
4.6.2 Master IEC 60870-5-101 profile 80
C264/EN CT/C30 Communications

Page 4/92 MiCOM C264/C264C

BLANK PAGE
Communications C264/EN CT/C30

MiCOM C264/C264C Page 5/92

1. SCOPE OF THE DOCUMENT

This document is a chapter of MiCOM C264 documentation binders. It describes the various
standard communications protocols implemented in the MiCOM C264.
MiCOM C264 supports 3 different types of communications:

• SCP Communication: communication over Ethernet IEC61850

• SCADA Communication: communication with an upper level SCADA system over

protocols (IEC 60870-5-101, IEC 60870-5-104, DNP3.0, MODBUS, DNP3 on TCP)

• IED Communication: communication with legacy IEDs. The MiCOM C264 is

considered as a master (IEC 60870-5-103, DNP3.0, MODBUS, IEC 60870-5-101)
C264/EN CT/C30 Communications

Page 6/92 MiCOM C264/C264C

2. SCP COMMUNICATION
2.1 Communication on Station bus
2.1.1 Finality
This item describes IEC61850-8-1 implementation inside MiCOM C264.
2.1.2 Inputs
2.1.2.1 Information: MiCOM C264 application SCP
The type of information that can be transmitted are:

• Changes of state of binary inputs

• Measurements (Analogue or CT/VT)

• Counters

• Controls

• Control acknowledgements

• Time synchronisation message

• Records (Event, fault, disturbance)

• MiCOM C264 information (Init. report, Operating mode, control mode, Date)
2.1.2.2 Information SCP MiCOM C264 application
The type of information that can be transmitted are:

• Changes of state of binary inputs

• Measurements (Analogue or CT/VT)

• Counters

• Controls

• Control acknowledgements

• Time synchronisation message

• Request for records

• Database downloading
Communications C264/EN CT/C30

MiCOM C264/C264C Page 7/92

2.1.3 Supported services

Services supported by the IEC61850 agency integrated in the MiCOM C264 are listed in the
ACSI service conformance statement defined in Table A.3 of document
MiCOM C264/C264P PICS.

2.1.4 Supported data objects

The following table describes the common class supported by the IEC61850 agency
integrated in the MiCOM C264:

Client Server
Common Class Comment
support support
Status
SPS Single input status YES YES
DPS Double input status YES YES
INS Integer input status YES YES
ACT Protection activation information YES YES
ACD Directional protection activation YES YES
information
Measurements
MV Measurement value YES YES
CMV Complex measurement value YES YES
WYE 3 phase + N measurement YES YES
DELTA Phase to phase measurement YES YES
Counters
BCR Binary counter YES YES
Control
SPC Single point control YES YES
DPC Double control output YES YES
BSC Binary step control YES YES
APC Analogue output YES YES
INC Integer control output YES YES
ISC Integer step control output YES YES
Description
LPL Logical node name plate YES YES
DPL Device name plate YES YES
Report Control Block
URCB Unbuffered report control block YES YES
BRCB Buffered report control block NO YES
C264/EN CT/C30 Communications

Page 8/92 MiCOM C264/C264C

3. SCADA COMMUNICATION
3.1 Overview
A MiCOM C264 can be connected to a SCADA through networks using various protocols:
1. DNP3 (serial link)
2. T101 (serial link)
3. T104 (TCP/IP link)
4. DNP3 (TCP/IP link)
5. MODBUS (serial link)
It is possible to have:

• Two different protocols running in parallel on different links

• The same protocol on two links (redundant mode). This is actually not supported for
Modbus protocol.

• For protocols running on TCP/IP link, there is only one Ethernet port. So redundancy
is not available for those protocols, and they all are physically running on the same
network (including IEC61850 protocol).

• In T104 protocol the C264 (server) can manage two clients. These two clients have
separate configurations but may have same data. On the SCADA port, up to four front
ends can be defined, corresponding to one active port and three backup ports. So, up
to four IP addresses will be defined during the configuration of each T104 client. If
both clients are communicating with the computer, they must manage thein own
redundancy for doing controls with coherency.
Common features to all SCADA communication and all protocols are specified below.
Specific features to each protocol are specified in subsequent paragraphs.
3.2 SCADA common functionality
3.2.1 Interface to SCADA
This paragraph describes the exchange of data between the “SCADA communication”
function and the Master SCADA. It is split into two sub-paragraphs:

• Inputs: data received from SCADA.

• Outputs: data sent from the “SCADA communication” function to SCADA.

For each kind of protocol, it is indicated if the data is treated or not:
3.2.1.1 Input

Data DNP3 T101 T104 DNP3 on IP MODBUS

Remote link initialisation Treated Treated Treated Treated Treated
General interrogation Treated Treated Treated Treated Not Treated
Control Treated Treated Treated Treated Treated
Setpoint Treated Treated Treated Treated Treated
Time synchronisation Treated Treated Treated Treated Not Treated
Database (download) Not Treated Not Treated Not Treated Not Treated Not Treated
Communications C264/EN CT/C30

MiCOM C264/C264C Page 9/92

3.2.1.2 Output

Data DNP3 T101 T104 DNP3 on IP MODBUS

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

3.2.2 Behaviour and specific treatments

NOTE: In subsequent paragraphs, the master station (e.g.: SCADA) is referred to
as the controlling station.
3.2.2.1 Initialisation
There is a running database for each SCADA link. At initialisation, a GI is performed on the
application in order to initialise these databases.
The GI sequence consists of different requests to the MiCOM C264 application in order to
get the value and state of all data (Binary input, measurement, counter, step position
indication).
3.2.2.2 General interrogation
The Outstation interrogation function is used for updating the controlling station after the
internal station initialisation procedure, or when the controlling station detects a loss of
information, or when the link layer connection has been re-established. The general
interrogation function of the controlling station requests the MiCOM C264 to transmit the
actual values of all addressed datapoints.
The MiCOM C264 marks the end of the general interrogation procedure by sending an
indication to the controlling station when the protocols allow it.
3.2.2.3 Clock synchronisation
Clock in MiCOM C264 may be synchronised by the controlling station.
NOTE: The clock can be synchronised by other means: external clock, Master
Clock, operator. Only one source will be selected at a given time. This
selection is performed by the clock synchronisation function based on
configuration and priority level. However the controlling station is not
informed of this fact and must continue to send clock synchronisation
commands.
The controlling station must perform the correction made on the time sent in synchronisation
commands.
3.2.2.4 Database downloading and switching
This function is only implemented in T101 and T104 protocols. The SCADA can download a
database and only a database. Then the type of file is 1 (Transparent file) and the IOA
(information object address) must be 1. The database downloaded will be the standby
database.
To switch over this database, the SCADA must send a reset process command
(C_RP_NA_1 (105)) with cause of transmission equal to 6 (activation) and QRP field set to 1
(general reset of process)
C264/EN CT/C30 Communications

Page 10/92 MiCOM C264/C264C

3.2.2.5 Local/remote mode

A substation or a bay can be in local or remote mode. When it is in local mode it can not be
controlled remotely and when it is in remote mode, it can not be controlled locally.
Each Mode can be associated to a binary input.
3.2.2.6 Taking Control
A Substation can be configured in taking control mode. This means:

• At a given time, only one SCADA can send controls to the substation (the one which
has the control).

• To be allowed to send controls, a SCADA must take control of the substation by

sending a specific command to the MiCOM C264.
On each SCADA link, there is a binary input indicating if the corresponding SCADA has the
control of the substation.
On reception of a Taking Control command, the MiCOM C264:

• Puts the substation in Remote mode (if it was in Local Mode)

• Gives the control to the (last) SCADA which asks for it

− Reset the “Taking Control Binary input” of the SCADA which had previously the
control

− Set the “Taking Control Binary input” of the SCADA which asks the control
If the take control command is set for a SCADA, MiCOM C264 should refuse all commands
from other SCADAs.
3.2.2.7 SBMC mode
This mode is used to test a substation while it is in Remote mode. As this mode is a test
mode, MiCOM C264 won’t send all changes of state to SCADA.
When bay turns to SBMC mode, MiCOM C264 will send to SCADA all concerned data
(configured Bay Based in the SCE) at specific states defined in the SCE for the management
of SBMC.
For those data, change of state won’t be transmitted, but will be memorised by MiCOM C264
while the Bay is in SBMC mode.
When the Bay returns to Non SBMC mode, MiCOM C264 will send the current state of any
data that has changed whilst the Bay has been in SBMC mode.
3.2.2.8 Redundancy
Serial links can be configured as redundant. In this case, SCADA can send requests on both
serial links: “main link “or “redundant link”.
MiCOM C264 always responds on the link used by SCADA for requesting the slave
3.2.2.9 Automatic synchrocheck
SCADA can send control to synchronised circuit breakers with a facility to bypass the
synchrocheck.
3.2.3 Data sent to SCADA
After the initialisation sequence, MiCOM C264 Slave sends the state of all of its data to the
SCADA. The current state of data is sent as state or as change of state messages,
depending on the protocol.
The data, which can be sent to SCADA, is detailed in the paragraphs below.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 11/92

3.2.3.1 Binary inputs

Binary inputs can be sent as states or as changes of state depending on the protocol.
A binary input can be associated with a single point or a double point.
NOTE: Multipoint status is not treated.
3.2.3.2 Measurements
Measurements can be sent in various formats: float, integer, normalised, scaled…
Measurements can be sent as periodical messages or as changes of state: variation,
threshold, and invalidity.
The choices of format and mode of transmission are done by configuration according to the
protocol.
3.2.3.3 Counters
Counters can be sent as spontaneous messages (changes of state) or on demand (counter
General Interrogation).
The choice whether to use spontaneous messages for a counter is done by configuration,
according to the protocol.
3.2.3.4 Tap position
Tap position indication (TPI) can be sent to SCADA as states or as changes of state. The
choice between state or change of state depends on the protocol. If the protocol allows the
both, the choice is done by configuration.
A digital input can be associated with a single point or a double point.
3.2.3.5 Computer disturbance file
Only Slow Wave Form is implemented for T101 or T104. maximum five slow wave form files
can be available at a time. The IOA of the first file is configured and the others are
consecutive. the type of file is 1 (Transparent file). When a slow wave form file is available,
an ASDU Directory (F_DR_TA_1 (126)) is sent by the computer with cause of transmission
spontaneous (3). The file is already available until a new file is created and replaces it. The
Scada can identify the file only with its date. The size of file must be lower or equal to the
size of one section
3.2.3.6 Sequence Of Events File (SOE)
The SOE is a circular file where Events of the MiCOM C264 are stored. There is one SOE
for each SCADA link.
The Events, which can be stored in SOE, are Binary Input and measurements. The choice is
done by configuration.
Following information in MiCOM C264 configuration are used to manage SOE file:

• For each SCADA protocol

− A flag indicating if SOE file have to be managed

− Identification of the SOE file on the link (Name, Address, …)

− The maximum size of the file

− The percentage of filling from which the MiCOM C264 will try to transmit the SOE
file

• For each BI / measurement

− A flag indicating if it must be stored in SOE

C264/EN CT/C30 Communications

Page 12/92 MiCOM C264/C264C

Rules for the SOE management are the following:

• At starting of the MiCOM C264, the SOE file is Empty

• When the SOE is full, the oldest Event is deleted and the new one is added

• As soon as the percentage of filling indicated in configuration is reached, the MiCOM

C264 tries to up-load the SOE file

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

• Reset of a group of Counters

• Reset of all Counters

• Freeze of a group of counters

• Freeze of all counters

• Read ( frozen value) of a group of Counters

• Read ( frozen value) of all Counters

3.2.4.3 Synchronisation
Depending on the configuration, MiCOM C264 can be synchronised by a SCADA.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 13/92

3.3 Slave DNP3 profile

DNP V3.00 Device Profile

Highest DNP Level Supported: Device Function:

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

Page 14/92 MiCOM C264/C264C

DNP V3.00 Device Profile

Timeouts while waiting for:

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

Count > 1 Never Always Sometimes Configurable

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

Queue Never Always Sometimes Configurable

Clear Queue Never Always Sometimes Configurable
• Select timeout: configurable (same value for all controls)
A pulse duration can be specified from Scada, for trip and close control with a transient DO.
When no value is specified, the default configured value is used.

FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICES ONLY:

Reports Binary Input Change Events when no Reports time-tagged Binary Input Change Events
Specific variation requested: When no specific variation requested:
Never Never
Only time-tagged Binary Input Change With Time
Only non-time-tagged Binary Input Change With Relative Time
Configurable to send both, one or the other Configurable (attach explanation)
(explanation below)
User option to have all Binary Input
Change Events returned as either:
• time-tagged OR
• non-time-tagged
Communications C264/EN CT/C30

MiCOM C264/C264C Page 15/92

DNP V3.00 Device Profile

Send Unsolicited Responses: Send Static Data in Unsolicited Responses:

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

User option to return all static counters in User option to select roll over:
One of the following variations: • 32 bit counters roll over at 2^32.
• 32-Bit Binary Counter • 16 bit counters roll over at 2^16
• 32-Bit Binary Counter Without Flag
• 16-Bit Binary Counter
• 16-Bit Binary Counter Without Flag
Send Multi-Fragment Responses: Yes No
Binary Input (BI) double management:
For a BI double, two binary inputs are configured, with a point address for the open contact and the
address + 1 for the close contact. All the BI double are transmitted this way.
C264/EN CT/C30 Communications

Page 16/92 MiCOM C264/C264C

3.3.1 DNP3 level 3: IMPLEMENTATION TABLE

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes (2)
(dec) (hex)
(dec) (hex)
1 0 Binary Input – All Variations 1 00,01,06,17,28
1 1 Binary Input 1 00,01,06, 17,28 129 00,17,28
1 2 Binary Input with Status 1 00,01,06,17,28 129 00,17,28
2 0 Binary Input Change - All Variations 1 06,07,08 129,130 17
2 1 Binary Input Change without Time 1
2 2 Binary Input Change with Time 1 06,07,08 129,130 17
2 3 Binary Input Change with Relative Time 1
10 0 Binary Output - All Variations 1
10 1 Binary Output
10 2 Binary Output Status 1
12 0 Control Block - All Variations (1)
12 1 Control Relay Output Block (1) 3,4,5,6 17,28 129 Request
echo
12 2 Pattern Control Block
12 3 Pattern Mask
20 0 Binary Counter - All Variations 1,7,8,9,10 00,01,06,17,28
20 1 32-Bit Binary Counter 1 00,01,06,17,28 129 00,17,28
20 2 16-Bit Binary Counter 1 00,01,06,17,28 129 00,17,28
20 3 32-Bit Delta Counter
20 4 16-Bit Delta Counter
20 5 32-Bit Binary Counter without Flag 1 00,01,06,17,28 129 00,17,28
20 6 16-Bit Binary Counter without Flag 1 00,01,06,17,28 129 00,17,28
20 7 32-Bit Delta Counter without Flag
20 8 16-Bit Delta Counter without Flag

1. Qualifier Codes (in hexa) (example of Binary Input)

Request Qualifier Response Qualifier

Range of Points (8 bits) 0 0
Range of Points (16 bits) 1 0
All Points 6 0
Count of Points (8 bits) 7 0
Count of Points (16 bits) 8 0
List of Points (8 bits) 17 17
List of Points (16 bits) 28 28
2. Qualifier Codes 17 and 28 are only available on one point, except for controls (controls can be selected/executed on one
or more points)

3. “Binary Counter - All Variations” (Object 20, Var 0):

Functions 7,8 ,9 & 10 are only available with qualifiers 06, 17 and 28
Communications C264/EN CT/C30

MiCOM C264/C264C Page 17/92

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes (2)
(dec) (hex)
(dec) (hex)
21 0 Frozen Counter - All Variations 1 00,01,06,17,28
21 1 32-Bit Frozen Counter 1 00,01,06,17,28 129 00,17,28
21 2 16-Bit Frozen Counter 1 00,01,06,17,28 129 00,17,28
21 3 32-Bit Frozen Delta Counter
21 4 16-Bit Frozen Delta Counter
21 5 32-Bit Frozen Counter with Time of
Freeze
21 6 16-Bit Frozen Counter with Time of
Freeze
21 7 32-Bit Frozen Delta Counter with Time
of Freeze
21 8 16-Bit Frozen Delta Counter with Time
of Freeze
21 9 32-Bit Frozen Counter without Flag 1 00,01,06,17,28 129 00,17,28
21 10 16-Bit Frozen Counter without Flag 1 00,01,06,17,28 129 00,17,28
21 11 32-Bit Frozen Delta Counter without
Flag
21 12 16-Bit Frozen Delta Counter without
Flag
22 0 Counter Change Event - All Variations 1 06,07,08
22 1 32-Bit Counter Change Event without
Time
22 2 16-Bit Counter Change Event without
Time
22 3 32-Bit Delta Counter Change Event
without Time
22 4 16-Bit Delta Counter Change Event
without Time
22 5 32-Bit Counter Change Event with Time 1 06,07,08 129,130 17
22 6 16-Bit Counter Change Event with Time 1 06,07,08 129,130 17
22 7 32-Bit Delta Counter Change Event with
Time
22 8 16-Bit Delta Counter Change Event with
Time
23 0 Frozen Counter Event - All Variations 1 06,07,08
23 1 32-Bit Frozen Counter Event without
Time
23 2 16-Bit Frozen Counter Event without
Time
23 3 32-Bit Frozen Delta Counter Event
without Time
23 4 16-Bit Frozen Delta Counter Event
without Time
23 5 32-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17
23 6 16-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17
23 7 32-Bit Frozen Delta Counter Event with
Time
23 8 16-Bit Frozen Delta Counter Event with
Time
C264/EN CT/C30 Communications

Page 18/92 MiCOM C264/C264C

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes (2)
(dec) (hex)
(dec) (hex)
30 0 Analog Input - All Variations 1 00,01,06,17,28
30 1 32-Bit Analog Input 1 00,01,06,17,28 129 00, 17,28
30 2 16-Bit Analog Input 1 00,01,06,17,28 129 00,17,28
30 3 32-Bit Analog Input without Flag 1 00,01,06,17,28 129 00,17,28
30 4 16-Bit Analog Input without Flag 1 00,01,06,17,28 129 00,17,28
31 0 Frozen Analog Input - All Variations
31 1 32-Bit Frozen Analog Input
31 2 16-Bit Frozen Analog Input
31 3 32-Bit Frozen Analog Input with Time of
Freeze
31 4 16-Bit Frozen Analog Input with Time of
Freeze
31 5 32-Bit Frozen Analog Input without Flag
31 6 16-Bit Frozen Analog Input without Flag
32 0 Analog Change Event - All Variations 1 06,07,08
32 1 32-Bit Analog Change Event without 1 06,07,08 129,130 17
Time
32 2 16-Bit Analog Change Event without 1 06,07,08 129,130 17
Time
32 3 32-Bit Analog Change Event with Time 1 06,07,08 129,130 17
32 4 16-Bit Analog Change Event with Time 1 06,07,08 129,130 17
33 0 0 Frozen Analog Event - All Variations
33 1 32-Bit Frozen Analog Event without
Time
33 2 16-Bit Frozen Analog Event without
Time
33 3 32-Bit Frozen Analog Event with Time
33 4 16-Bit Frozen Analog Event with Time
40 0 Analog Output Status - All Variations
40 1 32-Bit Analog Output Status
40 2 16-Bit Analog Output Status
41 0 Analog Output Block - All Variations
41 1 32-Bit Analog Output Block 3,4,5,6 17,28 129 Request
echo
41 2 16-Bit Analog Output Block 3,4,5,6 17,28 129 Request
echo
50 0 Time and Date - All Variations
50 1 Time and Date 1,2 07 (quantity=1)
50 2 Time and Date with Interval
51 0 Time and Date CTO - All Variations
51 1 Time and Date CTO
51 2 Unsynchronized Time and Date CTO
52 0 Time Delay - All Variations
52 1 Time Delay Coarse
52 2 Time Delay Fine
Communications C264/EN CT/C30

MiCOM C264/C264C Page 19/92

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes (2)
(dec) (hex)
(dec) (hex)
60 0
60 1 Class 0 Data 1 06,07,08
60 2 Class 1 Data 1 06,07,08
20,21 06
60 3 Class 2 Data 1 06,07,08
20,21 06
60 4 Class 3 Data 1 06,07,08
20,21 06
70 0 File management – All variations
70 2 Authentication Object 29 5b 129 5b
70 3 File Command Object 25,27 5b 129 5b
70 4 File Command Status Object 26,30 5b 129 5b
70 5 File Transfert Object 1,2 5b 129 5b
70 7 File Description 28 5b 129 5b
80 1 Internal Indications

81 1 Storage Object
82 1 Device Profile
83 1 Private Registration Object
83 2 Private Registration Object Descriptor
90 1 Application Identifier
100 1 Short Floating Point
100 2 Long Floating Point
100 3 Extended Floating Point
101 1 Small Packed Binary-Coded Decimal
101 2 Medium Packed Binary-Coded Decimal
101 3 Large Packed Binary-Coded Decimal
No Object (Cold Restart)
No Object (Warm Restart)
No Object (Delay Measurement
C264/EN CT/C30 Communications

Page 20/92 MiCOM C264/C264C

3.4 Slave IEC 60870-5-101 profile

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

Function or ASDU is not used

⌧ Function or ASDU is used as standardized (default)

R Function or ASDU is used in reverse mode

B Function or ASDU is used in standard and reverse mode

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

System definition

Controling station definition (Master)

⌧ Controlled station definition (Slave)

3.4.2 Network configuration

(network specific parameter, all configurations that are used are to be marked ‘X’)

⌧ Point-to-point ⌧ Multipoint-party line

⌧ Multiple point-to-point ⌧ Multipoint-star

Communications C264/EN CT/C30

MiCOM C264/C264C Page 21/92

3.4.3 Physical layer

(network specific parameter, all interfaces and data rates that are used are to be marked ‘X’)
Transmission speed (control direction)

Unbalanced interchange
CIRCUIT V24/V28 Balanced interchange
Recommended if Circuit X24/X27
Standard
> 1200 bits/s
100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s 56000 bits/s

200 bits/s ⌧ 4800 bits/s ⌧ 4800 bits/s 64000 bits/s

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

⌧ 600 bits/s ⌧ 19200 bits/s ⌧ 19200 bits/s

⌧ 1200 bits/s ⌧ 38400 bits/s

Transmission speed (monitor direction)

Unbalanced interchange
Circuit V24/V28 Balanced interchange
Recommended if Circuit X24/X27
Standard
> 1200 bits/s
100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s 56000 bits/s
200 bits/s ⌧ 4800 bits/s ⌧ 4800 bits/s 64000 bits/s

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

⌧ 600 bits/s ⌧ 19200 bits/s ⌧ 19200 bits/s

⌧ 1200 bits/s ⌧ 38400 bits/s

3.4.4 Link layer

(network specific parameter, all options that are used are to be marked ‘X’. Specify the
maximum frame length. If a non-standard assignment of class 2 messages is implemented
for unbalanced transmission, indicate the type ID and COT of all messages assigned to
class 2.)
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively
in this companion standard.
Link transmission procedure Address field of the link

⌧ Balanced transmission Not present (balanced transmission only)

⌧ Unbalanced transmission ⌧ One octet

⌧ Two octets

Structured

⌧ Unstructured

Frame length (number of bytes)

255 Maximum length L in control direction

up to 255 Maximum length L in monitor direction – configurable

C264/EN CT/C30 Communications

Page 22/92 MiCOM C264/C264C

3.4.5 Application layer

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

⌧ One octet ⌧ Two octets

Information object address

(system-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ One octet ⌧ Structured

⌧ Two octets ⌧ Unstructured

⌧ Three octets

Cause of transmission
(system-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ One octet ⌧ Two octets (with originator address)

Selection of standard ASDUs

Process information in monitor direction
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <1> := Single-point information M_SP_NA_1

⌧ <2> := Single-point information with time tag M_SP_TA_1

⌧ <3> := Double-point information M_DP_NA_1

⌧ <4> := Double-point information with time tag M_DP_TA_1

⌧ <5> := Step-position information M_ST_NA_1

⌧ <6> := Step-position information with time tag M_ST_TA_1

<7> := BitString of 32 bit M_BO_NA_1

<8> := BitString of 32 bit with time tag M_BO_TA_1

⌧ <9> := Measured value, normalized value M_ME_NA_1

⌧ <10> := Measured value, normalized value with time tag M_ME_TA_1

⌧ <11> := Measured value, scaled value M_ME_NB_1

⌧ <12> := Measured value, scaled value with time tag M_ME_TB_1

⌧ <13> := Measured value, short floating point value M_ME_NC_1

⌧ <14> := Measured value, short floating point value with time tag M_ME_TC_1

⌧ <15> := Integrated totals M_IT_NA_1

Communications C264/EN CT/C30

MiCOM C264/C264C Page 23/92

⌧ <16> := Integrated totals with time tag M_IT_TA_1

<17> := Event of protection equipment with time tag M_EP_TA_1

⌧ <18> := Packed start events of protection equipment with time tag M_EP_TB_1

⌧ <19> := Packed output circuit transmission of protection equipment with time tag M_EP_TC_1

<20> := Packed single-point information with status change detection M_PS_NA_1

<21> := Measured value, normalized value without quality descriptor M_ME_ND_1

⌧ <30> := Single-point information with time tag CP56Time2a M_SP_TB_1

⌧ <31> := Double-point information with time tag CP56Time2a M_DP_TB_1

⌧ <32> := Step-position information with time tag CP56Time2a M_ST_TB_1

<33> := Bistring of 32 bits with with time tag CP56Time2a M_BO_TB_1

⌧ <34> := Measured value, normalized with time tag CP56Time2a M_ME_TD_1

⌧ <35> := Measured value, scaled with time tag CP56Time2a M_ME_TE_1

⌧ <36> := Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1

⌧ <37> := Integrated totals with time tag CP56Time2a M_IT_TB_1

<38> := Event of protection equipment with time tag CP56Time2a M_EP_TD_1

⌧ <39> := Packed start events of protection equipment with time tag CP56Time2a M_EP_TE_1

⌧ <40> := Packed output circuit information of protection equipment with time tag CP56Time2a M_EP_TF_1

Process information in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <45> := Single command C_SC_NA_1

⌧ <46> := Double command C_DC_NA_1

⌧ <47> := Regulating step command C_RC_NA_1

⌧ <48> := Set point command, normalized value C_SE_NA_1

⌧ <49> := Set point command, scaled value C_SE_NB_1

⌧ <50> := Set point command, short floating point value C_SE_NC_1

<51> := BitString of 32 bits C_BO_NA_1

System information in monitor direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <70> := End of initialisation M_EI_NA_1

C264/EN CT/C30 Communications

Page 24/92 MiCOM C264/C264C

System information in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <100> := Interrogation command C_IC_NA_1

⌧ <101> := Counter Interrogation Command C_CI_NA_1

<102> := Read command C_RD_NA_1

⌧ <103> := Clock synchronisation command C_CS_NA_1

⌧ <104> := Test command C_TS_NB_1

<105> := Reset process command C_RP_NC_1

⌧ <106> := Delay acquisition command C_CD_NA_1

Parameter in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

<110> := Parameter of measured value, normalized value P_ME_NA_1

<111> := Parameter of measured value, scaled value P_ME_NB_1

<112> := Parameter of measured value, short floating point value P_ME_NC_1

<113> := Parameter activation P_AC_NA_1

File transfer
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <120> := File ready F_FR_NA_1

⌧ <121> := Section ready F_SR_NA_1

⌧ <122> := Call directory, select file, call file, call section F_SC_NA_1

⌧ <123> := Last section, last segment F_LS_NA_1

⌧ <124> := Ack file, ack section F_AF_NA_1

⌧ <125> := Segment F_SG_NA_1

⌧ <126> := Directory F_DR_TA_1

Special use (private range)

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <136> := Database version M_DB_NA_1

⌧ <137> := Regulating delay command C_RC_NB_1

Communications C264/EN CT/C30

MiCOM C264/C264C Page 25/92

Type identifier and cause of transmission assignments

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

Type ID Cause of transmission

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<1> M_SP_NA_1 X X X X
<2> M_SP_TA_1 X X

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

Page 26/92 MiCOM C264/C264C

Type ID Cause of transmission

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<46> C_DC_NA_1 X X X X X X X X
<47> C_RC_NA_1 X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X
<51> C_BO_NA_1 X
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1 X
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1 X X X X X
<105> C_RP_NA_1 X
<106> C_CD_NA_1 X X X
<110> P_ME_NA_1 X

<111> P_ME_NB_1 X
<112> P_ME_NC_1 X
<113> P_AC_NA_1 X
<120> F_FR_NA_1 X X X X
<121> F_SR_NA_1 X X X X
<122> F_SC_NA_1 X X X X
<123> F_LS_NA_1 X X X X
<124> F_AF_NA_1 X X X X
<125> F_SG_NA_1 X X X X
<126> F_DR_TA_1 X X

<136> M_DB_NA_1 X

<137> C_RC_NB_1 X X X X X X X X

3.4.6 Basic application functions

Station initialisation
(station-specific parameter, mark ‘X’ if function is used)

Remote initialisation

Cyclic data transmission

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Cyclic data transmission

Read procedure
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

Read procedure
Communications C264/EN CT/C30

MiCOM C264/C264C Page 27/92

Spontaneous transmission
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Spontaneous transmission

Link state between Controlling and Controlled Station

⌧ Management of the COM lost (Problem detecting on the link)

⌧ Management of the COM recovering (Problem not detecting on the link)

General interrogation
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ global

⌧ group 1 ⌧ group 7 ⌧ group 13

⌧ group 2 ⌧ group 8 ⌧ group 14

⌧ group 3 ⌧ group 9 ⌧ group 15

⌧ group 4 ⌧ group 10 ⌧ group 16

⌧ group 5 ⌧ group 11 Addresses per group have to be defined

⌧ group 6 ⌧ group 12

Counter General interrogation

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ global

⌧ group 1 ⌧ group 2 ⌧ group 3

⌧ group 4

Clock synchronisation
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Clock synchronisation

Notes: – The controlled station does not report the change of hour by
sending a clock synchronisation message (ASDU 103) to the
controlling station.
– When the controlling station send to controlled station a clock
synchronisation and if the system (includes controlled station), isn’t
synchronized by an other source: the clock synchronisation
response is positive.
– When the controlling station send to controlled station a clock
synchronisation and if the system (includes controlled station), is
synchronized by an other source: the clock synchronisation
response is negative.
C264/EN CT/C30 Communications

Page 28/92 MiCOM C264/C264C

Command transmission
(object -specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Direct command transmission

⌧ Direct set-point command transmission

⌧ Select and execute command

⌧ Select and execute set-point command

⌧ C_SE ACTTERM used

⌧ No additional definition

Short pulse duration (duration determined by a system parameter in the outstation)

Long pulse duration (duration determined by a system parameter in the outstation)

Persistent output

Transmission of integrated totals

(object -specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Mode A: local freeze with spontaneous transmission

Mode B: local freeze with counter interrogation

⌧ Mode C: freeze and transmit by counter interrogation commands

Mode D: freeze by counter interrogation command, frozen values reported

spontaneously

⌧ Counter read ⌧ General request counter

⌧ Counter freeze without reset ⌧ Request counter group 1

⌧ Counter freeze with reset ⌧ Request counter group 2

⌧ Counter reset ⌧ Request counter group 3

⌧ Request counter group 4

Parameter loading
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

Threshold value

Smoothing factor

Low limit for transmission of measured value

High limit for transmission of measured value

Communications C264/EN CT/C30

MiCOM C264/C264C Page 29/92

Parameter activation
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

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

Test procedure
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Test procedure

File transfer
(station-specific parameter), mark ‘X’ if function is used)
File transfert in monitor direction

⌧ Transparent file

Transmission of disturbance data of protection equipment

⌧ Transmission of sequences of events

Transmission of sequences of recorded analogue values

File transfer in control direction

Transparent file

Background scan
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Background scan

Acquisition of transmission delay

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

Acquisition of transmission delay

Management events priorities

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

Digitals Inputs and Analogs Inputs, management events priorities.

See: T101 standard Amendment 2 §7.2.2.2
C264/EN CT/C30 Communications

Page 30/92 MiCOM C264/C264C

3.4.7 Protocol Requirements

Class 1 data
The following types of information must be configured at the controlled station to be Class 1:
The following types of information are to be configured at the controlled station to be Class 1:

Single point information with or without time tag (on change)

Double point information with or without time tag (on change)
Step position information with or without time tag (on change)
Measured value, normalised with or without time tag (on change)
Measured value, scaled with or without time tag (on change)
Measured value, floated with or without time tag (on change)
Integrated totals with or without time tag (on change)
Time messages
All command responses (ACT_CONF, and ACT_TERM)

Class 2 data
The following types of information must be configured at the controlled station to be Class 2:

Single point information (GI scan, or BackGroundScan cycle)

Double point information (GI scan, or BackGroundScan cycle)
Step position information with or without time tag (on change)
Measured values, normalised (GI scan, or Periodic cycle, or BackGroundScan cycle)
Measured values, scaled (GI scan, or Periodic cycle, or BackGroundScan cycle)
Measured values, floated (GI scan, or Periodic cycle, or BackGroundScan cycle)
Step position values (GI scan, or BackGroundScan cycle)
Integrated totals (Counter GI scan)

3.4.8 Application Functions

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

MiCOM C264/C264C Page 31/92

Data Acquisition by Polling

The default for all analogue values shall be reporting as Class 2 data (COT=1,
periodic/cyclic, or COT = 2, BackgroundScan cyclic).
Values returned as Class 2 data do not have a time tag (since they are constantly repeated).
The controlled station may return Class 1 data in response to a Class 2 request if no Class 2
data is available and Class 1 data is awaiting transmission.
At the controlled station, if a request for Class 2 data is received and no data is available a
negative response, data not available, shall be returned to the controlling Station. The
negative response may be a fixed length frame (FC=9), which in this case is treated as a
NACK.
Normal Acquisition of Events
The default for all status changes are reported as Class 1 data (COT=3, spontaneous).
Values returned as Class 1 data shall have a time tag (either CP24Time2a, or CP56Time2a).
Status changes at the controlled station shall cause the ACD bit to be set in the next Class 1
or Class 2 data response. The controlling station shall respond to ACD set by inserting a
scan for Class 1 (spontaneous) data as the next scan.
The response to a Class 1 data request shall also have the ACD bit set if more Class 1 data
is awaiting transmission. In this case a further scan for Class 1 data shall be scheduled by
the controlling station.
Abnormal Acquisition of Events
At the controlled station, if a request for Class 1 data is received and no data is available an
error should be raised and a negative response, data not available, returned to the
controlling Station. The negative response shall be a fixed length frame (FC=9), which in
this case is treated as a NACK.
At the controlling station, if a response to a scan for Class 1 data indicates no data is
available an error shall be raised and scanning returned to Class 2 data requests.
General Interrogation
The GI return the current status information directly from the Computer database.
Time tags are not used for data items returned as part of the GI response.
The GI groups are supported so, these will be set up in the Computer configuration and each
of the (up to 16) groups shall be requested/reported individually.
Clock synchronisation
The System (including the controlled station) may have different synchronisation sources
(IRIG-B, SCADA).
When the controlling station send to controlled station a clock synchronisation and if the
system isn’t synchronized by an other source: the clock synchronisation response is
positive.
When the controlling station send to controlled station a clock synchronisation and if the
system is synchronized by an other source: the clock synchronisation response is negative.
All Class 1 data are time-tagged with:
Either the 3 bytes time-stamp (CP24Time2a), giving minutes and milliseconds within the
hour, or the 7 bytes time-stamp (CP56Time2a), giving minutes, milliseconds, hours, day,
month and year according to the Computer configuration.
The invalid bit in the time-stamp is set when the computer is not synchronised.
C264/EN CT/C30 Communications

Page 32/92 MiCOM C264/C264C

Command transmission
All control commands shall be Select before Execute, or Direct Execute.
For only the control commands: Activation termination is returned to the controlling station to
signal the end of a control sequence.
The QU field of the Qualifier of Command shall be set to zero (0), no additional definition.
Test procedure
A test command may be issued by the controlling station to ensure the availability of the
communications link and the commands subsystem.
Test commands are received at the controlled station on the active link. The controlled
station mirrors the test command, on the link from which it was received, with a cause of
transmission indicating activation confirmation.
An error response should be sent if the command is incorrect, with a cause of transmission
indicating negative activation confirmation.
3.5 Slave IEC 60870-5-104 Server profile
This companion standard presents sets of parameters and alternatives from which subsets
have to be selected to implement particular telecontrol systems. Certain parameter values,
such as the choice of “structured” or “unstructured” fields of the INFORMATION OBJECT
ADDRESS of ASDU represent mutually exclusive alternatives. This means that only one value
of the defined parameters is admitted per system. Other parameters, such as the listed set of
different process information in command and in monitor direction allow the specification of
the complete set or subsets, as appropriate for given applications. This clause summarises
the parameters of the previous clauses to facilitate a suitable selection for a specific
application. If a system is composed of equipment stemming from different manufacturers it
is necessary that all partners agree on the selected parameters.
Paragraph in grey are those which are not applicable for the IEC 60870-5-104 profile.
The selected parameters should be filled up ( ).
NOTE: In addition, the full specification of a system may require individual selection of
certain parameters for certain parts of the system, such as the individual selection
of scaling factors for individually addressable measured values.
To simplify the PID , we use the following conventions:
Not supported
Supported
3.5.1 System or device
System definition
Controlling station definition (Master)
Controlled station definition (Slave)
3.5.2 Network configuration (Network-specific parameter)
Point-to-point Multipoint-party line
Multiple point-to-point Multipoint-star
Communications C264/EN CT/C30

MiCOM C264/C264C Page 33/92

3.5.3 Physical layer (Network-specific parameter)

Transmission speed (control direction):

Unbalanced interchange Unbalanced interchange Balanced interchange

circuit V.24/V.28 circuit V.24/V.28 circuit X.24/X.27, V35
Standard Recommended if >1 200 bit/s
100 bit/s 2 400 bit/s 2 400 bit/s
200 bit/s 4 800 bit/s 4 800 bit/s
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s
56 000 bit/s
64 000 bit/s

Transmission speed (monitor direction):

Unbalanced interchange Unbalanced interchange Balanced interchange

circuit V.24/V.28 circuit V.24/V.28 circuit X.24/X.27, V35
Standard Recommended if >1 200 bit/s
100 bit/s 2 400 bit/s 2 400 bit/s
200 bit/s 4 800 bit/s 4 800 bit/s
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s
56 000 bit/s
64 000 bit/s

3.5.4 Link layer (Network specific parameter)

(Network-specific parameter, all options that are used should be filled up ( ). Specify
the maximum frame length. If a non-standard assignment of class 2 messages is
implemented for unbalanced transmission, indicate the type ID and COT of all messages
assigned to class 2.)
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively
in this companion standard.

Link transmission procedure Address field of the link

Balanced transmission Not present (balanced transmission
only)
Unbalanced transmission One octet
Two octets

Structured
Unstructured

Frame length
_255_ Maximum length L (number of bytes)
When using an unbalanced link layer, the following ASDU types are returned in class 2
messages (low priority) with the indicated causes of transmission:
C264/EN CT/C30 Communications

Page 34/92 MiCOM C264/C264C

The standard assignment of ASDUs to class 2 messages is used as follows:

Type Identification Cause of transmission

9,11,13,21 <1>

A special assignment of ASDUs to class 2 messages is used as follows:

Type Identification Cause of transmission

1,3,5 <20> to <41>
NOTE: In response to a class 2 poll, a controlled station prevent the controlling station with
ACD parameter, when there is no class 2 data available.
3.5.5 Protocol Requirements
3.5.5.1 Event
The following types of information are to be configured at the controlled station to be Event:

Single point information with or without time tag (on change)

Double point information with or without time tag (on change)
Step position information with or without time tag (on change)
Measured value, normalised with or without time tag (on change)
Measured value, scaled with or without time tag (on change)
Measured value, floated with or without time tag (on change)
Integrated totals with or without time tag (on change)
3.5.5.2 Static
The following types of information are to be configured at the controlled station to be Static:

Single point information (GI scan, or BackGroundScan cycle)

Double point information (GI scan, or BackGroundScan cycle)
Measured values, normalised (GI scan, or Periodic cycle, or BackGroundScan cycle)
Measured values, scaled (GI scan, or Periodic cycle, or BackGroundScan cycle)
Measured values, floated (GI scan, or Periodic cycle, or BackGroundScan cycle)
Step position values (GI scan, or BackGroundScan cycle)
Integrated totals (Counter GI scan)
3.5.6 Application layer
Transmission mode for application data
Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used
exclusively in this companion standard.

Common address of ASDU

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

One octet Two octets

Information object address

(System specific parameter)

One octet Structured

Two octets Unstructured
Three octets
Communications C264/EN CT/C30

MiCOM C264/C264C Page 35/92

Cause of transmission
(System-specific parameter)

One octet Two octets (with originator address)

Length of APDU
(System-specific parameter)
The maximum length of APDU is 253 (default) The maximum length may be reduced by the
system.

Configurable Maximum length of APDU per system

Selection of standard ASDUs

Process information in monitor direction
(Station-specific parameter)

<1>: = Single-point information M-SP-NA-1

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

Page 36/92 MiCOM C264/C264C

Process information in monitor direction with the Extension of time tag

(Station-specific parameter)

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

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

Process information in control direction

(station specific parameter)

<45>: = Single command C-SC-NA-1

<46>: = Double command C-DC-NA-1
<47>: = Regulating step command C-RC-NA-1
<48>: = Set point command normalised value C-SE-NA-1
<49>: = Set point command scaled value C-SE-NB-1
<50>: = Set point command, short floating point value C-SE-NC-1
<51>: = Bit-string of 32 bit C-BO-NA-1
<58>: = Single command with time tag CP56Time2a C_SC_TA_
1
<59>: = Double command with time tag CP56Time2a C_DC_TA_
1
<60>: = Regulating step command with time tag CP56Time2a C_RC_TA_
1
<61>: = Set point command normalized value with time tag CP56Time2a C_SE_TA_
1
<62>: = Set point command scaled value with time tag C_SE_TB_
CP56Time2a 1
<63>: = Set point command short floating point value with time tag C_SE_TC_
CP56Time2a 1
<64>: = Bitstring of 32 bits with time tag CP56Time2a C_BO_TA_
1

NOTE: Time tag command (ASDU 58 to 63) are managed as standard

command (ASDU 45 to 50), i.e. the time tag is not used.
System information in monitor direction
(station specific parameter)

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

Communications C264/EN CT/C30

MiCOM C264/C264C Page 37/92

System information in control direction

(station-specific parameter)

<100>: = Interrogation commands C-IC-NA-1

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

Parameter in control direction

(station specific parameter)

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

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

File transfer
(station specific parameter)

<120>: = File ready F-FR-NA-1

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

File transfer is only implemented in computer gateway.

Special use
(private range)

<136>: = Data base version M-DB-NA-1

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

Type identifier and cause of transmission assignments

(station specific parameters)

X Mark type identification/cause of transmission combinations: ‘X’ if used

Shaded boxes are not required
Blank = function or ASDU is not used
. Required in 1995 standard, suppressed in 2000.
C264/EN CT/C30 Communications

Page 38/92 MiCOM C264/C264C

Type ID Cause of transmission

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41

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

MiCOM C264/C264C Page 39/92

Type ID Cause of transmission

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41

<51> C_BO_NA_1
<58> C_SC_TA_1 X X X X X X X X
<59> C_DC_TA_1 X X X X X X X X
<60> C_RC_TA_1 X X X X X X X X
<61> C_SE_TA_1 X X X X X X X X
<62> C_SE_TB_1 X X X X X X X X
<63> C_SE_TC_1 X X X X X X X X
<64> C_BO_TA_1
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1
<105> C_RP_NA_1
<106> C_CD_NA_1
<107> C_TS_TA_1 X X X
<110> P_ME_NA_1
<111> P_ME_NB_1
<112> P_ME_NC_1
<113> P_AC_NA_1
<120> F_FR_NA_1 X X
<121> F_SR_NA_1 X X
<122> F_SC_NA_1 X X X
<123> F_LS_NA_1 X X
<124> F_AF_NA_1 X X
<125> F_SG_NA_1 X X
<126> F_DR_TA_1 X X
<136> M_DB_NA_1
<137> C_RC_NB_1 X X X X X X X X
<138> C_RC_TB_1 X X X X X X X X

• COT <45>:= Unknown Cause of Transmission

C264/EN CT/C30 Communications

Page 40/92 MiCOM C264/C264C

3.5.7 Basic application functions

Station initialisation
(Station specific parameter)

Remote initialisation

(Between Reset User ASDU’s).

Cyclic data transmission
(Station specific parameter)

Cyclic data transmission

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

Read procedure
(Station specific parameter)

Read procedure

Spontaneous transmission
(Station-specific parameter)

Spontaneous transmission

Double transmission of information objects with cause of transmission spontaneous

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

Single point information M_SP_NA_1, M_SP_TA_1, M_SP_TB_1 and

M_PS_NA_1
Double point information M_DP_NA_1, M_DP_TA_1 and M_DP_TB_1
Step position information M_ST_NA_1, M_ST_TA_1 and M_ST_TB_1
Bitstring of 32 bit M_BO_NA_1, M_BO_TA_1 and M_BO_TB_1
(if defined for a specific project)
Measured value, normalized value M_ME_NA_1, M_ME_TA_1, M_ME_ND_1 and
M_ME_TD_1
Measured value, scaled value M_ME_NB_1, M_ME_TB_1 and M_ME_TE_1
Measured value, short floating M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1
point number
Communications C264/EN CT/C30

MiCOM C264/C264C Page 41/92

General interrogation
(System or station-specific parameter)

Global
Group 1 Group 7 Group 13
Group 2 Group 8 Group 14
Group 3 Group 9 Group 15
Group 4 Group 10 Group 16
Group 5 Group 11
Group 6 Group 12 Information Object Addresses
assigned to each group must be
shown in a separate table

Counter General interrogation

(System or station specific parameter)

Global
Group 1 Group 3
Group 2 Group 4

Clock synchronisation
(Station specific parameter)

Clock synchronisation

Command transmission
(Object specific parameter)

Direct command transmission Select and execute command

Direct set point command transmission Select and execute set point
command
C-SE ACTTERM used

No additional definition
Short pulse duration (duration determined by a system parameter in the outstation)
Long pulse duration (duration determined by a system parameter in the outstation)
Persistent output

Transmission of integrated totals

(Station or object-specific parameter)

Mode A: local freeze with spontaneous.

Mode B: local freeze with counter.
Mode C: freeze and transmit by counter interrogation.
Mode D: freeze by counter interrogation command, frozen values reported.
C264/EN CT/C30 Communications

Page 42/92 MiCOM C264/C264C

Counter read General request counter

Counter freeze without reset Request counter group 1
Counter freeze with reset Request counter group 2
Counter reset Request counter group 3
Request counter group 4

Parameter loading
(Object-specific parameter)

Threshold value
Smoothing factor
Low limit for transmission of measured value
High limit for transmission of measured value

Parameter activation
(Object-specific parameter)

Act/Desactivation of persistent cyclic or periodic transmission of the addressed

object

Test procedure
(Station-specific parameter)

Test procedure

File transfer
(Station-specific parameter)
File transfer in monitor direction

Transparent file
Transmission of disturbance data of protection equipment
Transmission of sequences of events
Transmission of sequences of recorded analogue values

Only in computer gateway

File transfer in control direction

Transparent file

Background scan
(Station-specific parameter)

Background scan

Acquisition of transmission delay

(Station-specific parameter)

Acquisition of transmission delay

Management events priorities

(Station-specific parameter)

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

events priorities.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 43/92

Definition of time outs

Parameter Default Remarks Selected

value value
t0 30s Time out of connection establishment configurable
t1 15s Time out of send or test APDUs configurable
t2 10s Time out for acknowledges in case of no configurable
data messages t2 < t1
t3 20s Time out for sending test frames in case configurable
of a long idle state

Maximum range of values for all time outs: 1 to 255 s, accuracy 1 s

Maximum number of outstanding I format APDUs k and latest acknowledge

Parameter Default Remarks Selected

value value
K 12 APDUs Maximum difference receive sequence configurable
number to send state variable
W 8 APDUs Latest acknowledge after receiving w I- configurable
format APDUs

Maximum range of values k: 1 to 255 APDUs, accuracy 1 APDU

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

Parameter Value Remarks

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

RFC 2200 suite

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

Ethernet 802.3
Serial X.21 interface
Other selection from RFC 2200

3.6 Slave DNP3 (TCP/IP) profile

See Slave DNP3 Profile
C264/EN CT/C30 Communications

Page 44/92 MiCOM C264/C264C

3.7 Slave Modbus (MODICON) profile

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

Query message from Server Response message from Slave

Function code Function code
Eight-bit Data bytes Eight-bit data bytes
Error check Error check

3.7.1.1 Device address field

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

MiCOM C264/C264C Page 45/92

3.7.1.4 Error check field

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

3.7.2 Slave responses

3.7.2.1 When the slave answers
Except for broadcast messages (no response in this case), when a master device sends a
query to a slave device it expects a normal response.
One of four possible events can occur from the master’s query:

• If the slave device receives the query without communication error, and can handle
the query normally, it returns a normal response.

• If the slave does not receive the query due to a communication error, no response is
returned. The master program will process a timeout condition for query.

• If the slave receives the query, but detect a communication error [ bad CRC or framing
error for example ], no response is returned. The master program will process a
timeout condition for query.

• If the slave device receives the query without communication error, but cannot handle
it, the salve will return an exception response informing the master of the nature of the
error.
3.7.2.2 Exception Responses Codes
The exception code is sent as an 8-bit data, the range of valid codes is 1-8 in the protocol.
Supported exception responses codes are:

Code Name Meaning

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

Page 46/92 MiCOM C264/C264C

Code Name Meaning

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

3.7.3 Serial transmission mode

When messages are transmitted on standard MODBUS serial networks, each byte is sent
LSB first.
The format for each byte in MODBUS RTU mode is:

• Coding system: 8-bit binary, hexadecimal 0-9, A-F

Two hexadecimal characters contained in each 8-bit field of
the message

• Bits per Byte: 1 start bit8 data bits,

LSB sent first2 stop bits if no parity, or 1 parity bit and 1 stop
bit)

• Error Check Field: Cyclical Redundancy Check (CRC-16)

Communications C264/EN CT/C30

MiCOM C264/C264C Page 47/92

3.7.4 MODBUS Functions

MODBUS defines 24 functions, valid codes are in the range of 1-24.
3.7.4.1 Supported functions

Code Function name Supported

01 READ COIL STATUS [ identical to function code 02 ] YES
02 READ INPUT STATUS [ identical to function code 01 ] YES
03 READ HOLDING REGISTERS [ identical to function code 04 ] YES
04 READ INPUT REGISTERS [ identical to function code 03 ] YES
05 FORCE SINGLE COIL YES
06 PRESET SINGLE REGISTER YES
07 READ EXCEPTION STATUS YES
08 DIAGNOSTICS [ only sub function 0 is supported ] YES
09 PROGRAM 484 NO
10 POLL 484 NO
11 FETCH COMM. EVENT CTR. NO
12 FETCH COMM. EVENT LOG NO
13 PROGRAM CONTROLLER NO
14 POLL CONTROLLER NO
15 FORCE MULTIPLE COILS [ identical to function code 05, one point only ] YES
16 PRESET MULTIPLE REGISTERS [ identical to function code 06, one YES
point only ]

17 REPORT SLAVE ID NO
18 PROGRAM 884/M84 NO
19 RESET COMM. LINK NO
20 READ GENERAL REFERENCE NO
21 WRITE GENERAL REFERENCE NO
22 MASK WRITE 4X REGISTER NO
23 READ/WRITE 4X REGISTERS NO
24 READ FIFO QUEUE NO

3.7.4.2 General format of MODBUS functions

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

Page 48/92 MiCOM C264/C264C

A response message typically contains some of the following fields:

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

Slave Function Code Starting Starting No. of No. of CRC CRC

Address Address Address
= 01 Points (H) Points (L) (H)
(H) (L) (L)
The query message specifies the starting coil address and the quantity of coils to be read.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 49/92

Response:

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

Slave Function Code Starting Starting No. of No. of CRC CRC

Address Address Address
= 03 Points (H) Points (L) (H)
(H) (L) (L)
The query message specifies the starting register and the quantity of registers to be read.
Response:

Slave Function Byte Data Data Data Data Data Data CRC CRC
address code Count
(H) (L) (H) (L) (H) (L) (L) (H)
=
= 03 #1 #1 #i #i #nbytes/ 2 #nbytes/
<nbytes>
2

The register data in the response message are packed as two bytes per register, with the
binary contents right justified within each byte. For each register, the first byte contains the
high order bits and the second contains the low order bits.
C264/EN CT/C30 Communications

Page 50/92 MiCOM C264/C264C

Important notes:
1. If the starting address is not a point in configuration, the message will be not be
accepted, and an error exception 2 will be returned.
2. If the starting address is in configuration and if there is some “holes” (addresses not in
configuration) theses holes will be padded with the value 0
3.7.6.1 Signed normalised coding
The signed normalised coding is used to encode the 16 bits-registers. Analogue maximal
value will be coded 7FFFh (decimal value + 32767), and minimal value will be coded 8000h
(decimal value –32768).
For this mode, the gateway may now code the value on 8 to 16 bits [ low part of the register
will be used ]. But, 16 bits is normally the standard to use the full scale conversion.
Example:
in configuration the maximal value for an analogue point is +3000 and minimum value for
this analogue is 0.
That means that when the analogue is received with value 0 from the system, the gateway
will send to the SCADA the register with 8000h value. If this analogue is equal to the
maximal value +3000, the value sent to the SCADA is 7FFFh. Calculation is linear for the
coding between the min and max values.
3.7.6.2 Unsigned normalised coding
The unsigned normalised coding is used to encode the 16 bits-registers. Analogue maximal
value will be coded FFFFh (decimal value + 65535), and minimal value will be coded 0000h
(decimal value 0).
For this mode, the gateway may now code the value on 8 to 16 bits [ low part of the register
will be used ]. But, 16 bits is normally the standard to use the full scale conversion.
Example:
in configuration the maximal value for an analogue point is +3000 and minimum value for
this analogue is 0.
That means that when the analogue is received with value 0 from the system, the gateway
will send to the SCADA the register with 0h value. If this analogue is equal to the maximal
value +3000, the value sent to the SCADA is FFFFh. Calculation is linear for the coding
between the min and max values.
3.7.6.3 Natural coding
The natural coding is used to encode data without any calculation. That’s means that integer
value will be send.
Example:
if the gateway receives the value 10.xxxx, the value 0Ah will be set in the appropriate
register. The gateway receives the value –10,xxxx the value FFF6h will be coded. Sent
values are considered as signed values which are included between –32768 and +32767.
When minimum and maximum values are reached values FFF6h and FFFFh are
respectively sent.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 51/92

3.7.7 Function 05: Force Single Coil

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

Slave Function Code Point Point Force Force CRC CRC

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

Slave Function Code Point Point Force Force CRC CRC

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

Slave Function Code Point Point Force Force CRC CRC

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

Slave Function Code Point Point Force Force CRC CRC

Address Address Address Data Data
= 06 (L) (H)
(H) (L) (H) (L)
The normal response is an echo of the query, returned after the register has been preset.
NOTE: Only natural setpoints are managed by this function (no scaling is done)
C264/EN CT/C30 Communications

Page 52/92 MiCOM C264/C264C

3.7.9 Function 08: Diagnostic [Sub-function 0 only]

This request function 08 sub-function 0 is used to test the transmission.
Query:

Slave Function Code Sub Function Sub Function Data Data CRC CRC
Address code code
= 08 (H) (L) (L) (H)
(H) (L)
The query message specifies the data that will be echoed.
Response:

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

MiCOM C264/C264C Page 53/92

4. IED COMMUNICATION
4.1 Overview
Different types of IEDs are connected to a MiCOM C264 through networks using various
legacy protocols:
1. IEC 60870-5-103 (T103)
2. Modbus
3. DNP3
4. IEC 60870-5-101 (T101)
All these networks use a serial link to communicate with IEDs. As there are several serial
links on a MiCOM C264, it is possible to have:

• Different protocols running in parallel on different links

• The same protocol on several links

All these networks use a Master / Slave protocol where the MiCOM C264 is the Master. So,
there are two kinds of exchange:

• Request / reply
Master emits a request to a slave of its choice and wait for the response. Between
master and slave, only one transaction can be initiated. Then, in order to transmit the
same request to two different slaves, two transactions are required.

• Broadcast
Master transmits a command to all of slaves connected to the network. They perform it
without send any response.
Common features to all IEDs and all protocols are specified below in the paragraph 0
Specific features to each protocol are specified in subsequent paragraphs.
4.2 IED Common functionality
4.2.1 Interface to IEDs
4.2.1.1 Input

Data Note
Digital input Treated
Measurement Treated
Default position Depending on the protocol
Counter Treated
Tap position Treated
Control acknowledgement Treated
Setpoint acknowledgement Treated
Alarm Not Treated
Disturbance record Depending on the protocol
Tunnelling Frame response Depending on the protocol
C264/EN CT/C30 Communications

Page 54/92 MiCOM C264/C264C

4.2.1.2 Output

Data Note
Control Treated
Setpoint Depending on the protocol
Alarm acknowledgement Not Treated
Tunnelling Frame question Depending on the protocol
Time synchronisation Treated

4.2.2 Behaviour
4.2.2.1 Network supervision
The number of networks and IEDs is known by configuration.
Each network is managed independently of the other networks.
The management of a network consists of:

• Initialising the serial line

At start-up of the network monitoring, the serial line has to be initialised according to
the configuration.

• Synchronising the IEDs connected to the network.

• Polling the IEDs

This polling allows to connect IEDs, to exchange data with IEDs and to monitor the
connection of IEDs.

• Performing the monitoring of the each IED connected to this network.

Each IED is managed independently of the other IEDs. The state of each IED, i.e.
connected, disconnected, is monitored and every change of state is signalled to the
MiCOM C264 management function.
4.2.2.2 Time synchronisation
If the network has to be synchronised, the synchronisation is performed in one of two ways:
1. At connection of an IED, a synchronisation frame is sent to this IED.
2. Regularly, a synchronisation frame is broadcasted on the network.
When this is supported by the IEDs, the calculation of the transmission delay is performed.
NOTE: The synchronisation is a network attribute [not an IED attribute]. That means, that
the synchronisation is either sent to all the IEDs, or is not sent.
4.2.2.3 Polling of IED
Once the line is initialised, the MiCOM C264 has to try to connect IEDs and to manage
exchanges of data with each IEDs.
That’s done by polling: cyclically the MiCOM C264 questions each IED one after the other.
The polling manages the following items:

• Sequencing the questioning of the IEDs

• Connection of an IED [when a disconnected IED responds, it becomes Connected]

• Repetitions [if an IED doesn’t answer to a request, this request will be repeated the
next cycle]

• Disconnection of an IED [after N questions without answer, an IED becomes

Disconnected]

• Maximum time to wait for a response

Communications C264/EN CT/C30

MiCOM C264/C264C Page 55/92

• Minimum time between two frames on the network

• Sending functional requests to IEDs

Optimisation of polling may be done according to the followings ideas:

• When an IED is disconnected, it may be questioned only time to time [not all cycles]

• When an IED has important data to transmit [DI], it may be questioned successively
several times

• The maximum time to wait an answer may be configurable

The polling sequencing may be only stopped in the two following cases:

• Time synchronisation
Synchronisation is done periodically by sending a broadcast frame. After the
synchronisation frame has been sent, the polling starts again.

• Remote control to transmit to a slave

Control is a priority request. So, when a control must be sent to an IED, the polling is
stopped, the control is sent and the polling starts again.
4.2.2.4 Monitoring of an IED
Each IED is managed according to the following graph:

NOT_
INITIALISED
1
DISCON-
2
NECTED
2
1

CONNECTED
NOT_SYNCHRONISED

12
3 4

IN_SERVICE
5 OUT_OF_
GI
SERVICE
6 7

NORMAL
10 8

11 9 DISTUR-
TUNNELING BANCE

C0109ENa

Description of the possible states of an IED:

• NOT_INITIALISED: That’s the initial state of an IED. The MiCOM C264 polls the IED
every cycle in order to connect it.
If the IED responds, it becomes CONNECTED 2 .
If after some attempts the IED doesn’t respond, it becomes DISCONNECTED 1 .

• DISCONNECTED: The IED is disconnected. The MiCOM C264 polls the IED time to
time in order to connect it.
If the IED responds, it becomes CONNECTED 2 .
C264/EN CT/C30 Communications

Page 56/92 MiCOM C264/C264C

• CONNECTED: The IED is connected. This state includes several states. When an IED
becomes Connected, it goes to the NOT_SYNCHRONISED state.

• NOT_SYNCHRONISED: The IED has just became Connected. It must be

synchronised. Once it is synchronised, according to the information given by the IED,
it becomes IN_SERVICE 3 or OUT_OF_SERVICE 4 . (This information isn’t
available for some protocols. In this case, the IED becomes IN_SERVICE by default).

• OUT_OF_SERVICE: The IED is connected and says it is Out of service. The MiCOM
C264 polls the IED time to time waiting for the IED to become IN_SERVICE 5 .

• IN_SERVICE: The IED is connected and it says it is In Service. This state includes
several states. When an IED becomes In Service, it goes to the GI state.

• GI: The IED is In Service and a General Interrogation is going on.

For each information received during the GI, the information becomes available and its
state is transmitted to the application [see below for more information on GI
treatment].
At the end of the GI, the IED goes in the NORMAL state 6 .

• NORMAL: The IED is In Service and the monitoring of DI, AO and DO are performed.
If a disturbance record becomes present and the MiCOM C264 have enough places to
store the file, the IED goes in the DISTURBANCE state 8 .
If a request to open a tunnel for the IED arrives, it is accepted and the IED goes in the
TUNNELING state 10 .
Time to Time, a GI may be done. In this case the IED goes in the GI state 7 .

• DISTURBANCE: The IED is In Service and a disturbance record is being uploaded.

When the uploading of the disturbance file is finished, the IED goes back in the
NORMAL state 9 .

• TUNNELING: Tunnelling communication is going on.

When the Tunnelling communication is finished, the IED goes back in the NORMAL
state 9 .
That shows that GI, Disturbance uploading and tunnelling are mutually exclusive. That is
done for 2 reasons:

• To limit the overload of the network

• To suppress interaction between Tunnelling access and MiCOM C264 access.

Description of the transitions between states:

• 0: Initialisation of the transmission.

• 1: The IED becomes DISCONNECTED.

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

• 2: The IED becomes CONNECTED.

A synchronisation frame is sent to it and after, the status of the IED is red.

• 3: The status of the IED is indicates the IED is In Service.

A General Interrogation is activated.

• 4: The status of the IED is indicates the IED is Out Of Service.

• 5: see 3

• 6: The general Interrogation is finished.

• 7: A general Interrogation is activated [cyclical GI].

• 8: A disturbance file is available in the IED and there are enough places to store it in
the MiCOM C264.
A disturbance uploading is activated.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 57/92

• 9: End of disturbance file upload.

• 10: A request to open a communication channel throw tunnelling is received.

• 11: End of tunnelled communication.

• 12: Request to send a control command to the IED.

The polling is interrupted and the command is sent as soon as possible.
Initialisation procedure
Initially, all data normally received from an IED is marked as unknown. When an IED is first
connected, a general interrogation request is sent. A table is updated with data received in
response to the general interrogation. When the general interrogation is finished, the content
of the table is sent to the processing functions: binary inputs processing and measurement
treatment. Messages received subsequently are checked against the content of the table
and a change of state message is sent when there is a difference.
General interrogation
A general interrogation is performed:

• at initialisation time

• upon reconnection

• Cyclically [optional]
Messages received during the initial general interrogation are not sent to the processing
function. Instead the content of the table is sent at the end of the sequence.
Messages received during a general interrogation performed after the initialisation sequence
are sent immediately to the processing function
Some IEDs send a message indicating the end of the response to a general interrogation.
When this message is received, the sequence is considered as finished. If the IED does not
send this message, the MiCOM C264 must check that all data are received.
If all data are not received within a given time another request is sent. This process can be
repeated N times. If the response is still not received after N times a fault message is sent,
however the IED is still polled.
Disturbance File Management
The following rules apply for the management of the Disturbance Files of the IED:

• For each IED, there is an information in the configuration indicating if automatic upload
of Disturbance File has to be done. This indication may be overwritten by a command
from the application.

• When the MiCOM C264 detects that an IED has a Disturbance File ready to be
uploaded and that automatic upload is enabled, it uploads and stores it. When the
upload is finished, an indication is sent to the Upper transmission management to
inform it that a Disturbance file is ready.

• When there isn’t enough places to store a Disturbance File, the oldest file is deleted.

• The upper transmission management can only get Disturbance files stored in the
MiCOM C264. Once the upper transmission management has treated a file it is
deleted.
C264/EN CT/C30 Communications

Page 58/92 MiCOM C264/C264C

4.2.3 Data received from IEDs

After the initialisation sequence, IEDs are polled regularly. Depending on the type of IED the
current state of data can be received as state messages, or as change of state messages.
When a state message is received, the content is checked against the table and if there is a
difference a message is sent to processing functions and the table is updated. In this case,
the MiCOM C264 time stamps the change.
When a change of state message is received, the table is updated and the message is
transmitted to processing functions. In this case, the time stamping is made by the IED.
The data, which can be received from IEDs, are detailed in the paragraphs below.
4.2.3.1 Digital inputs
Digital inputs can be received as states or as changes of state. The choice between state
and change of state depends on the IED and on the protocol. This is known by configuration.
Even if digital inputs are received as change of state, it is still possible to request data as
states for general interrogations.
The conversion from digital input to binary input is performed by the binary input processing
function. A digital input can be associated with a single point or a double point.
4.2.3.2 Measurements
Measurements can be received in various formats: float, binary, BCD, etc. The received
value is converted into an internal format, which is common to all measurements in the
MiCOM C264.
Measurements can be received as periodical messages or as changes of state: variation,
threshold, and invalidity.
A message is sent to the processing function whenever a measurement is received from an
IED.
4.2.3.3 Counters
Counters are treated for DNP3.0
4.2.3.4 Tap position
Tap position are treated like measurements
4.2.3.5 Disturbance File
MiCOM C264 stores disturbance files as they are sent by IEDs without control of the format
of the Disturbance Files (Comtrade, …).
4.2.4 Data sent to IEDs
After the initialisation sequence, data can be sent to IEDs. The type of data, which can be
sent to IEDs, is described in subsequent paragraphs.
4.2.4.1 Controls
Controls are priority message. The polling sequence must be interrupted in order to send the
control as soon as possible.
Not all IEDs send control acknowledgement. If they do not, an acknowledgement is
simulated and sent to the handling of control sequences function.
When an IED is disconnected [or out of service] a negative acknowledgement is sent.
If the command is a “select before operate” command, the application must send two
commands to the transmission software: the first one for the selection and the second for the
execution.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 59/92

If the command is a double command, the application send one order, and depending on the
protocol, two cases have to be distinguished:

• The Double command is referenced only once in the IED Mapping. In this case, if an
OPEN (respectively CLOSE) command is received from the application, the master
send an OFF (respectively ON) order to the IED at the corresponding address.

• The double command is referenced by two addresses in the IED Mapping: one refers
to the Open Contact and the other to the Close Contact. In this case, if an OPEN
(respectively CLOSE) command is received from the application, the master sends an
ON order to the IED, at the address corresponding to the Open Contact (respectively
Close Contact).
4.2.4.2 Setpoints
SP controls are priority message. The polling sequence must be interrupted in order to send
the SP control as soon as possible.
Not all IEDs send SP control acknowledgement. If they do not, an acknowledgement is
simulated and sent to the handling of SP control sequences function.
When an IED is disconnected [or out of service] a negative acknowledgement is sent.
If the SP commands are always "direct execute" command (no “select before operate”).
For an IED, only one SP command is possible at a time.
4.2.5 Tunnelling
The serial tunnelling enable to connect a lap top computer – which run an IED setting
software – to a serial (RS232) line of the PACiS computer in order to communicate with an
IED connected to a legacy bus of the PACiS computer.

C264
Lap Top IED
Computer

RS232 link Legacy bus

dedicated to (Modbus, T103)
serial tunneling
C0149ENa

All serial RS232 lines of the computer – including the port onto the front panel – can be used
for serial tunnelling.
The choice of the serial line to be used for serial tunnelling is done by the computer
configuration.
The cable dedicated to tunnelling must be disconnected from the front panel when
tunnelling is not used.
4.2.5.1 Interface through the tunnelling serial line
The tunnelling serial line gives access to a user dialog.
This dialog enables an user to give commands to the Tunnelling RS232 software.

Commands are ASCII string terminated by ‘↵’ (code ASCII 13H) and are case sensitive.

A command is executed at the reception of the ‘↵’ character. An ASCII message is sent in
response, and a prompt message may be sent in order to indicate the computer is ready to
treat a new command.
If a command is unknown, an error message “Unknown command !” is sent.
C264/EN CT/C30 Communications

Page 60/92 MiCOM C264/C264C

List of the available commands:

• TunRSLines↵: List the legacy lines for which tunnelling is enabled.

Each line of the list corresponds to a legacy line for which tunnelling is enabled and have the
following format:
Line <line Number>: <Protocol>
If there is not any legacy line available for Tunnelling, the response is “No line available for
serial tunnelling.”

• TunRSIed nl↵: List the IED of a legacy line and their state [ln = line number].
The first line of the response gives information on the line:
Line <line Number>: <Protocol>
Each following line of the response corresponds to an IED and have the following format:
IED <Address>: <State>
Where <State> can be “available” or “not available”
If the line isn’t available for Tunnelling, the response is “The line nl is not available for serial
tunnelling.”

• TunRSStart ln, ad↵: Start a serial tunnelling session with the specified legacy line
[ln = legacy line number; ad = IED address].
The response is either “Serial Tunnelling started” or an error message explaining why the
command can’t be executed.
If the response is “Serial Tunnelling started”, legacy frames are awaited on the serial
Tunnelling link.

• TunRSStop↵: Stop the current serial tunnelling session.

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

• Connect a LapTop to the computer with a RS232 serial cable

(On the computer, the cable is connected to the serial line dedicated to the tunnelling)

• Launch Hyperterminal on the LapTop

• Enter the serial tunnelling starting command [“TunRSStart”]

The computer answers “Serial Tunnelling started”.

• Quit Hyperterminal (be sure to close the connection)

• Launch an IED setting Software [e.g.: MiCOM S1] on the LapTop

• Execute settings actions with the setting Software (that implies exchange of legacy
frames between the setting software and the IED through the computer)

• Quit the setting Software

• Launch Hyperterminal on the LapTop

Communications C264/EN CT/C30

MiCOM C264/C264C Page 61/92

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

The computer answers “Serial Tunnelling stopped”.

• Quit Hyperterminal (be sure to close the connection)

4.2.5.4 End of a serial tunnelling session
As described above, a serial tunnelling session may be ended by the “TunRSStop”
command.
If the user forgets to end the tunnelling session with the “TunRSStop” command, the session
will be automatically ended after expiry of a deadline - of about 2 minutes - without
exchange.
4.2.5.5 Fault case behaviours

• If the questioned IED does not answer, no frame of answer is returned to the setting
Software.

• If the setting software sends a new question frame [or repeats the last frame] whereas
the computer is still awaiting the answer from the IED, this new frame is ignored.
4.2.5.6 Serial tunnelling through a modem

Modem Lap Top

C264
Modem IED
Computer

Specialised
or RTC line RS232 link
Legacy bus
dedicated to serial
(Modbus,
tunneling
T103)

C0150ENa

If modems are well configured, this operating mode is transparent for the computer and no
specific management is needed in the software.
4.2.5.7 Tunnelling limits and Performances
The legacy protocols supported [protocols for which serial tunnelling is available] are the
following:

• MODBUS

• T103
The line to be used for serial tunnelling can be set through computer configuration.
If The serial tunnelling line is “frontal RS232”, it’s automatically configured:
19200Bd, 8 bits data, no parity, 1 stop bit.
For the other ports (COM1 to COM4), it follows the configuration parameters.
Only RS232 mode is supported.
C264/EN CT/C30 Communications

Page 62/92 MiCOM C264/C264C

4.2.6 Limits and Performances

• The number of serial links available limits the number of legacy network that can be
managed simultaneously by a MiCOM C264.

• The maximum number of IED that can be managed for a network is 16.

• Performance depends on the protocol used and on the number of IEDs connected to
each Network.
4.3 MODBUS communication
4.3.1 Finality
MODBUS is a legacy bus master/slave protocol that is used by many devices such as
relays, MiCOM C264s or monitoring devices. The aim of this chapter is not to describe the
protocol itself and its mechanisms (other documents and norms are there for that) but to give
the specificity of the functions that will be implemented in the MiCOM C264. These are the
MODBUS function numbers that will be used, the way in which each type of data will be
internally or externally updated, the general mechanisms used for the time synchronisation
and the configuration needs.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master Modbus” in the MiCOM C264.
4.3.2 Interface to IEDs
The following MODBUS functions are implemented in the MiCOM C264:

Function
Sub-code Used for Commentary
number
1–2 / Read DIs Read N bits
3–4 / Read DIs / MEAS / Read N words
Disturbance files
5 / Write CO Write 1 bit
15 / Write CO Write N bits
This function could be used with the
following restriction: you can only write
COs one after the other.
7 / Polling Read status byte
This function is used for detecting a DI
change of state, the presence of
disturbance files (Areva IEDs)
8 0 Polling Echo
This function could be used for
detecting if a device is connected or
not.
6 / Eventually for Write 1 word
tunnelling
16 / Eventually for Write N words
tunnelling
Communications C264/EN CT/C30

MiCOM C264/C264C Page 63/92

4.3.3 Behaviour
4.3.3.1 Polling
During a polling procedure, each slave is polled one after the other. This means that the
master waits for the answer to a request sent to a device before sending a new request to
the same or an other device.
There will be 2 types of polling:

• the polling performed by the application for the measurements and the digital inputs

• a low level polling used for detecting if a device is present or not.

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

Page 64/92 MiCOM C264/C264C

4.3.5 Data sent to IEDs

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

MiCOM C264/C264C Page 65/92

4.4 DNP 3.0 Communication

4.4.1 Finality
The purpose of this chapter is not to describe the DNP3 protocol but to specify the use of the
DNP3 protocol on a legacy bus of the MiCOM C264.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master DNP3” in the MiCOM C264.
Here are described:

• Specific behaviours attached to the protocol DNP3

• Restriction and enhancement

• Part of the DNP3 protocol used and not used

4.4.2 Interface to IEDs
4.4.2.1 Input

Object Variation Data GI Polling Function

01 0 Static BI ♦ [1] READ
02 0 BI Event ♦ [1] READ
20 0 Static Counter ♦ [1] READ
22 0 Counter Event ♦ [1] READ
30 0 Static Measurement ♦ [1] READ
32 0 Measurement Event ♦ [1] READ
60 01 Class 0 ♦ [1] READ
60 02, 03, 04 Class 1,2,3 ♦ [1] READ

NOTE: BI, Measurement and Counter are polled with the variation 0. That means
that all variations are required.
All other DNP3 objects are not treated.
4.4.2.2 Output

Object Variation Data Function Note

12 01 Command: Control [3] SELECT Treated
Relay Output Block
[4] OPERATE Treated
[5] DIRECT OPERATE Treated
[4] OPERATE Treated
[5] DIRECT OPERATE Treated
50 01 Time and Date [2] WRITE Treated

The DNP3 Master manages both direct control Command and Select before Operate for
digital control only.
When operate command is received from application, the Master checks in database to
know if the command is:
1. An execute command, which belongs to a SBO Control: OPERATE function is used in
this case.
2. A direct control: DIRECT OPERATE function is used is this case
C264/EN CT/C30 Communications

Page 66/92 MiCOM C264/C264C

4.4.3 Behaviour

• Synchronisation:

− The “Master DNP3” is always synchronised by the MiCOM C264. No calculation of

the transmission delay is performed.

− The DNP3 object used to synchronise IEDs is “Write Date and Time Request
(Object 50, Variation 01).

− Synchronisation is performed first at connection of an IED.

− Then, synchronisation is sent cyclically to all the IEDs.

• Initialisation:

− To connect an IED, a “Reset CU” (function 0) frame is sent to the IED.

− When the response is OK, the Master DNP3 send a message to the application to
tell that connection step is passed.

− Next step is General Interrogation

• General Interrogation:

− When the IED is connected, the MiCOM C264 ask for static data state and value with
a sequence of:

− Read BI,

− Read Measurement,

− Read TPI,

− Read Counter

− This Sequence is the General Interrogation. Next step is Polling

• Polling:

− The polling cycle depends on the configuration:

− Poll BI, Poll Measurement, Poll counter, Poll BI ….

− Poll C1, Poll C2, Poll C3, Poll C1 …

− The polling cycle must be interrupted at minimum in the two following case:

− Clock Synchronisation

− Remote control

• Event acquisition:

− Event occurs spontaneously. The slave device waits for being polled by the master.

• IED monitoring:

− A General Interrogation may be done after connection of an IED

Communications C264/EN CT/C30

MiCOM C264/C264C Page 67/92

4.4.4 Data received from IEDs

• Digital inputs:

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

identify the type of data.

− Digital inputs which are received as changes of state are identified by the DNP3
object number 02

− Digital inputs which are received as static data are identified by the DNP3 object
number 01

• Measurements:

− A Measurement is identified by an Index, associated to a couple “Object +

Variation” which identify the type of data.

− Both analogue and numeric measurements are treated

− Measurements which are received as changes of state are identified by the DNP3
object number 32

− Measurements which are received as static data are identified by the DNP3 object
number 30

• Counters:

− A Counter is identified by an Index, associated to a couple “Object + Variation”

which identify the type of data.

− Counters which are received as changes of state are identified by the DNP3
object number 22

− Counters which are received as static data are identified by the DNP3 object
number 20
4.4.5 Data sent to IEDs

• Controls:

− A Control is identified by an Index, associated to a couple “Object + Variation”

which identify the type of data.

− In case of basic control (Set, Reset, Trip, Close), DNP3 object 12 is used with the
Variation 01
C264/EN CT/C30 Communications

Page 68/92 MiCOM C264/C264C

4.4.6 Master DNP3.0 Profile

DNP V3.00 Device Profile

Vendor Name: AREVA T&D

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

Configurable If ’Configurable’, how?

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

Configurable If 'Configurable', how? ____________________________________________

Communications C264/EN CT/C30

MiCOM C264/C264C Page 69/92

DNP V3.00 Device Profile

Timeouts while waiting for:

Data Link Confirm None Fixed at 3s _ Variable Configurable
Complete Appl. Fragment None Fixed at ___ Variable Configurable
Application Confirm None Fixed at ___ Variable Configurable
Complete Appl. Response None Fixed at ___ Variable Configurable

Others
______________________________________________________________________________
Attach explanation if 'Variable' or 'Configurable' was checked for any timeout
Sends/Executes Control Operations:
WRITE Binary Outputs Never Always Sometimes Configurable
SELECT/OPERATE Never Always Sometimes Configurable
DIRECT OPERATE Never Always Sometimes Configurable
DIRECT OPERATE - NO ACK Never Always Sometimes Configurable

Count > 1 Never Always Sometimes Configurable

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

Queue Never Always Sometimes Configurable

Clear Queue Never Always Sometimes Configurable
• Select timeout: configurable

FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICES ONLY:

Reports Binary Input Change Events when no Reports time-tagged Binary Input Change
Events
Specific variation requested: when no specific variation requested:

Never Never
Only time-tagged Binary Input Change With Time
Only non-time-tagged Binary Input Change With Relative Time
Configurable to send both, one or the Configurable (attach explanation)
other (explanation below)

User option to have all Binary Input

Change Events returned as either:
• time-tagged OR
• non-time-tagged
C264/EN CT/C30 Communications

Page 70/92 MiCOM C264/C264C

DNP V3.00 Device Profile

Sends Unsolicited Responses: Sends Static Data in Unsolicited Responses:

Never Never
Configurable (attach explanation) When Device Restarts
Only certain objects When Status Flags Change
Sometimes (attach explanation)
ENABLE/DISABLE UNSOLICITED No other options are permitted.
Function codes supported
Default Counter Object/Variation: Counters Roll Over at:
No Counters Reported No Counters Reported
Configurable (explanation below) Configurable (explanation below)
Default Object _____20_______ 16 Bits
Default Variation _____02_______ 32 Bits
Point-by-point list attached Other Value _____________
Point-by-point list attached
User option to return all static counters in User option to select roll over:
one of the following variations: • 32 bit counters roll over at 2^32.
• 32-Bit Binary Counter • 16 bit counters roll over at 2^16
• 32-Bit Binary Counter Without Flag
• 16-Bit Binary Counter
• 16-Bit Binary Counter Without Flag
Sends Multi-Fragment Responses: Yes No
Communications C264/EN CT/C30

MiCOM C264/C264C Page 71/92

4.4.7 DNP.3 Level 3 IMPLEMENTATION TABLE

Underlined information in grey are not implemented

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes
(dec) (hex)
(dec) (hex)
1 0 Binary Input – All Variations 1, 22 00,01,06
1 1 Binary Input 1 00,01,06 129,130 00,01
1 2 Binary Input with Status 1 00,01,06 129,130 00,01
2 0 Binary Input Change - All Variations 1 06,07,08
2 1 Binary Input Change without Time 1 06,07,08 129,130 17,28
2 2 Binary Input Change with Time 1 06,07,08 129,130 17,28
2 3 Binary Input Change with Relative Time 1 06,07,08 129,130 17,28
10 0 Binary Output - All Variations 1 00,01,06
10 1 Binary Output
10 2 Binary Output Status 1 00,01,06 129,130 00,01
12 0 Control Block - All Variations (1)
12 1 Control Relay Output Block (1) 3,4,5,6 17,28 129 Request
echo
12 2 Pattern Control Block 5,6 17,28 129 Request
echo
12 3 Pattern Mask 5,6 00,01 129 Request
echo
20 0 Binary Counter - All Variations 1,7,8,9,10, 00,01,06
22
20 1 32-Bit Binary Counter 1 00,01,06 129,130 00,01
20 2 16-Bit Binary Counter 1 00,01,06 129,130 00,01
20 3 32-Bit Delta Counter 1 00,01,06 129,130 00,01
20 4 16-Bit Delta Counter 1 00,01,06 129,130 00,01
20 5 32-Bit Binary Counter without Flag 1 00,01,06 129,130 00,01
20 6 16-Bit Binary Counter without Flag 1 00,01,06 129,130 00,01
20 7 32-Bit Delta Counter without Flag 1 00,01,06 129,130 00,01
20 8 16-Bit Delta Counter without Flag 1 00,01,06 129,130 00,01

1. Commands must be selected/executed on one point

C264/EN CT/C30 Communications

Page 72/92 MiCOM C264/C264C

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes
(dec) (hex)
(dec) (hex)
21 0 Frozen Counter - All Variations 1 00,01,06
21 1 32-Bit Frozen Counter 1 00,01,06 129,130 00,01
21 2 16-Bit Frozen Counter 1 00,01,06 129,130 00,01
21 3 32-Bit Frozen Delta Counter 1 00,01,06 129,130 00,01
21 4 16-Bit Frozen Delta Counter 1 00,01,06 129,130 00,01
21 5 32-Bit Frozen Counter with Time of 1 00,01,06 129,130 00,01
Freeze
21 6 16-Bit Frozen Counter with Time of 1 00,01,06 129,130 00,01
Freeze
21 7 32-Bit Frozen Delta Counter with Time of
Freeze
21 8 16-Bit Frozen Delta Counter with Time of
Freeze
21 9 32-Bit Frozen Counter without Flag 1 00,01,06 129,130 00,01
21 10 16-Bit Frozen Counter without Flag 1 00,01,06 129,130 00,01
21 11 32-Bit Frozen Delta Counter without Flag
21 12 16-Bit Frozen Delta Counter without Flag
22 0 Counter Change Event - All Variations 1 06,07,08
22 1 32-Bit Counter Change Event without 1 06,07,08 129,130 17,18
Time
22 2 16-Bit Counter Change Event without 1 06,07,08 129,130 17,18
Time
22 3 32-Bit Delta Counter Change Event 1 06,07,08 129,130 17,18
without Time
22 4 16-Bit Delta Counter Change Event 1 06,07,08 129,130 17,18
without Time
22 5 32-Bit Counter Change Event with Time 1 06,07,08 129,130 17,18
22 6 16-Bit Counter Change Event with Time 1 06,07,08 129,130 17,18
22 7 32-Bit Delta Counter Change Event with
Time
22 8 16-Bit Delta Counter Change Event with
Time
Remarks:
Frozen counters (type21) are uploaded during general interrogation, but never polled after this.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 73/92

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes
(dec) (hex)
(dec) (hex)
23 0 Frozen Counter Event - All Variations 1 06,07,08
23 1 32-Bit Frozen Counter Event without 1 06,07,08 129,130 17,18
Time
23 2 16-Bit Frozen Counter Event without 1 06,07,08 129,130 17,18
Time
23 3 32-Bit Frozen Delta Counter Event 1 06,07,08 129,130 17,18
without Time
23 4 16-Bit Frozen Delta Counter Event 1 06,07,08 129,130 17,18
without Time
23 5 32-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17,18
23 6 16-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17,18
23 7 32-Bit Frozen Delta Counter Event with
Time
23 8 16-Bit Frozen Delta Counter Event with
Time
30 0 Analogue Input - All Variations 1 00,01,06
30 1 32-Bit Analogue Input 1 00,01,06 129,130 00,01
30 2 16-Bit Analogue Input 1 00,01,06 129,130 00,01
30 3 32-Bit Analogue Input without Flag 1 00,01,06 129,130 00,01
30 4 16-Bit Analogue Input without Flag 1 00,01,06 129,130 00,01
31 0 Frozen Analogue Input - All Variations
31 1 32-Bit Frozen Analogue Input
31 2 16-Bit Frozen Analogue Input
31 3 32-Bit Frozen Analogue Input with Time
of Freeze
31 4 16-Bit Frozen Analogue Input with Time
of Freeze
31 5 32-Bit Frozen Analogue Input without
Flag
31 6 16-Bit Frozen Analogue Input without
Flag
32 0 Analogue Change Event - All Variations 1 06,07,08
32 1 32-Bit Analogue Change Event without 1 06,07,08 129,130 17,18
Time
32 2 16-Bit Analogue Change Event without 1 06,07,08 129,130 17,18
Time
32 3 32-Bit Analogue Change Event with 1 06,07,08 129,130 17,18
Time
32 4 16-Bit Analogue Change Event with 1 06,07,08 129,130 17,18
Time
33 0 0 Frozen Analogue Event - All Variations
33 1 32-Bit Frozen Analogue Event without
Time
33 2 16-Bit Frozen Analogue Event without
Time
33 3 32-Bit Frozen Analogue Event with Time
33 4 16-Bit Frozen Analogue Event with Time
40 0 Analogue Output Status - All Variations 1 00,01,06
40 1 32-Bit Analogue Output Status 1 00,01,06 129,130 00,01
40 2 16-Bit Analogue Output Status 1 00,01,06 129,130 00,01
C264/EN CT/C30 Communications

Page 74/92 MiCOM C264/C264C

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual
Func Codes Qual Codes
Obj Var Description Codes Codes
(dec) (hex)
(dec) (hex)
41 0 Analogue Output Block - All Variations 3,4,5,6 17,28 129 Request
echo
41 1 32-Bit Analogue Output Block 5,6 17,28 129 Request
echo
41 2 16-Bit Analogue Output Block 5,6 17,28 129 Request
echo
50 0 Time and Date - All Variations
50 1 Time and Date 2 07 (quantity=1)
50 2 Time and Date with Interval
51 0 Time and Date CTO - All Variations
51 1 Time and Date CTO 129,130 07
(quantity=1)
51 2 Unsynchronized Time and Date CTO 129,130 07
(quantity=1)
52 0 Time Delay - All Variations
52 1 Time Delay Coarse 129,130 07
(quantity=1)
52 2 Time Delay Fine 129,130 07
(quantity=1)
60 0
60 1 Class 0 Data 1 06,07,08
60 2 Class 1 Data 1 06,07,08
20,21,22 06
60 3 Class 2 Data 1 06,07,08
20,21,22 06
60 4 Class 3 Data 1 06,07,08
20,21,22 06

70 1 File Identifier
80 1 Internal Indications 2 00 (index=7 ou
index=4)
1 00,01
81 1 Storage Object
82 1 Device Profile
83 1 Private Registration Object
83 2 Private Registration Object Descriptor
90 1 Application Identifier
100 1 Short Floating Point
100 2 Long Floating Point
100 3 Extended Floating Point
101 1 Small Packed Binary-Coded Decimal
101 2 Medium Packed Binary-Coded Decimal
101 3 Large Packed Binary-Coded Decimal
No Object (Cold Restart)

No Object (Warm Restart)

No Object (Delay Measurement

Communications C264/EN CT/C30

MiCOM C264/C264C Page 75/92

4.5 IEC 60870-5-103 Communication

4.5.1 Finality
The purpose of this chapter is not to describe the T103 but to specify the use of the T103
protocol on a legacy bus of the MiCOM C264.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master T103” in the MiCOM C264.
Here are described:

• Specific behaviours attached to the protocol T103

• Restrictions and enhancements

• Part of the T103 protocol used and not used

• Specific behaviours attached to implementation of Private Range of T103

4.5.2 Interface to IEDs
4.5.2.1 Input

ASDU Data Note

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

Page 76/92 MiCOM C264/C264C

4.5.2.2 Output

ASDU Data Note

6 Time synchronisation Treated
7 Request a GI Treated
20 Command Treated
23 … 31 Disturbance file management Treated
45 Single Command MiCOM Px3x only
46 Double Command MiCOM Px3x only
140 Read protection parameter MiCOM Px3x only
Only adress 0 which is DVICE: Device type
144 Setpoint Reg D only

4.5.3 Behaviour
4.5.3.1 Synchronisation
The “Master T103” link is always synchronised by the MiCOM C264. No calculation of the
transmission delay is performed.
4.5.3.2 Polling
To connect an IED, a “Reset CU” frame is sent to the IED.
By default an IED is polled by a “Polling C2” frame, allowing to get “non priority information”.
If an IED signals it has “priority information”, it is polled with a “Polling C1” frame.
4.5.3.3 IED monitoring
The “OUT_OF_SERVICE” state is managed. It corresponds to the “Lock of communication”
[DI 20].
A GI may be done after each end of Tunnelling session.
The MiCOM C264 may regularly look for Disturbance file presence
4.5.3.4 Tunnelling mode
During tunnelling mode, only polling C2 may be done by the MiCOM C264 [Normally, if
“priority information” is present, the remote Master may send a “polling C1 frame”].
The MiCOM C264 must spy the tunnelling exchange in order not to loose information [DI and
AI change]
For security raison, at the end of a tunnelling session, a GI is done
4.5.3.5 Station Interlocking
This functionality is only available on MiCOM P139 in private T103 range (Alstom D protocol
variant)
After GI, and only if IED is MiCOM Px3x, we send a read on MiCOM Px3x parameter adress
0 which corresponds to Device Type. If MiCOM Px3x responds with analog parameter set to
139, we activate Station Interlocking Management.
Case of local control (front panel of the MiCOM P139) with Station interlock:
As soon as a user will try to control a switchgear by the front panel, the MiCOM P139 will
send an ASDU 72 with FUN/TYP = F8h/74h in order to request to PACiS system the station
interlock conditions. PACiS system should check if the command is allowed (specific
treatment done by CONDUITE of the computer) and respond to the MiCOM P139.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 77/92

Case of remote control (from PACiS system) with Station interlock:

As soon as a user will try to control a device managed by MiCOM P139 by PACiS system
through T103 communication, the MiCOM P139 will send an ASDU 72 with FUN/TYP =
F8h/74h in order to request to PACiS system the station interlock conditions. PACiS system
should respond to the MiCOM P139 with a positive acknowledgement (checks have already
been done before)
If station Interlock is de-activated on MiCOM P139, the control of a switchgear on MiCOM
P139 by PACiS system through T103 communication is done by an EXECUTE ORDER
(selection will be refused by MiCOM P139)
4.5.3.6 REG D
The Reg D equipment manages 2 ASDU (144 and 17), for control of setpoints (144) and
setpoint value feedback (17), which is treated as a measurement in the computer. Setpoints
managed by the Reg D are "Direct Execute" only, there is no SBO management. The Reg D
setpoint command sequence is like the command sequence (ASDU20). The computer sends
the setpoint (ASDU 144), with the setpoint value, the Reg D sends its acknowledge
(ASDU1), if the acknowledge is OK, the Reg D sends the setpoint value feedback
(ASDU17).
4.5.4 Data received from IEDs
4.5.4.1 Digital inputs
An ASDU number [(1,2) in public Range],[(66,67,68,69) in private Range]
A DI is identified by a couple (Function Type, Information Number).
Digital inputs are received as changes of state.
Special DI may be managed:

− DI 20: Lock of the communication. A GI must be done when the communication is

unlocked

− DI 23 to 26: Change of configuration number

− DI which are not transmitted during a GI. For these DI, the IED signals only
change of state from OFF to ON. The MiCOM C264 must generate by itself the
change from ON to OFF.
4.5.4.2 Measurements
A Measurement is identified by:

− An ASDU Number [(3,4,9) in public range, (73,77) in private range]

− a couple (Function Type, Information Number)

− the rank of the Measurements in the ASDU

− the kind of Measurements [Current, Voltage, Power, Frequency, Other]

− the common address of ASDU

4.5.4.3 Bitstring 32-bits:
The state of the IED is identify by the ASDU 71 or 72 with couple FUN / TYP = F8h / 70h.
This ASDU describes the status of the IED (Station Interlocking active or not …)
A request to check station interlocking is identify by the ASDU 71 or 72 with couple FUN /
TYP = F8h / 74h. In this request, the couple FUN/TYP of the command to spend is defined.
4.5.4.4 Analog protection signal (ASDU 49):
Only for MiCOM Px3x, an analogue protection signal is received after GI
Only address 0 is managed. It is used to recognise MiCOM P139 in order to activate station
interlocking management.
C264/EN CT/C30 Communications

Page 78/92 MiCOM C264/C264C

4.5.4.5 Energy counter (ASDU 79):

Only for MiCOM Px3x, four energy counters are available.
Energy counters are identified by:

• An ASDU number (79) in private range

• a couple Function Type, Information number

• the rank of the counter in the ASDU

• the common address of the ASDU

Description TI VSQ COT ADR FUN INF DB0-DB4 DB5-DB9 DB10-DB14 DB15-DB19
Energy 4FH 04H 01H CAD F8H 6CH Active + Active - Reactive + Reactive -
counter

TI = Type identification
VSQ = variable structure qualifier
COT = cause of transmission
ADR = CAD = common address
FUN = function number
INF= information number
DB0-DB4 = active energy output
DB5-DB9 = active energy input
DB10-DB14 = reactive energy output
DB15-DB19 = reactive energy input
Format of the energy counter value

Value

Value

Value

S Value

IV CA CY Sequence number

S: 0 Value positive, 1 = value negative

CY: 0 = no carry, 1= carry
CA: 0 = not adjusted, 1 = adjusted
Communications C264/EN CT/C30

MiCOM C264/C264C Page 79/92

4.5.5 Data sent to IEDs

4.5.5.1 Controls
An ASDU Number and a couple (Function Type, Information Number) identify a control.
The acknowledgement of a control is to be waited as:

• A DI with the same (Function Type, Information Number) as the control and with a
‘Cause Of Transmission’ equals to ‘positive return’ or ‘negative return’ in public range

• A ASDU 45 or 46 with a ‘Cause Of Transmission’ equals to ‘end of activation OK’ or

‘en of activation KO’, or ‘deactivation OK’, or ‘deactivation KO’ in private range
4.5.5.2 Setpoints Controls:
A setpoint control is identified by an ASDU Number plus a couple (Function Type,
Information Number). In the case of the Reg D equipment the ASDU is 144.
The acknowledgement of a setpoint control is to be waited as:

• A DI (ASDU 1) with the same (Function Type, Information Number) as the control and
with a ‘Cause Of Transmission’ equals to ‘positive return’ or ‘negative return’ in public
range.

• An ASDU 17 with a ‘Cause Of Transmission’ equals to ‘Local Operation’ in public

range. The ASDU is a measurement which contains the setpoint feedback value.
4.5.5.3 Read protection parameter:
Only for MiCOM Px3x, a read of protection parameter (ASDU 140) address 0 (Device Type)
is sent to IED
The IED responds with ASDU 49 in which Device Type is set (139 if IED is a MiCOM P139
for example).
C264/EN CT/C30 Communications

Page 80/92 MiCOM C264/C264C

4.6 IEC 60870-5-101 Communication

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

Function or ASDU is not used

⌧ Function or ASDU is used as standardised (default)

R Function or ASDU is used in reverse mode

B Function or ASDU is used in standard and reverse mode

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

System definition

Controlling station definition (Master)

⌧ Controlled station definition (Slave)

4.6.2.2 Network configuration

(network specific parameter, all configurations that are used are to be marked ‘X’)

⌧ Point-to-point ⌧ Multipoint-party line

⌧ Multiple point-to-point ⌧ Multipoint-star

Communications C264/EN CT/C30

MiCOM C264/C264C Page 81/92

4.6.2.3 Physical layer

(network specific parameter, all interfaces and data rates that are used are to be marked ‘X’)
Transmission speed (control direction)

Unbalanced interchange
CIRCUIT V24/V28 Balanced interchange
Recommended if Circuit X24/X27
Standard
> 1200 bits/s

⌧ 100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s 56000 bits/s

⌧ 200 bits/s ⌧ 4800 bits/s ⌧ 4800 bits/s 64000 bits/s

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

⌧ 600 bits/s ⌧ 19200 bits/s ⌧ 19200 bits/s

⌧ 1200 bits/s ⌧ 38400 bits/s

Transmission speed (monitor direction)

Unbalanced interchange
CIRCUIT V24/V28 Balanced interchange
Recommended if Circuit X24/X27
Standard
> 1200 bits/s

⌧ 100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s 56000 bits/s

⌧ 200 bits/s ⌧ 4800 bits/s ⌧ 4800 bits/s 64000 bits/s

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

⌧ 600 bits/s ⌧ 19200 bits/s ⌧ 19200 bits/s

⌧ 1200 bits/s ⌧ 38400 bits/s

4.6.2.4 Link layer

(network specific parameter, all options that are used are to be marked ‘X’. Specify the
maximum frame length).
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively
in this companion standard.
Link transmission procedure Address field of the link

⌧ Balanced transmission Not present (balanced transmission only)

⌧ Unbalanced transmission ⌧ One octet

⌧ Two octets

⌧ Structured

⌧ Unstructured

Frame length (number of bytes)

255 Maximum length L in control direction

up to 255 Maximum length L in monitor direction – configurable

C264/EN CT/C30 Communications

Page 82/92 MiCOM C264/C264C

4.6.2.5 Application layer

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

⌧ One octet ⌧ Two octets

Information object address

(system-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ One octet ⌧ Structured

⌧ Two octets ⌧ Unstructured

⌧ Three octets

Cause of transmission
(system-specific parameter, all configurations that are used are to be marked ‘X’)

⌧ One octet ⌧ Two octets (with originator address)

Set to zero in case of no originator address.
Selection of standard ASDUs
Process information in monitor direction
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <1> := Single-point information M_SP_NA_1

⌧ <2> := Single-point information with time tag M_SP_TA_1

⌧ <3> := Double-point information M_DP_NA_1

⌧ <4> := Double-point information with time tag M_DP_TA_1

⌧ <5> := Step-position information M_ST_NA_1

⌧ <6> := Step-position information with time tag M_ST_TA_1

<7> := BitString of 32 bit M_BO_NA_1

<8> := BitString of 32 bit with time tag M_BO_TA_1

⌧ <9> := Measured value, normalized value M_ME_NA_1

⌧ <10> := Measured value, normalized value with time tag M_ME_TA_1

⌧ <11> := Measured value, scaled value M_ME_NB_1

⌧ <12> := Measured value, scaled value with time tag M_ME_TB_1

⌧ <13> := Measured value, short floating point value M_ME_NC_1

⌧ <14> := Measured value, short floating point value with time tag M_ME_TC_1

⌧ <15> := Integrated totals M_IT_NA_1

Communications C264/EN CT/C30

MiCOM C264/C264C Page 83/92

⌧ <16> := Integrated totals with time tag M_IT_TA_1

<17> := Event of protection equipment with time tag M_EP_TA_1

<18> := Packed start events of protection equipment with time tag M_EP_TB_1

<19> := Packed output circuit transmission of protection equipment with time tag M_EP_TC_1

<20> := Packed single-point information with status change detection M_PS_NA_1

⌧ <21> := Measured value, normalized value without quality descriptor M_ME_ND_1

⌧ <30> := Single-point information with time tag CP56Time2a M_SP_TB_1

⌧ <31> := Double-point information with time tag CP56Time2a M_DP_TB_1

⌧ <32> := Step-position information with time tag CP56Time2a M_ST_TB_1

<33> := Bistring of 32 bits with with time tag CP56Time2a M_BO_TB_1

⌧ <34> := Measured value, normalized with time tag CP56Time2a M_ME_TD_1

⌧ <35> := Measured value, scaled with time tag CP56Time2a M_ME_TE_1

⌧ <36> := Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1

⌧ <37> := Integrated totals with time tag CP56Time2a M_IT_TB_1

<38> := Event of protection equipment with time tag CP56Time2a M_EP_TD_1

<39> := Packed start events of protection equipment with time tag CP56Time2a M_EP_TE_1

<40> := Packed output circuit information of protection equipment with time tag CP56Time2a M_EP_TF_1

Process information in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <45> := Single command C_SC_NA_1

⌧ <46> := Double command C_DC_NA_1

⌧ <47> := Regulating step command C_RC_NA_1

⌧ <48> := Set point command, normalized value C_SE_NA_1

⌧ <49> := Set point command, scaled value C_SE_NB_1

⌧ <50> := Set point command, short floating point value C_SE_NC_1

<51> := BitString of 32 bits C_BO_NA_1

System information in monitor direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <70> := End of initialisation M_EI_NA_1

C264/EN CT/C30 Communications

Page 84/92 MiCOM C264/C264C

System information in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <100> := Interrogation command C_IC_NA_1

⌧ <101> := Counter Interrogation Command C_CI_NA_1

<102> := Read command C_RD_NA_1

⌧ <103> := Clock synchronisation command C_CS_NA_1

⌧ <104> := Test command C_TS_NB_1

<105> := Reset process command C_RP_NC_1

<106> := Delay acquisition command C_CD_NA_1

Parameter in control direction

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

<110> := Parameter of measured value, normalized value P_ME_NA_1

<111> := Parameter of measured value, scaled value P_ME_NB_1

<112> := Parameter of measured value, short floating point value P_ME_NC_1

<113> := Parameter activation P_AC_NA_1

File transfer
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ <120> := File ready F_FR_NA_1

⌧ <121> := Section ready F_SR_NA_1

⌧ <122> := Call directory, select file, call file, call section F_SC_NA_1

⌧ <123> := Last section, last segment F_LS_NA_1

⌧ <124> := Ack file, ack section F_AF_NA_1

⌧ <125> := Segment F_SG_NA_1

⌧ <126> := Directory F_DR_TA_1

Special use
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)
None
Communications C264/EN CT/C30

MiCOM C264/C264C Page 85/92

Type identifier and cause of transmission assignments

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

Type ID Cause of transmission

20 to 37 to
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45 46 47
36 41
<1> M_SP_NA_1 X X X X X
<2> M_SP_TA_1 X X X

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

Page 86/92 MiCOM C264/C264C

Type ID Cause of transmission

20 to 37 to
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45 46 47
36 41
<47> C_RC_NA_1 X X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X X
<51> C_BO_NA_1
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X
<101> C_CI_NA_1 X X X
<102> C_RD_NA_1
<103> C_CS_NA_1 X X
<104> C_TS_NA_1 X X
<105> C_RP_NA_1
<106> C_CD_NA_1

<110> P_ME_NA_1
<111> P_ME_NB_1
<112> P_ME_NC_1
<113> P_AC_NA_1
<120> F_FR_NA_1 X
<121> F_SR_NA_1 X
<122> F_SC_NA_1 X
<123> F_LS_NA_1 X
<124> F_AF_NA_1 X
<125> F_SG_NA_1 X
<126> F_DR_TA_1 X X

4.6.2.6 Basic application functions

Station initialisation
(station-specific parameter, mark ‘X’ if function is used)

Remote initialisation

Cyclic data transmission

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Cyclic data transmission

Read procedure
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

Read procedure

Spontaneous transmission
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Spontaneous transmission
Communications C264/EN CT/C30

MiCOM C264/C264C Page 87/92

Link state between Controlling and Controlled Station

⌧ Management of the COM lost (Problem detecting on the link)

⌧ Management of the COM recovering (Problem not detecting on the link)

General interrogation
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Global

Group 1 Group 7 Group 13

Group 2 Group 8 Group 14

Group 3 Group 9 Group 15

Group 4 Group 10 Group 16

Group 5 Group 11 Addresses per group have to be defined

Group 6 Group 12

Counter General interrogation

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Global

Group 1 Group 2 Group 3

Group 4

Clock synchronisation
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Clock synchronisation
Notes:

The controlled station reports the change of hour by sending a clock synchronisation message (ASDU 103) to the
controlling station.

Command transmission
(object -specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Direct command transmission

⌧ Direct set-point command transmission

⌧ Select and execute command

⌧ Select and execute set-point command

⌧ C_SE_ACTTERM used

⌧ No additional definition

Short pulse duration (duration determined by a system parameter in the outstation)

C264/EN CT/C30 Communications

Page 88/92 MiCOM C264/C264C

Long pulse duration (duration determined by a system parameter in the outstation)

Persistent output

Transmission of integrated totals

(object -specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

Mode A: local freeze with spontaneous transmission

Mode B: local freeze with counter interrogation

Mode C: freeze and transmit by counter interrogation commands

Mode D: freeze by counter interrogation command, frozen values reported

spontaneously

⌧ Counter read ⌧ General request counter

Counter freeze without reset Request counter group 1

Counter freeze with reset Request counter group 2

Counter reset Request counter group 3

Request counter group 4

Parameter loading
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

Threshold value

Smoothing factor

Low limit for transmission of measured value

High limit for transmission of measured value

Parameter activation
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

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

Test procedure
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Test procedure

File transfer
(station-specific parameter), mark ‘X’ if function is used)
File transfert in monitor direction

⌧ Transparent file

⌧ Transmission of disturbance data of protection equipment

⌧ Transmission of sequences of events

Communications C264/EN CT/C30

MiCOM C264/C264C Page 89/92

Transmission of sequences of recorded analogue values

File transfer in control direction

Transparent file

Background scan
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

⌧ Background scan

Acquisition of transmission delay

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

Acquisition of transmission delay

Management events priorities

(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)

Digital Inputs and Analog Inputs, management events priorities.

See: T101 standard Amendment 2 §7.2.2.2

4.6.2.7 Application Functions

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

Page 90/92 MiCOM C264/C264C

Normal Acquisition of Events

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

• the change of hour

• any time correction

• by sending a clock synchronisation message (ASDU 103) to the controlling station, as

Class 1 data, with a cause of transmission spontaneous (3).
The invalid bit in the time-stamp is set when the time source is not available.
Command transmission
All control commands shall be Select before Execute, or Direct Execute.
For only the control commands: Activation termination is returned to the controlling station to
signal the end of a control sequence.
The QU field of the Qualifier of Command shall be set to zero (0), no additional definition.
Communications C264/EN CT/C30

MiCOM C264/C264C Page 91/92

Test procedure
A test command may be issued by the controlling station to ensure the availability of the
communications link and the commands subsystem.
Test commands are received at the controlled station on the active link. The controlled
station mirrors the test command, on the link from which it was received, with a cause of
transmission indicating activation confirmation.
An error response should be sent if the command is incorrect, with a cause of transmission
indicating negative activation confirmation.
In the case of balanced mode, the controlled station may also send a test command to the
controlling station, to ensure the availability of the communications link as there is no polling
made by the controlling station.
C264/EN CT/C30 Communications

Page 92/92 MiCOM C264/C264C

BLANK PAGE