Sport Frame

Chapter 01
SPORT PROTOCOL
Basics
Block 0:
Block ‘0’ Record
This block is used in the beginning of all frames except for single character responses.
More blocks may or may not flow this.
It is also called as “Frame”

It contains the following 5 fields
Start (27H)
Length
Control Field
Address
CRC
1>Start Address:
This number is usually 27H /14 H and it indicates the beginning of the frame.
If the frame starts with 14H it is a single character frame.
2> Length
. It specifies the number of subsequent user data octets including the control and
address octets but excluding the CRC octets.
3> Control Field
The control field contains information that characterizes the direction of the message, the
type of the service provided and supports control functions for suppressing losses or
duplications of messages
1
RES =0 PRM=1 FCB FCV FUNC TION CO DE
RES = 0 PRM=0 ACD DFC FUNC TION CO DE
8 4 2 1 8 4 2 1
If the data is sent from RCC to RTU .. The following bits are present
i> RES : = Reserved Bit. It is always 0
ii> PRM : = This is the primary message bit .

PRM =1 if message is sent from RCC to RTU
iii> FCB : = Frame Count Bit

FCB bit toggles between 1 and 0
iv> FCV: = Frame Count Valid

This bit is always 1 except for Reset.
For RESET FCV bit is always 0
Note: FC => Function Code

