GE ML Series 350 Use and care manual

Communications Guide
SR350 revision: 2.0x
Manual P/N: 1601-9094-AA
GE publication code: GEK-113537J
*1601-9094-AA*
GE
Digital Energy
GE Digital Energy
650 Markland Street
Markham, Ontario
Canada L6C 0M1
TELEPHONE: Worldwide [phone]
Europe/Middle East Africa [phone]
North America toll-free 1 800 547 8629
FAX: [phone]
E-MAIL: Worldwide multi[email protected]
Europe multilin.t[email protected]
HOME PAGE: Internet: http://www.gedigitalenergy.com/multilin
350
Feeder Protection System
Feeder protection and control

© 2015 GE Multilin Inc. All rights reserved.
GE Digital Energy SR350 Feeder Protection System Communications Guide for revision
2.0x.
SR350 Feeder Protection System, EnerVista, EnerVista Launchpad, and EnerVista SR3
Setup, are trademarks or registered trademarks of GE Multilin Inc.
The contents of this manual are the property of GE Multilin Inc. This documentation is
furnished on license and may not be reproduced in whole or in part without the permission
of GE Multilin. The content of this manual is for informational use only and is subject to
change without notice.
Part number: 1601-9094-AA (February 2015)

Safety words and definitions
The following symbols used in this document indicate the following conditions:
Note Indicates a hazardous situation which, if not avoided, will result in death or serious
injury.
Note Indicates a hazardous situation which, if not avoided, could result in death or serious
injury.
Note Indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
Note Indicates practices not related to personal injury.
NOTE
Indicates general information and practices, including operational information and
practices, that are not related to personal injury.

350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE i
Table of Contents
1.
COMMUNICATIONS
INTERFACES
2. RS485 INTERFACE Electrical Interface.............................................................................................................2 - 1
MODBUS Protocol ..............................................................................................................2 - 2
Data Frame Format and Data Rate.................................................................................2 - 2
Data Packet Format................................................................................................................2 - 2
Error Checking ...........................................................................................................................2 - 3
CRC-16 Algorithm.....................................................................................................................2 - 3
Timing ............................................................................................................................................2 - 4
350 supported functions.......................................................................................................2 - 4
DNP protocol settings......................................................................................................2 - 5
DNP communication...............................................................................................................2 - 5
DNP device profile....................................................................................................................2 - 6
DNP implementation ..............................................................................................................2 - 8
DNP serial EnerVista Setup ..................................................................................................2 - 12
DNP general................................................................................................................................2 - 14
IEC 60870-5-103 serial communication .................................................................2 - 15
Interoperability ..........................................................................................................................2 - 15
Physical layer............................................................................................................................2 - 15
Link layer.....................................................................................................................................2 - 16
Application layer......................................................................................................................2 - 16
Application level........................................................................................................................2 - 20
Application functions ............................................................................................................2 - 20
Type identification..................................................................................................................2 - 20
Function type............................................................................................................................2 - 20
Information number..............................................................................................................2 - 21
Data management ..................................................................................................................2 - 21
Digital states .............................................................................................................................2 - 21
Measurands...............................................................................................................................2 - 22
Commands ................................................................................................................................2 - 23
103 general settings ...............................................................................................................2 - 24
3. ETHERNET
INTERFACE
Redundancy Options........................................................................................................3 - 2
Parallel Redundancy Protocol (PRP).................................................................................3 - 3
High-availability Seamless Redundancy (HSR)...........................................................3 - 5
Daisy Chain .................................................................................................................................3 - 5
MODBUS TCP/IP ..................................................................................................................3 - 6
Data and control functions..................................................................................................3 - 6
Exception and error responses..........................................................................................3 - 12
Request response sequence...............................................................................................3 - 12
CRC..................................................................................................................................................3 - 13
DNP Ethernet protocol settings...................................................................................3 - 15
DNP communication...............................................................................................................3 - 15
DNP device profile....................................................................................................................3 - 16
DNP port allocation .................................................................................................................3 - 18
DNP implementation ..............................................................................................................3 - 19
DNP Ethernet EnerVista Setup ...........................................................................................3 - 22

