100% found this document useful (1 vote)
496 views5 pages

IEC 60870-5-101 Protocol Summary

International Standard IEC 60870-5 defines a protocol for transmission of information in telecontrol systems including power systems. It specifies the message frame format with fields for header, body, security and end along with details of the control field and application service data unit frame formats used for communication between master and slave devices. The standard defines 14 common application service data units for functions like single point information, measured values, integrated totals and more.

Uploaded by

daaanu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
496 views5 pages

IEC 60870-5-101 Protocol Summary

International Standard IEC 60870-5 defines a protocol for transmission of information in telecontrol systems including power systems. It specifies the message frame format with fields for header, body, security and end along with details of the control field and application service data unit frame formats used for communication between master and slave devices. The standard defines 14 common application service data units for functions like single point information, measured values, integrated totals and more.

Uploaded by

daaanu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Protocol IEC 60870-5

International Standard IEC 60870-5-101

Message Frame:

Header Body Security End


S L L S C A ASDU CS E

S Start Character = 68H


L Length of character = C + A + ASDU
C Link Control Character
A Link Address ( 0 – 2 octet )
CS Checksum = value of C + A + ASDU
E End character = 16H

Control Field ( C ):

1 FCB FCV
RES PRM Function
0 ACD DFC

RES Reserved
PRM 1 = Message from Master (initiating)
0 = Message from Slave (responding)

FCB 0,1 = Alternating bit for successive SEND/CONFIRM or REQUEST/RESPOND


services per station.
This bit is used to delete losses and duplications of information transfer.
The master terminal keeps copy of the frame bit cout per Slave Station. If an
expected reply is time out (missing) or garbaged, the the same SEND/CONFIRM
or REQUEST/RESPOND service is repeated with the same frame count bit.

FCV Frame count bit valid:


0 = alternating function of FCB bit is invalid
1 = alternating function of FCB bit is valid

SEND/NO REPLY services, broadcast messages and other transmission services


that ignore the deletion of duplication or loss of information output do not
alternate the FCB bit and indicate this by a cleared FCV bit.

DFC Data flow control:


0 = further messages are acceptable
1 = further messages may cause data overflow

Slave (responding) stations indicate to the message iniating (primary) station


that an immediate succession of a further message may cause a buffer overflow.

ACD Access Demand:


There are two classes of message data provided, namely class 1 and 2;
0 = no access demand for class 1 data transmission;
1 = access demand for class 1 data transmission.

File Data By Ruly Page 1 of 5


Protocol IEC 60870-5

Note:
Class 1 data transmission is typically used for events or for messages with high
priority.
Class 2 data transmission is typically used for cyclic transmission or for low
priority messages

Unbalance Transmission, Control Field from Master (PRM=1)

Functio Frame Type Service Function FCV


Code
No.
0 SEND/CONFIRM expected Reset of remote link 0
1 SEND/CONFIRM expected Reset of user process 0
2 SEND/CONFIRM expected Reserved for balanced transmission -
procedure
3 SEND/CONFIRM expected User data 1
4 SEND/NO REPLY expected User data 0
5 Reserved Reserved -
6–7 Reserved Reserved for special use by agreement -
8 REQUEST for access demand Expected response specifies access 0
demand
9 REQUEST/RESPOND expected Request status of link 0
10 REQUEST/RESPOND expected Request user data class 1 1
11 REQUEST/RESPOND expected Request user data class 2 1
12 – 13 Reserved Reserved -
14 - 15 Reserved Reserved for special use by agreement -

Unbalance Transmission, Control Field from Slave (PRM=0)

Functio Frame Type Service Function


Code
No.
0 CONFIRM ACK: positive acknowledgment
1 CONFIRM NACK: message not accepted, link busy
2–5
6–7 Reserved for special use by agreement
8 RESPOND User data
9 RESPOND NACK: requested data not available
10 Reserved
11 RESPOND Status of link or access demand
12 Reserved
13 Reserved for special use by agreement
14 Link service not functioning
15 Link service not implemented

ASDU frame:

Data Unit Identifier Information Object 1 Object N


T Q C CA OA IE TT …….. OA IE TT

T Type identification
Q Variable structure (Number of object)
C Cause of Transmission (1 – 2 octect)
CA Common Address CASSDU ( 1 – 2 octet )

File Data By Ruly Page 2 of 5


Protocol IEC 60870-5

OA Information Object ( 1 – 3 octet )