Remaining four parameters are function codes <FC> given below
1> For Class A Request/Response the four bits/Function Codes will be filled like this
1 0 1 0 i.e. FC = 10
2> For Class B Request/Response the four bits/Function Code will be filled like this
1 0 1 1 i.e. FC = 11
3> For RESET the four bits/Function Code will be filled like this
0 0 0 0 i.e. FC = 0
If the data is sent from RTU to RCC. The following bits are present
1> RES
This will always be 0.
2> PRM
PRM =0 if message is sent from RTU to RCC.
3> ACD
Access demand bit.
This bit is set to 1 at the RTU if an event occurs.
Then RTU sends request for Class A / Class 1 data transmission.
2
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 flow priority messages.
4> DFC
Data Flow Control: 0 = further messages are acceptable
1= further messages may cause data overflow.
5>Address
This bit contains the RTU Address
6>CRC
This contains the CRC Bit.
e.g. of Block ‘0’ 27 02 5B 02 36
Here
27 = Starting Address
02 = Length
5B = Class B request with FCB bit = 0
02 = RTU address
36 = CRC byte
NACK Record
This comes as a “Negative Acknowledgement “ from the RTU to RCC.
This record contains Type Identification <TI> apart from the Block Ò’. Different values
of TI indicate different types of negative acknowledgement. For this record the FC=9 in
control field of Block Ò’.
Block `0’
TI
CRC
3
Different types of NACK records supported in this implementation are listed below:
Sl. No. NACK Record Description Type

Identifier
( TI )
1 CRC error in received message 211=D3 H P
2 Invalid Type Identifier 212=D4 H P
3 RTU Not configured 213=D5 H P
4 No points connected 214=D6 H P
7 Invalid time downloaded to RTU 217=D7 H P
9 I/O module mismatch with down load 219=DB H P
data
10 Selected file/point not configured or out 220=DC H P
of range
11 Attempt to down load invalid pulse width 221=DD H P
13 Invalid segment size 223=DF H P
14 Cannot be configured as TSS/SP/SSP 224=E0 H P
(whichever is applicable)
15 RTU powered on 225=E1 H P
16 No Class 2 data available 226=E2 H P
17 No points of requested type connected 227=E3 H P
18 Invalid Section Number 228=E4 H P
The NACK – ‘RTU powered on’ is used to indicate that the RTU has been switched on.
This can be used by the control station to download data to RTU or get fresh set of data
from RTU. This indication should be there as long as the last section of download
parameters is not sent.
NACK Byte
This negative acknowledgement byte is returned by the RTU to RCC whenever there are
no data objects of the requested class type.
NACK byte (A2H)
e.g. A2
4
Type Identification (TI)
Type identification defines the type of message
Type identification: = <8bits> <1… 255>
27 2o
Messages with undefined values of TYPE IDENTIFICATION are acknowledged

negatively and discarded by both controlling and controlled stations.
Value <0> is not used.
The following tables show the definition of TYPE IDENTIFICATION numbers for all
packets in monitor and control direction.
<1… 127>: = as per standard definitions by6 the IEC 101 standard
<136 …. 255> : = for private range use
Process information in monitor direction
<6> := step position information with time tag for acquisition of transformer tap positions
(for future use)
<8> := Bit string of 32 bit with time tag for events acquisition
<10> = bit string of 32 bit for all events.
<11> := measured value, scaled value for acquisition of measurands
<16> := integrated totals for acquisition of integrated MD values (for future use)
Process information in Control direction
<45> := single command

<46> :=double command for control breakers
<47> := regulating step command for control of transformer taps (for future use)
System information in control direction
<103> := clock synchronization command

<104> := test command
5
File transfer
<120> := file ready

<121> := section ready
<122> := call file, call section
<123> := last section, last segment
<124> := ack file, ack section
<125> := segment
Private range
<220> := diagnostics
<201> := block RTU/controlled station (for future use)
<202> := deblock RTU/controlled station (for future use)
<203> := averaged values (for future use)
<204> := synchronization of MD integration ( for future use)
<205> := all measured values, scaled value
<206> := current value of integrated values (for future use)
Information Object Address
If the point address (DI) from 1 – 32 gets changed then

Information Object Address = 01
If the point address (DI ) from 33 – 64 gets changed then

If the point address (DI ) from 65 - 96 gets changed then


6
Seven-Octet Binary Time :
This time record is used where absolute time record is required.
This time record is used where absolute time record is required. For this implementation,
it is used for clock synchronization command. The seven octets shall contain the
following information as per the given format.
Seven octet binary time := {Milliseconds, Minutes, Reserve 1, Invalid, Hours, Reserve 2,
Summer time, Day of month, Day of week, Months, Reserve 3, Years, Reserve 4}
Bits 8 7 6 5 4 3 2 1
Octets 1 Milliseconds
7
2 20
Milliseconds
15
2 2 20
3 RES1 Minutes
5
2 20
4 SU RES2 Hours
4
2 20
5 Day of week Day of month
22 20 2 4
20
6 RES3 Months
3
2 20
(Note 1)
7 Years
7
2 20
Milliseconds := <0….59,999>
Minutes := <0… 59>
RES1 := Reserved – 1 bit
Hours := <0… 23>
RES2 = Reserved – 2 bits
SU Summer time := <0> := Standard time
<1> := Summer time (not to be used)
Day of month := <1…31>
Day of week := <1….7>
Months := <1…12>
Years := <0..99>
Note : Day of week is not used in this implementation and is set to 0
7
Note 1: The MSB bit is used to indicate the current century. `0’ in the MSB position
indicates 20th century and a `1’ indicates 21 st century. Rest of the 7 bits of the byte gives
the last two digits of the absolute year.
2.3.1 Four-octet binary time :
This record is used in all the responses except time synchronization. (for example, event
responses, transformer tap position etc.). The 4 octets shall contain the following
information as per the format given below.
Bits 8 7 6 5 4 3 2 1
Milliseconds
27 20
215 20
Minutes
5
RES1 2 20
Hours
RES2 4
2 20
Milliseconds = <0….59,999>
Minutes = <0… 59>
Hours = <0..23>
8
Chapter 02
APPLICATION SERVICES FORMAT DETAILS.
This chapter describes the various Request and Response sequences from RTU to
RSS and vice-versa.
Service Name:
a) Events in bit string of 32 bit with time tag ( events data) (10/8)
b) Measured value, scaled value (11/8)
c) Clock synchronization command (11/8)
d) Single command ( command transmission) (11/8)
e) Double command ( command transmission) (11/8)
f) Test Procedure (11/8)
g) Diagnostics (11/8)
h) All measured values, scaled values (11/8)
i) Download complete information (11/8)
j) Reset controlled station (0/0)
k) All Events in bit string of 32 bit (10/8)
9
1> Events: ( 10/8 )
When ever an event occurs RTU sets the ACD bit to 1 and sends to RCC.
Then RCC sends request for class 1 data
Request:
Block ‘0’
FC = 10 < for class 1 data >
E.g.: 27 2 7a 4 73
1> 27 => Starting Address

2> 2 => Length of the packet
3> 7a => Class A message with FCB = 1
4> 4 => Address of RTU
5> 73 => CRC Byte
Response:
Positive Response:
Block “0”
Type Identification 8
Information Object Address 1…n
Event Data Record 1…n
Four - Octet Time Record 1…n
CRC Byte
FC =8
1> Block 0
2> TI = 8 H
10
3> Information Object Address
The information object address in the packet corresponds to the starting address of
the 32-bit event data record.
4> Event Data Record:

Each event data record contains 32 bits of station information.
They correspond to status values of 32 contiguous bits.
5>Four - Octet Time Record

It is the time stamping at which an event occurred at RTU.
Negative Response:
(a) No class 1 data available to transmit
NACK byte
e.g. A2
(b) Other NACK’s possible are
NACK record
1. RTU powered on
2. RTU not configured
3. CRC error in the received message
Example of Response
E.g.
This packet is returned if DI point 1 = 0 and the DI point 2 =1 of RTU number 02
27 c 8 2 39 | 8 | 1 | 56 55 15 0 | 0 0 3 e | 26
This packet is returned if DI point 1 = 1 and the DI point 2 =0 of RTU number 02
27 c 8 2 39 | 8 | 1 | 55 55 15 0 | 0 0 3 f | 26
11
The whole packet can be divided into following six blocks:
1>Block 0:
27 => start address

c => length
8 => Control Field
2 => RTU address
39 => CRC Byte
2> Type Identification
8H
3>Information Object Address

If the point address (DI ) from 33 – 64 gets changed then



4>Event Data Record
56 55 15 0 these four bytes represent the Event Data Record
56 55 15 0 is the Event Data Record when DI point 1 = 0 and the DI point 2 =1 of

RTU number 02
55 55 15 0 is the Event Data Record DI point 1 = 1 and the DI point 2 =0 of RTU

number 02
12
One can note that there is change only in first byte of this block and remaining bytes are
same .
56 => 0 1 0 1 0 1 1 0 == DI points 8,7,6,5,4,3,2,1 respectively

55 => 0 1 0 1 0 1 0 1 == DI points 8,7,6,5,4,3,2,1. respectively
Note the highlighted bits they are only changing .
5> Four - Octet Time Record
0 0 3 e
0 0 3 f
These four bytes represent the Four - Octet Time Record <explained above>
0 => Hours
0 => Minutes
3 => Seconds
e => Milli seconds
6>CRC Byte
Here 26 is the CRC Byte
13
2> Measured Value, Scaled Value / Measurands :
(Request – Respond)
Request:
Block ‘0’
FC=11 < Class 2 >
e.g.
27 2 7b 2 3a
Response:
Positive response:
(1) Measurand values
Block “0”
Information Object Address #1..N
Measurand value #1..N
Information object address #N
CRC Byte
FC=8
1> Block 0
2> TI = 11 or b H
4> Measurand value
5> CRC Byte
14
E.g
27 b 8 2 55 || b || 1 0 2 c1 3 0 4 cb || 58
First 5 bytes are Block “0”
TI =11 = b H
1 0 => value of DI point 1 = 0
2 c1 => value of DI point 2 = 193
3 0 => value of DI point 3 = 0
4 cb => value of DI point 4 = 203
59 => CRC Byte
(2) Negative Acknowledgements
(a) NACK’s possible are
NACK record
Different NACK records are possible here are possible

1. RTU powered on
3. CRC error in received message.
4. No Class 2 data available
15
3> Clock Synchronization
Clocks at all the RTUs have to be synchronized with the clock at the RCC to provide
correct chronological sets of time-tagged events or information objects. The clocks are
initially synchronized by the RCC after system initialization and RTU initialization and
then resynchronized periodically by transmission of the `Clock Synchronization’
command.
Request :
Block Ò’
Seven Octet Time Record
1> CRC byte Block 0
2> TI = 103 = 67 H
3> Seven Octet Time Record
This time record is used where absolute time record is required.
4> CRC byte
E.g.
27 a 5b 1 36 || 67 || 75 4b 28 9 f 7 82 || e
The packets are explained as below..
27 => Starting address of the packet
a => Length of the packet
5b => this is a class 2 data with FCB bit = 0
1 => RTU address
36 => CRC Byte
67 => Type Identification = 67 H
75 4b 28 9 f 7 82 => Seven Octet Time Record < explained below>
e => CRC byte
16
The following packet is the example of Seven Octet Time Record.
Each Bit is explained as follows
75 4b 28 9 f 7 82
75 => 117 milliseconds

4b => 75 seconds
28 => 40 minutes
9=> 9 hours
f=>15 day
7=> 7th month
82 => 10000010 = MSB ………. LSB
MSB here =1 => 21st century
Remaining seven bits give 02 => 2002 year
Response :
Positive Response:
(1) Clock Synchronization confirmation
Block Ò’
CRC byte
FC=8
The Seven-Octet Time Record will contain the time of the RTU clock after
synchronization taking into account the necessary correction.
E.g
27 a 8 1 46 || 67 || 34 4c 28 9 f 7 82 || 75
The packets are explained as below..

27 => Starting address of the packet
a => Length of the packet
8 => Control Field
1 => RTU address
46 => CRC Byte
67 => Type Identification = 67 H
34 4c 28 9 f 7 82 => Seven Octet Time Record < explained below>
75 => CRC byte
17
The following packet is the example of Seven Octet Time Record.
Each Bit is explained as follows
34 4c 28 9 f 7 82
34 => 52 milliseconds
4c => 76 seconds
28 => 40 minutes
9 => 9 hours
f =>15 day
7 => 7th month
82 => 1 0 0 0 0 0 1 0 = MSB ………. LSB
MSB here =1 => 21st century

Remaining seven bits give 02 => 2002 year
(2) Negative Response:
NACK Record
Different NACK conditions possible are :

1. RTU powered on
2. CRC error in received message
3. Invalid Type Identification
4. Invalid time downloaded to RTU
4>Single Command
18
Request :
Execute Command
Block Ò’
Cause of Transmission
Single Command Operation
CRC byte
FC=11
<6> := activation confirmation
1> Block 0
2> TI = 45 => 2D H
3> Cause of Transmission = 6 H < fixed>
5> Single Command Operation
6> CRC byte
E.g
The following packet was transmitted when single command was given
27 6 7b 1 6d || 2d || 6 || 1 || 0 || 13
Here first 5 bytes are block “0”
2d => TI = 45 => 2D H
6 => Cause of Transmission = 6 H < fixed >
Here Information Object Address =1

That implies:
0=> Single Command Operation
13 => CRC byte
19
Response:
Block Ò’
CRC byte
FC=8
<10> = Termination confirmation
E.g.
The following packet is recived
27 6 28 1 1d || 2d || a || 1 || 0 || 44
2d => TI = 45 => 2D H
Cause of Transmission = a H < fixed > = 10 D = Termination confirmation

That implies:
0 => Single Command Operation
44 => CRC byte
20
Negative Acknowledgements
(a) Selected address object not available
NACK byte
(b) Other NACK conditions those are possible.
NACK record
(1) RTU powered on

(2) CRC error in the received message
(3) Invalid Type Identification
RTU not configured
21
5>Double Command
(1) Request:
Execute Confirmation
Block Ò’
Double Command Operation
CRC byte
FC=11
<6> := Activation confirmed
1> Block 0
2> TI = 46 => 2E H
3> Cause of Transmission = 6 H
5> Double Command Operation
6> CRC byte
e.g.
The following packet was transmitted when single command was given
27 6 7b 1 6d || 2e || 6 || 1 || 2 || 18
2e => TI = 46 => 2e H
6 => Cause of Transmission = 6 H < fixed >

That implies:
2=> Double Command Operation
22
18 => CRC byte
Response:
Execute Confirmation
Block Ò’
CRC byte
FC=8
<10> = Termination confirmation
E.g:
The following packet is recived
27 6 28 1 1d || 2e || a || 1 || 2 || 4f
2e => TI = 46 => 2e H
Cause of Transmission = a H < fixed > = 10 D = Termination confirmation

That implies:
2 => Double Command Operation
4f => CRC byte
23
(a) Selected address object not available
NACK byte
(b) Other NACK conditions those are possible.
NACK record
(1) RTU powered on

(2) RTU not configured
24
6> Test Procedure
Request :
Block `0’
Fixed Test Bit Pattern (byte 1)
CRC byte
FC=11
Test procedure has the following fields

1> Block 0 < as explained above>
2> Type Identification (TI) = 104 = 68 H
3> Fixed Test Bit Pattern (byte1) = 10101010 = AA
4> Fixed Test Bit Pattern (byte2) = 01010101 = 55
5> CRC byte
e.g. . 27 5 7b 1 51 68 aa 55 b
Response :
Positive Acknowledgements
Confirmation for the link healthiness
Block `0’
CRC byte
FC=8
25
NACK Record
Different NACK conditions those are possible.
(1) RTU powered on

e.g. . 27 5 7b 1 51 68 aa 55 b = Transmitted packet

27 5 8 1 2d 68 aa 55 b = Received packet
26
7>All Measured Values, Scaled value
(Request-Respond)
This request can be used to acquire all measurands in one message. The measurand
values will be sent as a sequence of values. The ordering of the sequence will be based on
the address of the measured values starting from the value corresponding to the lowest
address (say address zero).
Request :
Block `0’
CRC byte
FC=11
1> Block 0
2> TI = 205 => CD H
3> CRC
Response :
Block `0’
Measured value #1
Measured value #2
………….
Measured value #N
CRC byte
FC=8
For each of the requests, the following class of Negative Acknowledgements applies.
(2) NACK when any error is identified
NACK record
Different Negative Acknowledgements that are possible here are :

(1) RTU powered on
27
(5) No Points of the requested type connected
8>Reset controlled station

(Request-Respond)
This request is used to initialize the link of controlled station. It will be sent by control
station whenever the FCB of RTU is to be reset
Request :
Block `0’
FC=0
The Function Code of control field in Block 0 will be set to 0 to indicate that the remote
link is to be reset. The details are given in section on Frame Format.
e.g.
27 2 40 1 5a
Control Field = 40
The Bits for the Control Field will be filled like this
RES =0 PRM=1 FCB=0 FCV=0 FUNC TION CO DE
RES = 0 PRM=0 ACD=1 DFC=0 FUNC TION CO DE
8 4 2 1 8 4 2 1
FC=0
28
Response :
Block `0’
FC=0
The Function Code of the response will be set to 0 to indicate positive acknowledgement.
e.g.
27 2 20 1 4e
Control Field = 20
For each of the requests, the following class of Negative Acknowledgements applies.
(2) NACK when any error is identified
NACK record
Different Negative Acknowledgements that are possible here are :

29
9>Perform Complete Diagnostics
(Request-Respond)
The RTU, on receiving this command from the RCC, shall enter into diagnostic mode,
perform the diagnostic tests and transmit the results of the diagnostics back to the RCC.
The RTU suspends the data acquisition when the diagnostics is in progress. Any
powered-on RTU responds to this request even if it is not downloaded with configuration
data.
Request :
Block Ò’
`CRC byte
FC=11
1> Block 0
2> TI = 220 => DC H
3> CRC byte
e.g . 27 3 5b 1 25 dc 78 = transmitted packet
Response:
(1) Result of the diagnostics
Block Ò’
Type of RTU (Note 1)
Diagnostic result 1(Note 2)
Card Type (Note 4) No. of cards
Result (Note 5)
Result (Note 6)
Card Type No. of cards
Result
Result
……..
CRC byte
FC=8
Eg
30
Note 1:
b a
a) These 5 bits indicate the types of RTU
Value of <a>
0 -- Not used
1 -- TSS
2 -- SP
3 -- SSP
b) These 3 bits indicate the status of RTU

Value of <b>
0 -- normal
1 -- blocked
2 -- RTU not initialized
Note 2:
7 6 5 4 3 2 1 0
Each bit indicates the status of the device specified below. A bit set to 1 indicates error.
0 - For future use

1 - Read only memory
2 - Data bus
3 - For future use
4 - RAM check (stuck at 0)
5 - RAM check (stuck at 1)
6 - Battery low
7 - Battery backed-up RAM
The diagnostics given above will be optional and will not be a requirement for acceptance
of the system.
Note 3:
31
7 6 5 4 3 2 1 0
Each bit indicates the status of the device specified below. A bit set to 1 indicates error.
0 - Real time clock (RTC) read/write check

1 - RTC interrupt
2 - Sequential communication controller 1 loop check
3 - Transmit 1 interrupt
4 - Receive 1 interrupt
5 - Sequential communication controller 2 loop check
6 - Transmit 2 interrupt
7 - Receive 2 interrupt
The diagnostics given above will be optional and will not be a requirement for acceptance
of the system.
Note 4:
a | b
Value of <a> (card type)

0 – AI
1– DI
2 – PI
3 -AO
4 – DO
Remaining five bits are used to indicate the number of each type of cards.
Note 5:
7 6 5 4 3 2 1 0
Each bit indicates the status of the device specified above. A bit set to 1 indicates error.
(2) Negative Acknowledgements
NACK record
Different NACK conditions those are possible.
32
10>All Events Data

This request is sent to obtain the status of all the devices in the field. Whenever the host
or the RTU is coming up for the first time or after a failure it requires the status of all the
devices in the field. Hence this request is used to address that requirement. The Function
code for this request will be 10.
Request:
Block `0’
CRC byte
FC=10
Response:
Block “0”
Event Data Record
CRC Byte
FC=10
Each event data record contains 32 bits of station information. Number of event records
depends on number of points in that station. This packet will contain the status of all the
points in the RTU.
The Negative ACKs possible for this down load are :

1. RTU powered on
3. CRC error in the received message
4. Invalid Type Identification
33
ANNEXURE 1
LIST O F ABBRIVIATIONS
Abbreviation Full Form of the Abbreviation

ACD Access Demand Bit
ACK Acknowledgements
AI Analog Input
AO Analog Output
ASDU Application Service Data unit
BPS Bits Per Second
COT Cause of transmission
CRC Cyclic redundancy Check
DCE Data terminal equipment
DI Digital Input
DO Digital
DO Digital Output Output
FC Function Code
FCB Frame Count Bit
FCV Frame Count Bit Valid
FD Full Duplex
FT… Frame Format Type …. (1,2,3,1.1,1.2 etc.) Defined in IEC 870-5-2
HD Half Duplex
ITU International Telecommunication Union
MD Maximum Demand
MVA Mega Volt Ampere
NACK Negative Acknowledgements
NCP Network Core Protocol
PAI Pseudo Analog Input
34
PAO Pseudo Analog Output
PDI Pseudo Digital Input
PDO Pseudo Digital Output
PDU Protocol Data Unit
PRM Primary Message
RBE Report by Exception
RCC Remote Control Centre
RTU Remote Terminal Unit
SCADA Supervisory control and Data Acquisition System
SP Sectioning and Paralleling Post
SPORT Standardized Communication Protocol
SSP Sub sectioning and paralleling post
TI Type Identification
TSS Traction Sub Station
TVM Trivactor Meter
35
1>Events
Request:
27 2 7a 4 73
Response:
28 c 8 2 39 | 8 | 1 | 56 55 15 0 | 0 0 3 e | 26
2> Measured Value, Scaled Value / Measurands :
Request:
28 2 7b 2 3a
Response:
27 B 8 2 55 || B || 1 0 2 c1 3 0 4 cb || 58
3> Clock Synchronization
Request
29 a 5b 1 36 || 67 || 75 4b 28 9 f 7 82 || E
Response
27 a 8 1 46 || 67 || 34 4c 28 9 f 7 82 || 75
4>Single Command
Request
27 6 7b 1 6d || 2D || 6 || 1 || 0 || 13
Response
27 6 28 1 1d || 2D || a || 1 || 0 || 44
36
5>Double Command
Request
28 6 7b 1 6d || 2E || 6 || 1 || 2 || 18
Response
27 6 28 1 1d || 2E || A || 1 || 2 || 4f
6> Test Procedure
Request
27 5 7b 1 51 68 AA 55 b
Response
27 5 8 1 2d 68 AA 55 b
37

Sport Frame

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sport Frame

Uploaded by

Copyright:

Available Formats

Chapter 01

Block ‘0’ Record

It is also called as “Frame”

3> Control Field

RES = 0 PRM=0 ACD DFC FUNC TION CO DE

i> RES : = Reserved Bit. It is always 0

ii> PRM : = This is the primary message bit .

iii> FCB : = Frame Count Bit

iv> FCV: = Frame Count Valid

Note: FC => Function Code

e.g. of Block ‘0’ 27 02 5B 02 36

This comes as a “Negative Acknowledgement “ from the RTU to RCC.

Sl. No. NACK Record Description Type

NACK byte (A2H)

Type identification defines the type of message

Type identification: = <8bits> <1… 255>

Messages with undefined values of TYPE IDENTIFICATION are acknowledged

Value <0> is not used.

<136 …. 255> : = for private range use

Process information in monitor direction

Process information in Control direction

<45> := single command

System information in control direction

<103> := clock synchronization command

<120> := file ready

Information Object Address

If the point address (DI) from 1 – 32 gets changed then

If the point address (DI ) from 33 – 64 gets changed then

If the point address (DI ) from 65 - 96 gets changed then

If the point address (DI ) from 97 - 128 gets changed then

This time record is used where absolute time record is required.

Note : Day of week is not used in this implementation and is set to 0

2.3.1 Four-octet binary time :

APPLICATION SERVICES FORMAT DETAILS.

FC = 10 < for class 1 data >

1> 27 => Starting Address

4> Event Data Record:

5>Four - Octet Time Record

(a) No class 1 data available to transmit

(b) Other NACK’s possible are

This packet is returned if DI point 1 = 0 and the DI point 2 =1 of RTU number 02

This packet is returned if DI point 1 = 1 and the DI point 2 =0 of RTU number 02

27 => start address

2> Type Identification

3>Information Object Address

If the point address (DI) from 1 – 32 gets changed then

If the point address (DI ) from 33 – 64 gets changed then

If the point address (DI ) from 65 - 96 gets changed then

If the point address (DI ) from 97 - 128 gets changed then

4>Event Data Record

56 55 15 0 these four bytes represent the Event Data Record

56 55 15 0 is the Event Data Record when DI point 1 = 0 and the DI point 2 =1 of

55 55 15 0 is the Event Data Record DI point 1 = 1 and the DI point 2 =0 of RTU

56 => 0 1 0 1 0 1 1 0 == DI points 8,7,6,5,4,3,2,1 respectively

Note the highlighted bits they are only changing .

5> Four - Octet Time Record

Here 26 is the CRC Byte

FC=11 < Class 2 >

(1) Measurand values

First 5 bytes are Block “0”

1 0 => value of DI point 1 = 0

2 c1 => value of DI point 2 = 193

3 0 => value of DI point 3 = 0

4 cb => value of DI point 4 = 203