ii 350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE
DNP general................................................................................................................................3 - 24
IEC60870-5-104 protocol...............................................................................................3 - 25
IEC 60870-5-104 interoperability .....................................................................................3 - 25
IEC 60870-5-104 protocol settings..................................................................................3 - 33
IEC 60870-5-104 point lists .................................................................................................3 - 34
Summary of Ethernet client connections...............................................................3 - 35
4. SR3 IEC61850
GOOSE
Simplified SR3 IEC61850 GOOSE configuration...................................................4 - 1
SR3 GOOSE capabilities......................................................................................................... 4 - 2
Setting up the SR3 GOOSE Configurator.......................................................................4 - 3
Simplified SR3 IEC61850 GOOSE messaging........................................................4 - 5
Connection..................................................................................................................................4 - 5
Configuration.............................................................................................................................4 - 6
SR3 GOOSE configuration via the IEC 61850 configurator ............................4 - 18
Introduction to the SR3 IEC61850 Device Configurator .......................................4 - 18
SR3 GOOSE configuration - Lab ........................................................................................4 - 22
Configuration lab steps........................................................................................................4 - 24
SR3 IEC 61850 GOOSE details......................................................................................4 - 36
EnerVista SR3 Setup software structure ....................................................................... 4 - 37
GOOSE transmission...............................................................................................................4 - 39
GOOSE Rx.....................................................................................................................................4 - 41
GOOSE Rx status ......................................................................................................................4 - 41
GOOSE Rx headers ..................................................................................................................4 - 43
GOOSE receive dataset structure..................................................................................... 4 - 44
GOOSE remote inputs ............................................................................................................ 4 - 45
IEC 61850 Logical Nodes................................................................................................4 - 47
System logical nodes (LN Group: L)..................................................................................4 - 48
Logical Nodes for protection functions (LN Group:P) ..............................................4 - 48
Logical nodes for protection related functions (LN Group: R).............................4 - 55
Logical Nodes for generic references (LN Group: G) ..............................................4 - 56
Logical Nodes for metering and measurement (LN Group: M)...........................4 - 59
Logical Nodes for switchgear (LN Group: X)................................................................4 - 60
IEC 61850 Common Data Class..................................................................................4 - 60
Common data class specifications for status information..................................4 - 60
Common data class specifications for measurand information.......................4 - 63
Common data class specifications for controllable status information........4 - 65
Common data class specifications for description information........................4 - 67
5. OPC–UA
COMMUNICATION
STANDARD
Definitions and Acronyms .............................................................................................5 - 1
OPC–UA Architecture.......................................................................................................5 - 1
OPC–UA Settings................................................................................................................5 - 2
OPC–UA Server Configuration Data..........................................................................5 - 2
OPC–UA Point Lists............................................................................................................5 - 2
6. USB INTERFACE MODBUS Protocol..............................................................................................................6 - 1
Data Frame Format and Data Rate ................................................................................6 - 1
Data Packet Format................................................................................................................6 - 1
Error Checking...........................................................................................................................6 - 2
CRC-16 Algorithm ....................................................................................................................6 - 2
Timing............................................................................................................................................6 - 3
350 supported functions ......................................................................................................6 - 3

350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE iii
7. TIME PROTOCOLS IEC 1588 Precision Time Protocol (PTP)....................................................................7 - 1
Real Time Clock .........................................................................................................................7 - 1
8. MODBUS MEMORY
MAP
MODBUS memory map...................................................................................................8 - 1
Format Codes ......................................................................................................................8 - 63
9. MODBUS
FUNCTIONS
Function Code 03H............................................................................................................9 - 1
Function Code 04H............................................................................................................9 - 2
Function Code 05H............................................................................................................9 - 3
Function Code 06H............................................................................................................9 - 4
Function Code 07H............................................................................................................9 - 4
Function Code 08H............................................................................................................9 - 5
Function Code 10H............................................................................................................9 - 6
Error Responses..................................................................................................................9 - 7
Force coil commands.......................................................................................................9 - 7
Performing Commands Using Function Code 10H............................................9 - 8
10. USING THE
MODBUS USER MAP
MODBUS User Map............................................................................................................10 - 1
11. APPENDIX Warranty................................................................................................................................11 - 1
Change notes.......................................................................................................................11 - 1
Manual Revision history ........................................................................................................11 - 1

iv 350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE

350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE 1–1
SR350 Feeder Protection System
Chapter 1: Communications
interfaces
GE
Digital Energy
Communications interfaces
The 350 has three communications interfaces. These can be used simultaneously:
• RS485
•USB
•Ethernet

1–2 350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE
CHAPTER 1: COMMUNICATIONS INTERFACES

350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE 2–1
SR350 Feeder Protection System
Chapter 2: RS485 interface
GE
Digital Energy
RS485 interface
Electrical Interface
The hardware or electrical interface in the 350 is two-wire RS485. In a two-wire link, data is
transmitted and received over the same two wires. Although RS485 two wire
communication is bi-directional, the data is never transmitted and received at the same
time. This means that the data flow is half duplex.
RS485 lines should be connected in a daisy chain configuration with terminating networks
installed at each end of the link (i.e. at the master end and at the slave farthest from the
master). The terminating network should consist of a 120 W resistor in series with a 1 nF
ceramic capacitor when used with Belden 9841 RS485 wire. Shielded wire should always
be used to minimize noise. The shield should be connected to all of the 350 s as well as the
master, then grounded at one location only. This keeps the ground potential at the same
level for all of the devices on the serial link.
NOTE
NOTE: Polarity is important in RS485 communications. The '+' (positive) terminals of every device
must be connected together.

2–2 350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE
MODBUS PROTOCOL CHAPTER 2: RS485 INTERFACE
MODBUS Protocol
The 350 implements a subset of the Modicon Modbus RTU serial communication standard.
The Modbus protocol is hardware-independent. That is, the physical layer can be any of a
variety of standard hardware configurations. This includes USB, RS485, fibre optics, etc.
Modbus is a single master / multiple slave type of protocol suitable for a multi-drop
configuration.
The 350 is always a Modbus slave. It can not be programmed as a Modbus master.
Computers or PLCs are commonly programmed as masters.
Both monitoring and control are possible using read and write register commands. Other
commands are supported to provide additional functions.
The Modbus protocol has the following characteristics.
•Address:1to254
• Supported Modbus function codes: 3H, 4H, 5H, 6H, 7H, 8H, 10H
Data Frame Format and Data Rate
One data frame of an asynchronous transmission to or from a 350 typically consists of 1
start bit, 8 data bits, and 1 stop bit. This produces a 10 bit data frame. This is important for
transmission through modems at high bit rates.
Modbus protocol can be implemented at any standard communication speed. The
350 supports operation at 9600, 19200, 38400, 57600, and 115200 baud. The USB
interface will support only 115200 baud.
Data Packet Format
A complete request/response sequence consists of the following bytes (transmitted as
separate data frames):
Master Request Transmission:
SLAVE ADDRESS: 1 byte
FUNCTION CODE: 1 byte
DATA: variable number of bytes depending on FUNCTION CODE
CRC: 2 bytes
Slave Response Transmission:
SLAVE ADDRESS: 1 byte
FUNCTION CODE: 1 byte
DATA: variable number of bytes depending on FUNCTION CODE
CRC: 2 bytes
SLAVE ADDRESS: This is the first byte of every transmission. This byte represents the user-
assigned address of the slave device that is to receive the message sent by the master.
Each slave device must be assigned a unique address and only the addressed slave will
respond to a transmission that starts with its address. In a master request transmission the
SLAVE ADDRESS represents the address of the slave to which the request is being sent. In a
slave response transmission the SLAVE ADDRESS represents the address of the slave that is
sending the response.
FUNCTION CODE: This is the second byte of every transmission. Modbus defines function
codes of 1 to 127.
DATA: This will be a variable number of bytes depending on the FUNCTION CODE. This may
be Actual Values, Setpoints, or addresses sent by the master to the slave or by the slave to
the master.
CRC: This is a two byte error checking code.

CHAPTER 2: RS485 INTERFACE MODBUS PROTOCOL
350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE 2–3
Error Checking
The RTU version of Modbus includes a two byte CRC-16 (16 bit cyclic redundancy check)
with every transmission. The CRC-16 algorithm essentially treats the entire data stream
(data bits only; start, stop and parity ignored) as one continuous binary number. This
number is first shifted left 16 bits and then divided by a characteristic polynomial
(11000000000000101B). The 16 bit remainder of the division is appended to the end of the
transmission, MSByte first. The resulting message including CRC, when divided by the
same polynomial at the receiver will give a zero remainder if no transmission errors have
occurred.
If a 350 Modbus slave device receives a transmission in which an error is indicated by the
CRC-16 calculation, the slave device will not respond to the transmission. A CRC-16 error
indicates than one or more bytes of the transmission were received incorrectly and thus
the entire transmission should be ignored in order to avoid the 350 performing any
incorrect operation.
The CRC-16 calculation is an industry standard method used for error detection. An
algorithm is included here to assist programmers in situations where no standard CRC-16
calculation routines are available.
CRC-16 Algorithm
Once the following algorithm is complete, the working register “A” will contain the CRC
value to be transmitted. Note that this algorithm requires the characteristic polynomial to
be reverse bit ordered. The MSBit of the characteristic polynomial is dropped since it does
not affect the value of the remainder. The following symbols are used in the algorithm:
—>: data transfer
A: 16 bit working register
AL: low order byte of A
AH: high order byte of A
CRC: 16 bit CRC-16 value
i, j: loop counters
(+): logical exclusive or operator
Di: i-th data byte (i = 0 to N-1)
G: 16 bit characteristic polynomial = 1010000000000001 with MSbit dropped and bit order
reversed
shr(x): shift right (the LSbit of the low order byte of x shifts into a carry flag, a '0' is shifted
into the MSbit of the high order byte of x, all other bits shift right one location
The algorithm is:
1. FFFF hex —> A
2. 0 —> i
3. 0 —> j
4. Di (+) AL —> AL
5. j+1 —> j
6. shr(A)
7. is there a carry? No: go to 8. Yes: G (+) A —> A
8. is j = 8? No: go to 5. Yes: go to 9.
9. i+1 —> i

2–4 350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE
MODBUS PROTOCOL CHAPTER 2: RS485 INTERFACE
10. is i = N? No: go to 3. Yes: go to 11.
11. A —> CRC
Timing
Data packet synchronization is maintained by timing constraints. The receiving device
must measure the time between the reception of characters. If 3.5 character times elapse
without a new character or completion of the packet, then the communication link must
be reset (i.e. all slaves start listening for a new transmission from the master). Thus at 9600
baud a delay of greater than 3.5 x 1 / 9600 x 10 = 3.65ms will cause the communication
link to be reset.
350 supported functions
The following functions are supported by the 350 :
• FUNCTION CODE 03H - Read Setpoints
• FUNCTION CODE 04H - Read Actual Values
• FUNCTION CODE 05H - Execute Operation
• FUNCTION CODE 06H - Store Single Setpoint
• FUNCTION CODE 07H - Read Device Status
• FUNCTION CODE 08H - Loopback Test
• FUNCTION CODE 10H - Store Multiple Setpoints
Refer to section 6 of this guide for more details on MODBUS function codes.

CHAPTER 2: RS485 INTERFACE DNP PROTOCOL SETTINGS
350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE 2–5
DNP protocol settings
DNP communication
Figure 2-1: DNP communication menu
The following path is available using the keypad. For instructions on how to use the
keypad, please refer to Chapter 3 - Working with the Keypad.
PATH: SETPOINTS > RELAY SETUP > COMMUNICATIONS > DNP PROTOCOL > DNP GENERAL
To view the list of DNP Binary Inputs please refer to the Format Codes section - FC134B - of
this Guide.
S1 DNP GENERAL
DNP ADDRESS
DNP TCP/UDP PORT
CHANNEL 1 PORT
CHANNEL 2 PORT
TME SYNC IIN PER.
DNP MSG FRAG SIZE
DNP TCP CONN. T/O
▼
S1 DNP
DNP GENERAL
DNP UNSOL RESPONSE*
DEFAULT VARIATION
DNP CLIENT ADDRESS*
DNP POINTS LIST
▼
898769A1.cdr
DNP CLIENT ADDRESS*
CLIENT ADDRESS 1
▼
CLIENT ADDRESS 2
CLIENT ADDRESS 3
CLIENT ADDRESS 4
CLIENT ADDRESS 5
POINT 0
...
▼
POINT 1
POINT 2
POINT 63
S1 DNP POINTS LIST
BINARY INPUTS
BINARY OUTPUTS
ANALOG INPUTS
POINT 0 ENTRY
...
POINT 1
POINT 2
POINT 31
▼
ENTRY
ENTRY
ENTRY
POINT 0 ON
...
POINT 0 OFF
POINT 1 ON
POINT 1 OFF
POINT 15 ON
POINT 15 OFF
▼
DEFAULT VARIATION
DNP OBJECT 1
▼
DNP OBJECT 2
DNP OBJECT 20
DNP OBJECT 21
DNP OBJECT 22
DNP OBJECT 23
DNP OBJECT 30
DNP OBJECT 32
DNP UNSOL RESPONSE*
FUNCTION
▼
TIMEOUT
MAX RETRIES
DEST ADDRESS
* Ethernet only

2–6 350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE
DNP PROTOCOL SETTINGS CHAPTER 2: RS485 INTERFACE
DNP device profile
DNP 3.0 Device Profile
(Also see the IMPLEMENTATION TABLE in the following section)
Vendor Name: General Electric Multilin
Device Name: SR350 Relay
Highest DNP Level Supported:
For Requests: Level 2
For Responses: Level 2
Device Function:
□Master
⊠Slave
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels
Supported (the complete list is described in the attached table):
Binary Inputs (Object 1)
Binary Input Changes (Object 2)
Binary Outputs (Object 10)
Control Relay Output Block (Object 12)
Binary Counters (Object 20)
Frozen Counters (Object 21)
Counter Change Event (Object 22)
Frozen Counter Event (Object 23)
Analog Inputs (Object 30)
Analog Input Changes (Object 32)
Analog Deadbands (Object 34)
Time and Date (Object 50)
Internal Indications (Object 80)
Maximum Data Link Frame Size (octets): Maximum Application Fragment Size (octets):
Transmitted: 292 Transmitted: configurable up to 2048
Received: 292 Received: 2048
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
⊠None ⊠None
□Fixed at 3 □Configurable
□Configurable
Requires Data Link Layer Confirmation:
⊠Never
□Always
□Sometimes
□Configurable
Requires Application Layer Confirmation:
□Never

CHAPTER 2: RS485 INTERFACE DNP PROTOCOL SETTINGS
350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE 2–7
□Always
⊠When reporting Event Data
⊠When sending multi-fragment responses
□Sometimes
□Configurable
Timeouts while waiting for:
Data Link Confirm: ⊠None □Fixed □Variable □Configurable
Complete Appl. Fragment: ⊠None □Fixed □Variable □Configurable
Application Confirm: □None ⊠Fixed at 10 s □Variable □Configurable
Complete Appl. Response: ⊠None □Fixed at ___ □Variable □Configurable
Others:
Transmission Delay: No intentional delay
Need Time Interval: Configurable (default = 24 hrs.)
Select/Operate Arm Timeout: 10 s
Binary input change scanning period: 8 times per power system cycle
Analog input change scanning period: 500 ms
Counter change scanning period: 500 ms
Frozen counter event scanning period: 500 ms
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
Explanation of ‘Sometimes’: Object 12 points are mapped to Virtual Inputs and Commands (Force
Coils). Both “Pulse On” and “Latch On” operations perform the same function in the 350 ; that is, the
appropriate Virtual Input or Coil is put into the “On” state. The On/Off times and Count value are
ignored. “Pulse Off” and “Latch Off” operations put the appropriate Virtual Input or Coil into the “Off”
state. “Trip” and “Close” operations both put the appropriate Virtual Input or coil into the “On” state if
a paired mapping is set, otherwise “Trip” will put into “Off” and “Close” will put into “On”.
Reports Binary Input Change Events when no
specific variation requested:
Reports time-tagged Binary Input Change
Events 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 □Configurable (attach explanation)
Sends Unsolicited Responses: Sends Static Data in Unsolicited Responses:
□Never ⊠Never
□Configurable □When Device Restarts
□Only certain objects □When Status Flags Change
⊠Sometimes No other options are permitted.
DNP 3.0 Device Profile

2–8 350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE
DNP PROTOCOL SETTINGS CHAPTER 2: RS485 INTERFACE
DNP implementation
⊠ENABLE/DISABLE unsolicited Function codes
supported
Explanation of ‘Sometimes’: It will be disabled for
RS-485 applications, since there is no collision
avoidance mechanism. For Ethernet communication
it will be available and it can be disabled or enabled
with the proper function code.
Default Counter Object/Variation: Counters Roll Over at:
□No Counters Reported □No Counters Reported
□Configurable (attach explanation) □Configurable (attach explanation)
⊠Default Object: 20 ⊠16 Bits
Default Variation: 1
⊠Point-by-point list attached □Other Value: _____
⊠Point-by-point list attached
Sends Multi-Fragment Responses:
⊠Yes
□No
DNP 3.0 Device Profile
OBJECT REQUEST RESPONSE
OBJECT
NO.
VARIATION
NO.
DESCRIPTION FUNCTION
CODES (DEC)
QUALIFIER CODES
(HEX)
FUNCTION
CODES (DEC)
QUALIFIER CODES
(HEX)
1 0 Binary Input (Variation 0 is
used to request default
variation)
1 (read) 22
(assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
--- ---
1 Binary Input 1 (read) 22
(assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
2 Binary Input with Status 1 (read) 22
(assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
2 0 Binary Input Change
(Variation 0 is used to
request default variation)
1 (read) 06 (no range, or all)
07, 08 (limited
quantity)
--- ---
1 Binary Input Change
without Time 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
2 Binary Input Change with
Time 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
3 Binary Input Change with
Relative Time 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
--- ---
10 0 Binary Output Status
(Variation 0 is used to
request default variation)
1 (read) 00, 01(start-stop) 06
(no range, or all) 07,
08 (limited quantity)
17, 28 (index)
--- ---

CHAPTER 2: RS485 INTERFACE DNP PROTOCOL SETTINGS
350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE 2–9
2 Binary Output Status 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
12 1 Control Relay Output Block 3 (select)4
(operate) 5 (direct
op) 6 (dir. op,
noack)
00, 01 (start-stop)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) echo of request
20 0 Binary Counter (Variation 0
is used to request default
variation)
1 (read) 7 (freeze)
8 (freeze noack) 9
(freeze clear) 10
(frz. cl. noack) 22
(assign class)
00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
--- ---
1 32-Bit Binary Counter 1 (read)7 (freeze)
8 (freeze noack) 9
(freeze clear) 10
(frz. cl. noack) 22
(assign class)
00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
2 16-Bit Binary Counter 1 (read) 7 (freeze)
8 (freeze noack) 9
(freeze clear) 10
(frz. cl. noack) 22
(assign class)
00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
5 32-Bit Binary Counter
without Flag 1 (read) 7 (freeze) 8 (freeze noack) 9
(freeze clear) 10
(frz. cl. noack) 22
(assign class)
00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
6 16-Bit Binary Counter
without Flag 1 (read) 7 (freeze) 8 (freeze noack) 9
(freeze clear) 10
(frz. cl. noack) 22
(assign class)
00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
21 0 Frozen Counter(Variation 0
is used to request
defaultvariation)
1 (read) 22
(assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
--- ---
1 32-Bit Frozen Counter 1 (read) 22
(assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
2 16-Bit Frozen Counter 1 (read) 22
(assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
9 32-Bit Frozen Counter
without Flag 1 (read) 22 (assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
10 16-Bit Frozen Counter
without Flag 1 (read) 22 (assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
22 0 Counter Change Event
(Variation 0 is used to
request default variation)
1 (read) 06 (no range, or all)
07, 08 (limited
quantity)
--- ---
OBJECT REQUEST RESPONSE
OBJECT
NO.
VARIATION
NO.
DESCRIPTION FUNCTION
CODES (DEC)
QUALIFIER CODES
(HEX)
FUNCTION
CODES (DEC)
QUALIFIER CODES
(HEX)

2–10 350 FEEDER PROTECTION SYSTEM – COMMUNICATIONS GUIDE
DNP PROTOCOL SETTINGS CHAPTER 2: RS485 INTERFACE
1 32-Bit Counter Change
Event 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
23 2 16-Bit Counter Change
Event 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
5 32-Bit Counter Change
Event with Time 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
6 16-Bit Counter Change
Event with Time 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
0 Frozen Counter Event
(Variation 0 is used to
request default variation)
1 (read) 06 (no range, or all)
07, 08 (limited
quantity)
--- ---
1 32-Bit Frozen Counter Event 1 (read) 06 (no range, or all)
07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
2 16-Bit Frozen Counter Event 1 (read) 06 (no range, or all)
07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
5 32-Bit Frozen Counter Event
with Time 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
6 16-Bit Frozen Counter Event
with Time 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
30 0 Analog Input (Variation 0 is
used to request default
variation)
1 (read) 22
(assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
--- ---
1 32-Bit Analog Input 1 (read) 22
(assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
2 16-Bit Analog Input 1 (read) 22
(assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
3 32-Bit Analog Input without
Flag 1 (read) 22 (assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
4 16-Bit Analog Input without
Flag 1 (read) 22 (assign class) 00, 01 (start-stop) 06 (no range, or all)
07, 08 (limited
quantity) 17, 28
(index)
129 (response) 00, 01 (start-stop)
17, 28 (index) (see
Note 2)
32 0 Analog Change Event
(Variation 0 is used to
request default variation)
1 (read) 06 (no range, or all)
07, 08 (limited
quantity)
--- ---
1 32-Bit Analog Change Event
without Time 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
2 16-Bit Analog Change Event
without Time 1 (read) 06 (no range, or all) 07, 08 (limited
quantity)
129 (response)
130 (unsol.
resp.)
17, 28 (index)
OBJECT REQUEST RESPONSE
OBJECT
NO.
VARIATION
NO.
DESCRIPTION FUNCTION
CODES (DEC)
QUALIFIER CODES
(HEX)
FUNCTION
CODES (DEC)
QUALIFIER CODES
(HEX)