IE Set of information elements (
TT Time tag of information object ( 0 – 7 octet)

3 Octet Time Frame:

Lo-SEC Hi-SEC MIN

Lo-SEC Low byte of Milliseconds


Hi-SEC High byte of Milliseconds
MIN Minute

7 Octet Time Frame:

2 oct 1 oct 1 oct 1 oct 1 oct 1 oct


8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
SEC SEC I MIN S HOUR DOW DAY MON YEAR
1 2

I Invalid
S Sommertime
HOUR Hour (1 - 23)
DOW Day of week (1 – 7)
DAY Day (1 – 31)
MON Month (1 - 12)
YEAR Year (1998 = 98; 2002 = 102)

Selection of Standard ASDUs

No. Function Description Function Name


Code
1 1 Single point information M_SP_NA_1
2 2 Single point information with time tag M_SP_TA_1
3 3 Double point information M_DP_NA_1
4 4 Double point information with time tag M_DP_TA_1
5 5 Step position information M_ST_NA_1
6 6 Step position information with time tag M_ST_TA_1
7 9 Measured value, normalized value M_ME_NA_1
8 10 Measured value, normolized value with time tag M_ME_TA_1
9 11 Measured value, scaled value M_ME_NB_1
10 12 Measured value, scaled value with time tag M_ME_TB_1
11 13 Measured value, short floating point value M_ME_NC_1
12 14 Measured value, short floating point value with time tag M_ME_TC_1
13 15 Integrated totals M_IT_NA_1
14 16 Integrated totals with time tag M_IT_TA_1
15 21 Measured value, normalized value without quality M_ME_ND_1
descriptor
16 45 Single command C_SC_NA_1
17 46 Double command C_DC_NA_1
18 47 Regulating step command C_RC_NA_1
19 48 Set point command, normalized value C_SE_NA_1
20 49 Set point command, scaled value C_SE_NB_1
21 70 End of Initialization M_EI_NA_1
22 100 Interrogation command C_IC_NA_1

File Data By Ruly Page 3 of 5


Protocol IEC 60870-5

23 101 Counter interrogation C_CI_NA_1


24 103 Clock synchronisation command C_CS_NA_1

Transmission procedure

1. Balance
Di aplikasikan pada konfigurasi Point-to-point.
Setiap saat RTU dapat mengirimkan data tanpa harus menunggu di polling oleh MTU.

2. Unbalance
Di aplikasikan pada konfigurasi Point-to-multipoint.
RTU atau outstation selalu sebagai slave, master station melakukan regular poling dengan megirim
function code 11 (request data class 2). RTU akan merespon dengan data jika data class 2 tersedia
atau NACK dengan ACD = 0 bila data tidak tersedia, tetapi bila RTU memiliki data class 1 maka
RTU akan merespon dengan NACK dengan ACD=1.

Contoh Message:

CC to RTU:

10 49 03 4C 16

10 = Start of message
49 = Control Field (PRM = 1, FCB=0, FCV = 0, Function = 9, Request status link)
03 = RTU Address
4C = Checksum
16 = End of message

RTU to CC:

10 0B 03 0E 16

10 = Start of message
0B = Control Field (PRM = 0, DFC=0, ACD = 0, Function = 11, status link of link)
03 = RTU Address
0E = Checksum
16 = End of message

CC to RTU:

10 40 03 43 16

10 = Start of message
49 = Control Field (PRM = 1, FCB=0, FCV = 0, Function = 0, reset remote link)
03 = RTU Address
43 = Checksum
16 = End of message

File Data By Ruly Page 4 of 5


Protocol IEC 60870-5

RTU to CC:

E5

E5 = Single character ACK

CC to RTU:

10 7B 03 7E 16

10 = Start of message
7B = Control Field (PRM = 1, FCB=1, FCV = 1, Function = 11, request data class 2)
03 = RTU Address
43 = Checksum
16 = End of message

RTU to CC:

68 1B 1B 68 08 03 09 04 01 03 00 92 01 81 FF 00 93 01 F8 7F 00 90
01 00 00 00 91 01 61 8D 00 4B 16

68 = Start of message
1B = Character Length
1B = Character Length
68 = Start of message
08 = Control Field (PRM = 0, DFC=0, ACD = 0, Function = 8, user data)
03 = RTU Address
09 = Data type (type identification = 9, measured value, normalized value)
04 = Number of data
01 = Cause of transmission =1 ( periodic, cyclic)
03 00 = CAASDU = 3
92 01 = Object Address/Register #1
81 FF = Value #1
00 = quality of value #1
93 01 = Object Address/Register #2
F8 7F = Value #2
00 = quality of value #2
90 01 = Object Address/Register #3
00 00 = Value #3
00 = quality of value #3
91 01 = Object Address/Register #4
61 8D = Value #4
00 = quality of value #4
4B = Checksum
16 = End of message

File Data By Ruly Page 5 of 5

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy