Rec523 dnpprotmanENc

DNP 3.
0
Remote Communication Protocol
for REC 523
Technical Description
1MRS 750958-MUM Remote Communication Protocol DNP 3.0
Issued: 24.09.2000 for REC 523
Version: C/7.12.2000
Checked: ML Technical Description
Approved:
We reserve the right to change data without prior notice.
Contents
1. Overview of the Protocol ..........................................................5
1.1. Physical layer ................................................................................5
1.2. Data link layer ...............................................................................5
1.3. Transport pseudo-layer .................................................................6
1.4. Application layer ............................................................................6
1.5. Frame formats ...............................................................................7
1.5.1. Overall information .............................................................7
1.5.2. Data link layer frame format ...............................................8
1.5.3. Transport layer frame format .............................................9
1.5.4. Application layer frame format ...........................................9
1.5.4.1. Application request format ...................................9
1.5.4.2. Application response format ...............................10
2. REC 523 Profile in DNP 3.0 .....................................................20
2.1. Supported functions ....................................................................20
2.1.1. Data link layer ..................................................................20
2.1.2. Transport layer .................................................................22
2.1.3. Application layer ...............................................................23
2.2. Supported data types ..................................................................24
2.2.1. Point numbering overall rules ..........................................24
2.2.2. Standard object types definitions .....................................24
2.2.3. Single bit binary input .......................................................25
2.2.4. Binary input with status ....................................................26
2.2.5. Binary input change without time .....................................26
2.2.6. Binary input change with time ..........................................27
2.2.7. Binary output ....................................................................29
2.2.8. Binary output with status ..................................................29
2.2.9. Control relay output block ................................................30
2.2.10.32-bit binary counter without flag .....................................32
2.2.11.32-bit counter change event without time ........................33
2.2.12.32-bit analogue input without flag ....................................33
2.2.13.32-bit analogue change event without time .....................34
2.2.14.32-bit analogue output status ...........................................35
2.2.15.32-bit analogue output block ............................................35
2.2.16.Time and date ..................................................................36
2.2.17.Time delay coarse ............................................................37
2.2.18.Time delay fine .................................................................37
2.2.19.Internal indications ...........................................................37
2.2.20.Application identifier .........................................................38
2.3. New object types definitions ........................................................38
ABB Automation 3
DNP 3.0 Remote Communication Protocol 1MRS 750958-MUM
for REC 523
2.3.1. Byte sequence (string) ..................................................... 38

2.3.2. SPA message .................................................................. 38
3. Protocol Interface Implementation ....................................... 40
3.1. Application to protocol mapping .................................................. 40
3.1.1. POD concept ................................................................... 40
3.1.2. POD configuration ........................................................... 40
3.1.2.1. DNP object map ................................................. 41
3.1.2.2. DNP classes (default assignment) ..................... 42
3.1.3. Defining the POD contents .............................................. 42
3.1.3.1. Visible POD entry format ................................... 42
3.1.3.2. POD diagnostics ................................................ 45
3.1.3.3. Examples of mapping application data into
the DNP protocol 48
3.2. Protocol address map based on default POD ............................ 53
3.3. Protocol software version ........................................................ 115
3.4. Interface configuration .............................................................. 116
3.4.1. Communication start-up procedure ............................... 116
3.4.2. Port assignment ............................................................. 116
3.4.3. Link parameters ............................................................. 117
3.4.4. Protocol parameters ...................................................... 120
3.4.4.1. Recommendations for parameter tuning due to
specific medium or link characteristics ............ 123
3.4.4.2. Application mapping review ............................. 125
3.4.4.3. DNP/LON gateway function ............................. 126
4. Appendix A: Profile Checklist ............................................. 128
5. Appendix B: List of Used Abbreviations ............................ 136
4 ABB Automation
for REC 523
1. Overview of the Protocol

The DNP protocol has been developed by Harris Controls based on the early
versions of the IEC 60870-5 standard telecontrol protocol specifications. Now the
protocol specification is controlled by the DNP Users Group.
The ISO OSI based model supported by this protocol specifies physical, data link
and application layers only. This reduced protocol stack is referred to as Enhanced
Performance Architecture (EPA). However, to support advanced RTU functions and
messages larger than the maximum frame length as defined by the IEC document
60870-5-1, the DNP Version 3 Data Link is intended to be used with a transport
pseudo-layer. As a minimum, this transport layer implements message assembly and
disassembly services.
1.1. Physical layer

The physical layer that is recommended for the data link is a bit-serial oriented
asynchronous physical layer supporting 8-bit data, 1 start bit, 1 stop bit, no parity
and RS232C voltage levels and control signals. The modem used for communication
using PSN (Public Switched Network) or private leased lines must conform (as a
minimum) to the V. 24 standard DCE definition.
The physical layer must provide 5 basic services:
• Send
• Receive
• Connect (when PSN is used for communication)
• Disconnect (when PSN is used for communication)
• Status (e.g. indication of medium availability)
1.2. Data link layer

The DNP 3.0 data link layer is designed to operate with connection-oriented and
connectionless asynchronous or synchronous bit serial physical layers (such as RS-
232, RS-485 and fibre-optic transceivers). Fully balanced transmission procedures
were adopted to support spontaneous transmissions from outstations.
'DWDOLQNIXQFWLRQV
• performing message retries
• synchronizing and handling of FCB bit (Flow Control Bit) in the control octet
• setting and clearing the DFC bit (Data Flow Control) based on buffer availability
• automatically establishing a connection based on the destination parameter in a
dial-up environment when a directed service is requested by the user
• disconnecting in a dial-up environment
• packing user data into the defined frame format and transmitting the data to the
physical layer
• unpacking the frames that are received from the physical layer into user data
• controlling all aspects of the physical layer
ABB Automation 5
for REC 523
• performing collision avoidance/detection procedures to ensure the reliable

transfer of data across the physical link
• responding to all valid frames (function codes) received from the physical layer
'DWDOLQNUHVSRQVLELOLWLHV
• exchange of service data units (SDUs) between peer DNP data links
• error notification to data link user
• sequencing of SDUs
• quality SDU delivery
Quality delivery can be SEND-NO-REPLAY or SEND-CONFIRM to indicate
whether or not a message acknowledgment is required.
1.3. Transport pseudo-layer

To support advanced RTU functions and messages exceeding the maximum frame
length, a transport pseudo-layer which implements (as a minimum) message
assembly and disassembly services was introduced.
This pseudo-layer is actually a super-data link transport protocol, which is normally
included in some OSI data links.
7UDQVSRUWIXQFWLRQV
• packing user data into one or more frames of the defined DNP data link frame
format and transmitting the data to the data link layer
• unpacking multiple frames that are received from the data link layer into user
data
• controlling all aspects of the data link excluding data link configuration
7UDQVSRUWUHVSRQVLELOLWLHV
• exchange of SDUs between peer DNP transport pseudo layers
• error notification to transport user
• sequencing of SDUs
1.4. Application layer

The application layer is responsible for performing operations on data objects
defined by the device or on the device itself. These operations can be: returning
actual values (read function), assigning new values (write function) if the object
represents control points, arming and energizing the output point (select, operate or
direct operate functions) if counters are used, storing actual values (freeze functions)
and clearing the counters. There are also several functions controlling the device or
the state of the application (e.g. reset device function).
All data objects are assigned to classes. The DNP protocol defines 4 classes: class 0
for static data, class 1 for events produced by data change, class 2 for frozen data and
class 3 for events produced by freeze operations. Only static data (assigned to class
0) is always available and can be interrogated using the read function.
An outstation can spontaneously generate so-called unsolicited responses to report
event data without being polled by the master station.
6 ABB Automation
for REC 523
1.5. Frame formats
1.5.1. Overall information

Complete DNP frame structure:
Byte
Description
offset
Request Response
0 Start character Start character
1 Start character Start character
2 Length field Length field
3 Control byte Control byte
4 Destination address Destination address
Link layer frame format
5 Destination address Destination address
6 Source address Source address
7 Source address Source address
8 CRC CRC
9 CRC CRC
Transport layer frame format 10 Transport header field Transport header field
11 Application Appl. control field Application response Appl. control field
request header header
12 Appl. function code Appl. function
code
13 Object data Internal indication
14 Object data Internal indication
15 Object data Object data
Application layer frame format 20 Object data Object data
26 CRC CRC
27 CRC CRC
... ... ...
Notes:
• Data link layer frames without user data are only 10 bytes long
• Object data fields are optional and depend on the application layer function code
chosen
• For a detailed description of each field see section below
ABB Automation 7
for REC 523
1.5.2. Data link layer frame format

)UDPHIRUPDW
Fixed length header 10 octets Body

Block 0 Block 1 Block n
START LENGTH CONTROL DESTI- SOURCE CRC USER CRC ... USER CRC
0x0564 NATION DATA DATA
1 FCB FCV Primary to Secondary

DIR PRM FUNCTION CODE
0 RES DFC Secondary to Primary
Bit 7 6 5 4 3 2 1 0
'DWDOLQNKHDGHUIUDPHILHOGV
Field Sub-field Description

START 2 starting octets of the header (0x0564)
LENGHT 1 octet count of USER DATA in the header and body. This
includes the CONTROL, DESTINATION and SOURCE fields in
the header. The CRC fields are not included in the count. The
minimum value for LENGTH is 5, which indicates that only the
header is present, and the maximum value is 255.
CONTROL The control field contains the direction of the frame, type of frame
and flow control information.
DIR The direction bit indicates the physical direction of the frame with
relation to the designated master station. Value 1 indicates a
frame from the designated master station; value 0 indicates a
frame from a non-master station.
PRM The primary bit indicates the direction of the frame with relation
to the initiating station. Value 1 indicates a frame from the
initiating station, 0 indicates a frame from the responding station.
FCB The frame count bit is used for suppressing losses and
duplication of frames to the secondary station. This bit toggles for
each successful SEND-CONFIRM service that is initiated by the
same primary station and directed at the same secondary
station.
FCV The frame count valid bit enables the FCB bit to function. Value 1
means that the FCB is valid and must be checked against the
state of the FCB bit of the last frame sent with the FCV bit set.
Value 0 indicates that the state of the FCB shall be ignored.
RES Reserved always 0
DFC The data flow control bit is used to prevent the overflow of buffers
in the secondary station. The secondary station returns this bit
set to a 1, if the following SEND of user data to this secondary
station causes overflow of the data link buffers.
CONTROL FUNCTION The function code indicates type of the frame.
contd CODE
8 ABB Automation
for REC 523
DEST. 2 octet destination address. The first octet is the LSB and the
second octet is the MSB.
SOURCE 2 octet source address. The first octet is the LSB and the second
octet is the MSB.
CRC 2 octet Cyclic Redundancy Check
USER Each block following the header has 16 octets of user-defined
DATA data, except the last block, which contains 1 to 16 octets as
needed.
1.5.3. Transport layer frame format

)UDPHIRUPDW
Transport header User data (1 - 249 octets)
FIN FIR SEQUENCE
Bit 7 6 5 4 3 2 1 0
FIN The final bit set to 1 indicates that this frame of user data is the last frame of
a sequence in a complete user message.
FIR The first bit set to 1 indicates that the frame is the first in a sequence of
frame(s) that comprise a complete message. When a secondary station
receives a frame with the FIR bit set, any previously received and not
terminated frame sequence is discarded. If a frame is received without the
FIR set and no message sequence is currently in progress, then the frame is
ignored.
SEQUENCE The sequence number of the frame is used to check that each frame is
being received in sequence. It guards against missing or duplicated frames.
All user messages start off with a sequence specified in the first frame that
has the FIR bit set (each message may start with any sequence number
between 0 and 63). Sequence 63 will be followed by 0.
1.5.4. Application layer frame format
1.5.4.1. Application request format
DUI IO...IO DUI IO

Request header Object header data ... Object header data
APCI ASDU
ABB Automation 9
for REC 523
Field Description
Request header The request header identifies the purpose of the message and consists
of APCI (Application Protocol Control Information)
Object header This header identifies the data objects that follow
Data Data object(s) of the type specified in the object header
5HTXHVWKHDGHU
Application Control Function Code

AC FC
FIN FIR CON SEQUENCE

7 6 5 4 3 2 1 0 Bit
Field Explanation
FIR If set to one, this bit indicates that the message fragment is the first of a
complete application message.
FIN If set to one, this bit indicates that the message fragment is the final fragment
of a complete application message.
CON If set to one in a received message, this bit indicates that the sending
application is expecting a confirmation from the receiving application of the
reception of the fragment.
SEQUENCE Indicates the fragment number. Fragment numbers 0...15 are reserved for
master station requests and all outstation responses (NOT Unsolicited
Responses). Fragment numbers 16...31 are reserved for unsolicited
responses.
1.5.4.2. Application response format
DUI IO…IO DUI IO

Response header Object header data ... Object header data
APCI ASDU
Field Description
Response header The response header identifies the purpose of the message and
consists of APCI (Application Protocol Control Information).
Object header This header identifies the data objects that follow.
Data Data object(s) of the type specified in the object header.
10 ABB Automation
for REC 523
Response header
Application Control Function Code Internal Indications

AC FC IIN
FIN FIR CON SEQUENCE

7 6 5 4 3 2 1 0 Bit
Field Explanation
FIR If set to one, this bit indicates that the message fragment is the first of a
complete application message.
FIN If set to one, this bit indicates that the message fragment is the final
fragment of a complete application message.
CON If set to one in a received message, this bit indicates that the sending
application is expecting a confirmation from the receiving application of the
reception of the fragment.
SEQUENCE Indicates the fragment number. Fragment numbers 0…15 are reserved for
master station requests and all outstation responses (NOT Unsolicited
Responses). Fragment numbers 16…31 are reserved for unsolicited
responses.
,QWHUQDOLQGLFDWLRQV
The ,QWHUQDO,QGLFDWLRQV (IIN) field is a two-octet field that follows the function code
in all responses. When a request cannot be processed due to formatting errors, or the
requested data is not available, the IIN is always returned with the appropriate bits
set.
First octet:
Bit 0 All stations message received
Bit 1 Class 1 data available
Bit 4 Time synchronization required from the master
Bit 5 Set when some or all of the outstation’s digital output points are in
a local state
Bit 6 Device trouble
Bit 7 Device restart
Second octet:
Bit 0 Function code not implemented
Bit 1 Requested object(s) unknown
Bit 2 Parameters in the qualifier, range or data fields are not valid or out
of range
Bit 3 Overflow of event buffer(s), or other application buffers
Bit 4 Request understood but requested operation is already being
executed
ABB Automation 11
for REC 523
Bit 5 Current configuration of the outstation is corrupt

Bit 6 Reserved (0)
Bit 7 Reserved (0)
7KHLQWHUQDOLQGLFDWLRQV field is fully supported by the REC 523 DNP interface.
Object header
The object header of the message specifies the data objects (or IOs) that are either
contained in the message or are to be used to respond to this message.
Object Qualifier Range
Field Explanation
Object Specifies the object group and variation of the objects that follow the header.
This is a two-octet field. The object field uniquely identifies the type or class of
object which gives the structure (and hence size) of the data object
Qualifier Specifies the range field. This is a one-octet field.
Range Indicates the quantity of objects, starting and ending index or identifiers for the
objects in question.
Object field
The 2EMHFWfield specifies an object group and the variation of the object within the
group. The combined object group plus variation uniquely specifies the object to
which the message refers.
An objectcan be assigned to one of four classes. When the2EMHFWfield specifies a
data class instead of a specific object type, the 2EMHFWfield refers indirectly to all the
data objects assigned to that class of data and not to any specific object type.
The 2EMHFW field is two octets in length. The first octet specifies the general type of
data (e.g. analogue inputs) and the second octet specifies the variation of the data
type (e.g. 16-bit analogue inputs or 32-bits analogue inputs). In the request direction,
if the object variation is specified as zero, this indicates the default variation for this
group. In the response, however, variation 0 cannot be used to specify the object. A
specific variation has to be given. By requesting data with variation 0, it is not
necessary for the master to know what variations the outstation supports. However,
the master must be able to interpret the object headers and have some knowledge of
the structure of each variation.
first octet second octet

Object group 0 or object variation Application request header
object variation Application response direction
Qualifier field
The4XDOLILHUfield specifies the5DQJHfield.
7 6 5 4 3 2 1 0 Bit
R Index Size 4 bit Qualifier Code
12 ABB Automation
for REC 523
The 5DQJHfield is used to index data or as an identifier. The structure and use of the
5DQJHfield are dependent on the value in the ,QGH[6L]Hfield and the 4XDOLILHU&RGH
field.
,QGH[6L]HELWV
• In a Request Object Header where 4XDOLILHU&RGH equals 11
The ,QGH[6L]H bits are valid only when the 4XDOLILHU&RGH is 11. These bits
indicate the size, in octets, of each entry in the 5DQJH field.
0 = not valid with 4XDOLILHU&RGH11
1 = 1 octet identifier size
4 = reserved
5 = reserved
6 = reserved
7 = reserved
• In a Response or Request Object Header that is part of a message containing data
objects
The 3-bit ,QGH[6L]H field specifies the size of an index or the object size
prefixing each object.
0 = objects are packed with no index prefixing them
1 = objects are prefixed with 1 octet index
4 = objects are prefixed with 1 octet object size
7 = reserved
4XDOLILHU&RGHELWV
The 4XDOLILHU&RGH field is used to specify the 5DQJH field.
0 = 8-bit start and stop indices in the 5DQJH field
1 = 16-bit start and stop indices in the 5DQJH field
2 = 32-bit start and stop indices in the 5DQJHfield
3 = 8-bit absolute address identifiers in the 5DQJH field
6 = no 5DQJH field (implies all specified objects)
7 = 8-bit single field quantity
10 = reserved
11 = free format qualifier used to specify objects when other 4XDOLILHU&RGHV are
inadequate or do not provide enough identifying information.
12 = reserved
13 = reserved
14 = reserved
15 = reserved
ABB Automation 13
for REC 523
Range field for messages without data objects

4XDOLILHU&RGHIRUGHVFULELQJSRLQWVLQVHTXHQFH
Qualifier Code 0 or 3, index size 0, points are I1 to I2 inclusive
Start 8 bit Stop 8 bit

I1 I2
Qualifier Code 1 or 4, index size 0, points I1 to I2 inclusive

I1 I2

I1 I2
4XDOLILHU&RGHIRU$//SRLQWVRIWKHJLYHQW\SHQRUDQJHILHOG
4XDOLILHU&RGHIRUGHVFULELQJDQXPEHURIXQUHODWHGSRLQWV
Qualifier Code 7, index size 0, points are 0…Q-1 inclusive
Quantity
8 bit
Q
Qualifier Code 7, index size 1, points are I1, I2 … IQ inclusive
Quantity Index ... Index

8 bit 8 bit 8 bit
Q I1 IQ

8 bit 16 bit 16 bit
Q I1 IQ

8 bit 32 bit 32 bit
Q I1 IQ
14 ABB Automation
for REC 523
Quantity
16 bit
Q

16 bit 8 bit 8 bit
Q I1 IQ

16 bit 16 bit 16 bit
Q I1 IQ

Q I1 IQ
Quantity
32 bit
Q

32 bit 8 bit 8 bit
Q I1 IQ

Q I1 IQ

Q I1 IQ
ABB Automation 15
for REC 523
4XDOLILHU&RGHLVXVHGWRGHVFULEHSRLQWVWKDWKDYHWREHXQLTXHO\LGHQWLILHG
E\DQREMHFWLGHQWLILHUVXFKDVD)LOH2EMHFW,GHQWLILHURU&RQILJXUDWLRQ+HDGHU
7KHW\SHRILGHQWLILHULVLPSOLHGE\WKHREMHFWW\SH
Qualifier Code 11, index size 1, octets Oi1…OiN form the object identifier for
Object i where 0<=i<Q (quantity)
Quantity Size O11 O12 ... O1N ... Size OQ1 ... OQN
8 bit 8 bit 8 bit
Q N1 NQ
Qualifier Code 11, index size 2, octets Oi1…OiN form the object identifier for
Q N1 NQ
Qualifier Code 11, index size 3, octets Oi1...OiN form the object identifier for
Q N1 NQ
Note:
Qualifier Code 11 is not supported by the REC 523 DNP interface.
Range field for messages with data objects
4XDOLILHU&RGHIRUGHVFULELQJSRLQWVLQVHTXHQFH
Start 8 bit Stop 8bit DO DO ... DO

I1 I2 I1 I1+1 I2
Start 16 bit Stop 16 bit DO DO ... DO

I1 I2 I1 I1+1 I2
Start 32 bit Stop 32 bit DO DO ... DO

I1 I2 I1 I1+1 I2
16 ABB Automation
for REC 523
Start 8 bit Stop 8bit Size 8 bit DO I1 ... Size 8 bit DO I2

I1 I2 S1 with size S2 with size
S1 S2
Note: A 16- and 32-bit object size can also be used by using I size 5 and 6
Start 16 bit Stop 16 bit Size 16 DO I1 ... Size 16 DO I2

I1 I2 bit with size bit with size
S1 S1 S2 S2
Note: An 8- and 32-bit object size can also be used by using I size 4 and 6
Start 32 bit Stop 32 bit Size 32 DO I1 ... Size 32 DO I2

I1 I2 bit with size bit with size
S1 S1 S2 S2
Note: An 8- and 16-bit object size can also be used by using I size 4 and 5
,PSRUWDQWQRWH
'R127XVH4XDOLILHU&RGHIRUGHVFULELQJDPHVVDJHWKDWFRQWDLQVGDWD
REMHFWVEHFDXVHWKHH[DFWQXPEHURISRLQWVLVQRWNQRZQDQGWKHUHIRUHWKH
FRQWHQWVRIWKHPHVVDJHFDQQRWEHGHWHUPLQHG
4XDOLILHU&RGHIRUGHVFULELQJDQXPEHURIXQUHODWHGSRLQWV
Qualifier Code 7, index size 0, points are 0...Q-1 inclusive
Quantity DO ... DO
8 bit I0 I(Q-1)
Q
Qualifier Code 7, index size 1, points are I1, I2 ... IQ inclusive
Quantity Index DO ... Index DO

8 bit 8 bit I1 8 bit IQ
Q I1 IQ

Q I1 IQ
ABB Automation 17
for REC 523

Q I1 IQ
Quantity DO ... DO
16 bit I0 I(Q-1)
Q

Q I1 IQ

Q I1 IQ

Q I1 IQ
Quantity DO ... DO
32 bit I0 I(Q-1)
Q

Q I1 IQ

Q I1 IQ
18 ABB Automation
for REC 523

Q I1 IQ
4XDOLILHU&RGHLVXVHGWRGHVFULEHSRLQWVWKDWKDYHWREHXQLTXHO\LGHQWLILHG
E\DQREMHFWLGHQWLILHUVXFKDVD)LOH2EMHFW,GHQWLILHURU&RQILJXUDWLRQ+HDGHU
7KHW\SHRILGHQWLILHULVLPSOLHGE\WKHREMHFWW\SH
Object I, where 0<=i<Q (quantity) which is followed by the object identified. The
size of the object is contained in the Object Identifier and thus the application layer
must be able to interpret some fields of the object identifier in order to process a
message.
Quantity Size O11 ... O1N DO ... Size OQ1 ... OQN DO
8 bit 8 bit ID1 8 bit IDQ
Q N1 NQ
message.
Q N1 NQ
message.
Q N1 NQ
Note:
Qualifier Code 11 is not supported by the DNP interface of REC 523.
ABB Automation 19
for REC 523
2. REC 523 Profile in DNP 3.0
2.1. Supported functions
2.1.1. Data link layer

Selection of functions supported in frames sent from the primary station (PRM=1)
Function
Frame type Service function
code
0 SEND - CONFIRM expected Reset of remote link
1 SEND - CONFIRM expected Reset of user process
2 SEND - CONFIRM expected Test function for link
3 SEND - CONFIRM expected User data
4 SEND - NO REPLY expected Unconfirmed user data
9 REQUEST - RESPOND expected Request link status
Selection of functions supported in frames sent from the secondary station (PRM=0)
Function
Frame type Service function
code
0 CONFIRM ACK - positive acknowledgement
1 CONFIRM NACK – message not accepted, link
busy
11 RESPOND Status of link (DFC=0 or DFC=1)
14 RESPOND Link service not functioning
15 RESPOND Link service not used or implemented
&RPPXQLFDWLRQLQPXOWLSOHPDVWHUHQYLURQPHQW
The REC 523 is able to communicate with multiple master stations using the SEND-
NO-REPLAY service. Before using the SEND-CONFIRM service, the data link
layers of both the primary and secondary stations have to be reset (UHVHWRIUHPRWH
OLQN service function). In this case, REC 523 is able to communicate with one
designated master (the address of this station is stored as a parameter) and one
“virtual” master. If another master wants to use the SEND-CONFIRM service to
communicate with REC 523, it first has to send a UHVHWRIUHPRWHOLQN request. This
will enable SEND-CONFIRM communication with this station and disable SEND-
CONFIRM communication with the previous “virtual” master.
&RPPXQLFDWLRQLQDGLDOXSHQYLURQPHQW
When using a modem connection through the PSN (Public Switched Network),
string parameters are used. These parameters include initialization, hang-up and
dialing strings. Please refer to section /LQNSDUDPHWHUVfor further information.
There can be one default and 4 spare dialling strings. The dialling string contains a
phone number of the designated master station. The REC 523 unit will open the
channel only when communication with the designated master station is needed and
the channel is actually closed. If the default master station does not answer the call
20 ABB Automation
for REC 523
spare dialling numbers will be used. If all attempts to connect will fail then the
emergency number will be dialled. REC 523 will hung up immediately after
connecting. The emergency number can be e.g. operator GSM number.
When dial-up connection is used, following parameters must be set to configure
REC 523 with DNP protocol:
• Parameter “Connection mode” must be set to GLDOXSPRGH
• Parameter “Modem init str” must be set to parameterize modem (according to
manual of the used modem)
• In case of using GSM modem “GSM PIN code” parameter must also be set
accordingly.
Each modem operation is started by hanging-up any active connection. This
includes also the procedure of establishing the connection between REC523 and
SCADA system. Modem configuration/initialization is done every time when the
link initialization is performed (this does not apply to entering the GSM modem
PIN-code).
In case of using GSM modems, two levels of modem initialization are used:
• hard initialization after the device start-up, which includes the entering of PIN-
code and common modem configuration,
• soft initialization, which includes only modem reconfiguration.
If the REC 523 unit is allowed to open the connection – the “reporting flag” in DNP
POD should be set to HQDEOHG for those items that are allowed to cause opening of
the connection. For lower priority items that should not cause REC 523 to open the
connection the “reporting flag” should be set to GLVDEOHG.
To be able to connect to the master station at least “Modem dial str” must be set to
dial master stations number (Note that this string must include ATD prefix).
Communication channel is opened only after a request from the protocol software.
The algorithm of this operation assumes a predefined number of 6 attempts done
with random and increasing intervals between consecutive tries (intervals are given
in Figure 2.1.1.-1). It is possible to define more than one telephone number of the
SCADA system using separate dialing strings as link handler parameters (1 primary
number, up to 4 spare numbers).
During each attempt of establishing a connection all configured dialing numbers
from the list will be used one after another (without delays). It is also possible to
define one emergency number that is used only when it is not possible to establish
the connection with any of the configured numbers (primary and spare numbers)
after all attempts. This emergency number can be e.g. a number of the operator's
telephone. The idea of using this number is to inform the operator about traffic
problem in the telephone switching network or possible error in system
configuration. After a call has been made to the emergency number (if defined) or
all attempts to all configured numbers has failed, REC 523 initializes the link (and
hang-ups the connection) and waits for the master station to connect. Detailed
behavior of the dialing algorithm is shown on the figure below:
ABB Automation 21
for REC 523
Request to open channel

Attempt:=1
Dial primary number
Communicate with YES

Connection succesful?
master station
NO
Is next spare number YES Dial next available

configured? spare number
NO
Attempt:=Attempt+1
Case Attempt of:

NO 2: wait 0...60 seconds
All 6 attempts to connect to
configured numbers 3: wait 1...4 minutes
4: wait 4...19 minutes
executed?
YES
Dial emergency
number (if in use)
Disconnect,
initialize modem
and wait for master
to connect
dial
)LJ 7KHEHKDYLRXURIWKHGLDOLQJDOJRULWKP
When master station dials the number of REC 523 unit and successfully connects
between dialing attempts, this situation is treated the same way as if REC 523 would
successfully connect.
REC 523 is responsible for closing the communication channel when there is no
communication with the master station for a predefined time (no valid frame is
received, including also the frames addressed to other units). A watchdog function
supervising the incoming valid frames has been added to the protocol software; the
watchdog timeout is defined by a configurable parameter “Watchdog TO” in the
protocol parameter group.
When communication with another station is required and the communication
channel is closed, the transaction fails. The REC 523 unit may only call the
designated master station, and a connection with another station must be established
by this station.
2.1.2. Transport layer

Transmitted data messages can be segmented when required. In addition, incoming
APDUs may be segmented and the transport layer in REC 523 will be prepared to
assemble incoming LPDUs into one APDU.
Window size 1 (for one APDU) is assumed on the interface between the transport
layer and the application layer.
22 ABB Automation
for REC 523
2.1.3. Application layer

Selection of application functions supported in REC 523:
Code Function Description

0 Confirm Message fragment confirmation used both in requests and
responses. No response to this message is required.
1 Read Requested specified object from an outstation: respond with
objects requested if available.
2 Write Store specified objects in an outstation: respond with status
of the operation.
3 Select Select or arm output points but do not set or produce any
output action (controls, setpoints, analogue outputs); respond
with the status of the control points selected. The Operate
function code is required to activate these outputs.
4 Operate Set or produce output actions on the points previously
selected with the Select function; respond with the status of
the control points.
5 Direct operate Set or produce output actions on the points; respond with the
status of the control points.
6 Direct operate Set or produce output actions on the points; do not respond.
without ACK
13 Cold restart Perform the desired reset sequence; respond with object
indicating time until outstation is available.
14 Warm restart Perform the desired partial reset sequence; respond with
object indicating time until outstation is available.
17 Start application Start running the specified application(s); respond with the
status of the operation.
18 Stop application Stop the specified application(s); respond with the status of
the operation.
20 Enable unsolicited Enable spontaneous reporting of the specified data object(s);
messages respond with status of the operation.
21 Disable unsolicited Disable spontaneous reporting of the specified data
messages object(s); respond with the status of the operation.
22 Assign class Assign specified data object(s) to a particular class.
23 Delay Allows the master station to calculate the path delay (or
measurement propagation delay) for a particular outstation. The value
calculated from this function code should be used to adjust
the time of day when the outstation time is set.
129 Response Response to a request message.
130 Unsolicited Unsolicited response that was not prompted by a request.
message
Important notes:
• Implementation of the 'HOD\PHDVXUHPHQW function in REC 523 does not fully
follow the procedure described in the protocol specification. Only an
approximated delay value is supported by the outstation.
• Multi-fragment application messages are not supported.
ABB Automation 23
for REC 523
2.2. Supported data types
2.2.1. Point numbering overall rules

The following rules apply to the interpretation of the object point number (DNP
Application Layer UDQJH field) in conjunction with objects and variations:
5XOH
Point L of object [variation \ represents the same physical point as point L, object [,
variation], where\ and ] are variations of object[.
5XOH
Point L of object [ can be reported in many variations (i.e. it can be a 16-bit or 32-bit
counter). When reporting to a request for class data or variation 0 of object[, there
should be only one variation of the object returned. All points of object [should be
returned using variation \, where \ is the default variation of object [. A situation
where some points of object [ are returned using variation \ and others using
variation ], when responding to a class scan or to a request with variation 0 in object
header, is against this rule. When reported as an event, point L can be returned in
either one of the variations for that object. The exact variation to be returned is an
application-specific decision.
5XOH
Point Lwithin two different objects of the same grouping is not necessarily unique.
However, the following rules apply within such groupings as binary inputs, binary
outputs, counters, analogue inputs and analogue outputs:
• Point Lin the static object is the same physical point as point L in the event object
(this applies to object pairs 1 - 2, 20 - 22 and 30 - 32).
• Point L in the frozen object is the same physical point as point L in the frozen event
object (this applies to object pairs 21 - 23 and 31 - 33).
• Point L in the binary output (object 10) is the same physical point as point Lin the
control relay output block (object 12).
• PointLin the analogue output status (object 40) is the same physical point as
point L in the analogue output block object (object 41).
5XOH
Object groupings which, by definition or due to device limitations, can have only
one point per object, or where no point number is needed, should use a range number
0 or quantity equal to 1, when a message format that requires a point number is used.
2.2.2. Standard object types definitions

The following convention was used for describing data:
Data types:
All data can be described as GDWDW\SH in their most elementary form. Data types are
recognized as standard constructs used in most language compilers. DNP
information elements use constructs, as defined by the IEC 60870-5-4 standard, as
the basis of their descriptions. The table below lists available data types for this
implementation and their meaning.
24 ABB Automation
for REC 523
Data type Symbol Meaning

UNSIGNED INTEGER UI Positive whole number
INTEGER I Positive or negative whole number
BITSTRING BS Assembly of independent bits
OCTETSTRING OS Assembly of octets
Data size:
Each information element is composed of data type and data size. Data size L is noted
after the data type symbolic notation, and it is a cardinal number that specifies the
length of the data field in bits or octets, as appropriate. Example:
BS12 specifies BITSTRING of 12 bits.
Bit position:
In defining an information object, which is a combination of information elements,
the position of individual bits can be significant. The bit position of a specified field
of data size n is denoted in square brackets [p 1...pn] where p1 and pn denote the first
and the last bits of the field.
2.2.3. Single bit binary input

Data object 1 - Variation 1
Type: static
Description:
The VLQJOHELWELQDU\LQSXWobject is used to represent the state of a digital input point
(hardware or software).
Object coding:
BS1[0...0]
State=BS1[0] <0,1 BIN>
Narrative:
The VLQJOHELWELQDU\LQSXWrepresentation is used to transmit binary input states in a
packed format. Data objects are always transmitted in complete octets with
unoccupied bit positions set to 0. The following example illustrates the packing of Q
of these data objects.
7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8
0 0 0 n n-1 n-2 n-3 n-4
NOTE:
This variation contains no points status information. 2QOLQHUHVWDUWand such bits
which are part of the ELQDU\LQSXWZLWKVWDWXV variation, are not included in this
variation. The use of the VLQJOHELWELQDU\LQSXW implies that the point is on-line and
all other status bits are cleared (i.e. UHVWDUWbit, FRPPXQLFDWLRQORVWbit, etc. are
cleared).
ABB Automation 25
for REC 523
2.2.4. Binary input with status

Type: static
Description:
The ELQDU\LQSXWZLWKVWDWXV object is used to represent the state of a digital input
point (hardware or software), and it also indicates the status of the point as follows:
• The on-line bit indicates that the binary input point has been read successfully. If
this field is set to off-line, the state of the digital point may not be correct.
• The restart bit indicates that the field device that originated the data object is
currently restarting. This device may be the device reporting this data object.
• The communication lost bit indicates that the device reporting this data object has
lost communication with the originator of the data object.
• The remote forced data bit indicates that the state of the binary input has been
forced to its current state at a device other than the end device.
• The local forced data bit indicates that the state of the binary input has been
forced to its current state at the end device.
• The chatter filter bit indicates that the binary input point has been filtered in order
to remove unnecessary transitions in the state of the point.
• The state bit indicates the current state of the binary input point.
Object coding:
7 6 5 4 3 2 1 0
BS8[0...7]
On-line = BS1[0] <0, off-line; 1, on-line>

Restart = BS1[1] <0, normal; 1, restart>
Communication lost = BS1[2] <0, normal; 1, lost>
Remote forced data = BS1[3] <0, normal; 1, forced>
Local forced data = BS1[4] <0, normal; 1, forced>
Chatter filter = BS1[5] <0, normal; 1, filter on>
Reserved = BS1[6] <0 >
State = BS1[7] <0, 1 BIN>
This variation is used to report the status of controlled objects as follows:

• Object state open (value 10) on-line=1, state=1
• Object state closed (value 01) on-line=1, state=0
• Object state undefined (value 00 on-line=0, state=0
• Object state undefined (value 11) on-line=0, state=1
2.2.5. Binary input change without time

Type: event
26 ABB Automation
for REC 523
Description:
The ELQDU\LQSXWFKDQJHZLWKRXWWLPH object is used to represent the changed state
of the digital input point (hardware or software). It also indicates the status of the
point as follows:
to remove unnecessary transitions in the state of the point.
Object coding:
7 6 5 4 3 2 1 0
BS8[0...7]

Note concerning REC 523:

This variation is used to report the status of controlled objects as follows:
Object state open (value 10) on-line=1, state=1
Object state closed (value 01) on-line=1, state=0
Object state undefined (value 00) on-line=0, state=0
Object state undefined (value 11) on-line=0, state=1
2.2.6. Binary input change with time

Type: event
ABB Automation 27
for REC 523
Description:
The ELQDU\LQSXWFKDQJHZLWKWLPHobject is used to represent the changed state of
the digital input point (hardware or software) and the time at which the state
changed. It also indicates the status of the point as follows:
this field is set to off-line, the state of the digital point may be incorrect.
forced to its current state at the device other than the end device.
to remove unneeded transitions in the state of the point.
The WLPHRIRFFXUUHQFH indicates the absolute time at which the end device detected
the change of state. The accuracy of this time will depend on the accuracy of the
individual device. Time of occurrence is recorded as milliseconds since midnight,
January 1st, 1970, at zero hours, zero minutes, seconds and milliseconds.
Object coding:
FLAG
7 6 5 4 3 2 1 0
Time of occurrence
7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
47 46 45 44 43 42 41 40
{FLAG = BS8[0...7]
Time of occurrence = UI48[0...47] <248-1 ms>
}
FLAG = {
}
28 ABB Automation
for REC 523
2.2.7. Binary output

Type: static
Description:
The ELQDU\RXWSXW object is used to control a digital output point (hardware or
software). The state bit indicates the desired Logic State of digital output point.
Object coding:
BS1[0...0]
Narrative:
Data objects are always transmitted in complete octets with unoccupied bit positions
set to 0. The following example illustrates the packing of Qof these data objects.
7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8
0 0 0 n n-1 n-2 n-3 n-4
2.2.8. Binary output with status

Type: static
Description:
The ELQDU\RXWSXWZLWKVWDWXV object is used to represent the state of a digital output
point (hardware or software), and it also indicates the status of the point as follows:
• The on-line bit indicates that the binary output point has been read successfully. If
• The remote forced data bit indicates that the state of the binary output has been
• The local forced data bit indicates that the state of the binary output has been
• The chatter filter bit indicates that the binary output point has been filtered in
order to remove unnecessary transitions in the state of the point.
• The state bit indicates the current state of the binary output point.
Object coding:
7 6 5 4 3 2 1 0
BS8[0...7]
ABB Automation 29
for REC 523

2.2.9. Control relay output block

Type: static
Description:
• The control relay output block information object contains digital output control
parameters. These parameters define the type and duration of the digital output.
• The control code field indicates the control function to be performed. The
applicability of this code will depend on the type of hardware used in the end
device.
• The count field indicates how many times the control operation should be
performed in succession.
• The on-time field specifies the amount of time the digital output is to be turned on
(may not apply to all control types).
• The off-time field specifies the amount of time the digital output is to be turned
off (may not apply to all control types).
Object coding:
Control code
7 6 5 4 3 2 1 0
Count
7 6 5 4 3 2 1 0
On time
31 0
Off time
31 0
Status/Reserved
7 6 5 4 3 2 1 0
{Control code = BS8[0...7]

Count = UI[0...7] <0...255>
On-time = UI32[0...31] <0...232-1ms>
Off-time = UI32[0...31] <0...232-1ms>
Status = UI7[0...6] <0...127>
Reserved = [7...7] <0...1>
30 ABB Automation
for REC 523
}
Control code = {
Code = BS4[0...3] <0...15>
Queue = BS1[4] <0, normal; 1, requeued>
Clear = BS1[5] <0, normal; 1, clear>
Trip/Close = BS2[6...7] <00, NUL; 01, Close; 10, Trip>
}
Trip/Close:
This field determines the control relay to be activated in a system where a trip and
close relay pair is used to energize and de-energize the field points. The NUL value
in this field can be used to activate the field point select relay only without activating
trip or close relays. In a system without field point select relays, the NUL value
would not perform any control operation. In a system without trip/close relays, this
field should always be NUL to indicate a normal digital control operation where the
exact control point is inherently known. This field does not support both the trip and
close attributes simultaneously, as this is an illegal operation for the system.
Count:
The count field determines how many times the control operation is executed until
completed. If the count is 0, do not execute the control.
Code:
The control block can be used with devices which support control queuing on a
point-per-point basis, or devices which have other control mechanisms. In the
former case, any control command should be queued for the particular point in
question. In the latter case, each control is performed until completion before next
control is accepted for that point.
Queue:
Place the operation at the back of the control queue when it is complete. If the
control code is NUL then no control operation is queued, and the queue is cleared of
all controls including the currently running control, if the clear attribute is set.
When a control function is executed and completed, it is removed from the queue.
If the control block for that operation had the queue attribute set, the control
operation is re-queued (to the end of the queue) for that point.
Clear:
Cancel the currently running operation and remove queued operations on affected
points immediately before activating this new operation (if not NUL). If the control
operation has the clear attribute set, all control operations, including the currently
running control, are removed from the queue and this control operation is
performed.
The meaning of the code field and the operation to be performed is determined by
the following:
0: NUL operation. No operation specified. Only the R attribute is processed.
1: Pulse On - the point(s) is turned on for the specified on-time, turned off for
the specified off-time and left in the off state
2: Pulse Off - The point(s) is turned off for the specified off-time, then turned
on for the specified on-time and left in the on state.
3: Latch On - This latches the point(s) on.
4: Latch Off - This latches the point(s) off.
5 - 15: Undefined
ABB Automation 31
for REC 523
The reserved bit of the control point after the operation can be determined if the
control output is on.
The success or failure of the requested control operation is indicated in the status
field. The meaning of this field is determined as follows:
0: Request accepted, initiated or queued
1: Request not accepted as the operate message was received after the arm
timer timed out. The arm timer was started when the select operation for the
same point was received.
2: No previous matching select message (i.e. an operate message was sent to
activate a control point that was not previously armed with the select
message).
3: Request not accepted as there were formatting errors in the control request
(either select, operate or direct operate).
4: Control operation not supported for this point.
5: Request not accepted, as the control queue is full or the point is already
active.
6: Request not accepted because of control hardware problems.
7-127: Undefined
Notes:
• In REC 523, the DNP close command will be interpreted as a close or earth
command and the DNP trip command will be interpreted as an open or free
command.
• Maximal delay between a select and an operate command is by default 20
seconds. After that time, the response to the operate request will contain the value
2 in the status field (QRWDUPHG).
• If the device is in the local state (remote operations on relays are blocked) or
control operation for single relay is blocked (block input was activated) the
response to the select request will contain the value 4 (QRWVXSSRUWHG)
2.2.10. 32-bit binary counter without flag

Type: static
Description:
• The ELWELQDU\FRXQWHU represents an accumulated value. This can be
accumulated pulses or transitions from a hardware or software point.
• The YDOXH field shows the current value of the counter at the time of reporting or
the last reported value from the originating device. This value will increment
indefinitely until a counter clear operation is performed, in which case the value
is reset to 0.
Object coding:
Value
31 0
Value = UI32[0...31] <0...232-1>
32 ABB Automation
for REC 523
Note:
The use of this variation implies that the input point is on-line and that all other flag
bits are normal (i.e. this variation implies that flag=1: on-line bit is set, the other bits
are cleared - see flag field definition given in section 2.2.6).
2.2.11. 32-bit counter change event without time

Type: event
Description:
The ELWFRXQWHUFKDQJHHYHQWZLWKRXWWLPHrepresents a counter value that has
exceeded a configured deadband. This can be accumulated pulses or transitions from
a hardware or software point. The current value field shows the value of the counter,
which generated the event. The flag field has the same meaning as in the previous
objects, with the following inclusion:
• When set, the UROORYHUbit indicates that the accumulated value has exceeded the
last reported recordable value (232-1). The counter value has been reset to 0 upon
UROORYHU and counting has resumed as normal. This bit is cleared when the counter
value (plus the 5ROORYHU6WDWH) is reported.
Object coding:
FLAG
7 6 5 4 3 2 1 0
Value
31 0
{FLAG = BS8[0...7]
Value = UI32 [0...31] <0...232-1>
}
FLAG = {
Roll-over = BS1[5] <0, normal; 1, roll-over>
}
2.2.12. 32-bit analogue input without flag

Type: static
Description:
ABB Automation 33
for REC 523
• The ELWDQDORJXHLQSXWis an information object used to represent a hardware

or software analogue point. The 32-bit signed value could represent a digitized
signal or a calculated value.
• The FXUUHQWYDOXH field shows the current value of the analogue input at the time
of reporting, or the last value reported from the originating device.
Object coding:
Current value
31 0
Value = I32[0...31] <-231...231-1>

Note:
The use of this variation implies that the input point is on-line and that all other flag
bits are normal (i.e. this variation implies that flag=1: on-line bit is set, the other bits
are cleared - see flag field definition given in section 2.2.5).
2.2.13. 32-bit analogue change event without time

Type: event
Description:
• The ELWDQDORJXHFKDQJHHYHQWZLWKRXWWLPH is an information object used to
represent a changed hardware or software analogue point. The 32-bit signed
value could represent a digitized signal or a calculated value.
• The FXUUHQWYDOXH shows the value of the analogue input at the time specified in
WLPH.
• The IODJ field has the same meaning as for previous objects, with these additions:
• The over-range field indicates that the digitized signal or calculation has
exceeded +231-1 positively, or -231 negatively. The actual value field can be
ignored as its value is undefined.
• The reference check field indicates that the reference signal used to digitize the
analogue input is not suitable, and the resulting digitized value may be incorrect.
Object coding:
FLAG
7 6 5 4 3 2 1 0
Value
31 0
{FLAG = BS8[0...7]
Value = UI32 [0...31] <-231...232-1>
}
FLAG = {
34 ABB Automation
for REC 523

Over-range = BS1[5] <0, normal; 1, over-range>
Reference check = BS1[6] <0, normal; 1, error>
}
2.2.14. 32-bit analogue output status

Type: static
Description:
• The 32-bit analogue output status information object represents the actual value
of a hardware DAC analogue output or software point and associated status.
• The DFWXDOYDOXH field contains the current value of the analogue output.
• The IODJ field has the same meaning as that for the previous object.
Object coding:
FLAG
7 6 5 4 3 2 1 0
Actual value
31 0
{FLAG = BS8 [0...7]

Actual value = I32 [0...31] <-231...232-1>
}
FLAG = {
Reserved = BS1[5] <0>
}
Narrative:
This object can be returned after an analogue output operation has been performed,
in order to determine the success of the operation.
2.2.15. 32-bit analogue output block

Type: static
ABB Automation 35
for REC 523
Description:
• The 32-bit analogue output block information object represents the desired value
of a hardware DAC analogue output or software point. The value represented is
merely logical, as the value may be scaled and/or manipulated before any output
level is set.
• The requested value field contains the desired value of the analogue output. The
actual value of the analogue output is returned in the analogue output status
object.
• The control status field indicates the status of the analogue control operation. The
meaning of this field is as follows:
0:Request accepted, initiated, or queued.
1:Request not accepted as the RSHUDWH message was received after the DUP timer
timed out. The DUPtimer was started when the VHOHFWoperation for the same
point was received.
2:No previous matching VHOHFWmessage (i.e. an RSHUDWHmessage was sent to
activate a control point that was not previously armed with the VHOHFW message)
3:Request not accepted as there were formatting errors in the control request
(either VHOHFW,RSHUDWHorGLUHFWRSHUDWH)
4:Control operation not supported for this point.
5:Request not accepted, as the control queue is full or the point is already active.
6:Request not accepted because of control hardware problems.
7-127:Undefined.
Object coding:
Requested value
31 0
Control status
7 0
Requested value = I32[0...31] <-231...231-1>

Status = UI8 [0...7] <0...255>
2.2.16. Time and date

Description:
The WLPHDQGGDWHobject is an object that represents the absolute time of day and
date. This object should be used for time synchronization.
Object coding:
Absolute time
7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
47 46 45 44 43 42 41 40
48
Absolute time = UI48[0...47] <0...2 -1>
36 ABB Automation
for REC 523
Narrative:
$EVROXWHWLPH is recorded as milliseconds since midnight, January 1st, 1970, at zero
hours, zero minutes, zero seconds, and milliseconds.
2.2.17. Time delay coarse

Description:
The WLPHGHOD\FRDUVH information object represents a relative time that indicates a
time period starting from the time of message reception. This object can be used to
report station availability after cold or warm reset.
Object coding:
Seconds
7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8
Seconds = UI16[0...15] <0...65535 Seconds>
2.2.18. Time delay fine

Description:
The WLPHGHOD\ILQH information object represents a relative time that indicates a time
period starting from the time of message reception. This object can be used in time
synchronization to perform delay measurement calculations or other functions that
require time-based calibration.
Object coding:
Milliseconds
7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8
Milliseconds = UI16[0...15] <0...65535 milliseconds>
2.2.19. Internal indications

Description:
,QWHUQDOLQGLFDWLRQV is an information element used to convey internal states and
diagnostic results of a responding station. This information can be used by a
receiving station to perform error recovery or other actions.
Object coding:
BS1[0...0]
Narrative:
Data objects are always transmitted in complete octets with unoccupied bit positions
set to 0. The following example illustrates the packing of Q of these data objects.
ABB Automation 37
for REC 523
7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8
0 0 0 n n-1 n-2 n-3 n-4
2.2.20. Application identifier

Description:
$SSOLFDWLRQLGHQWLILHUis an information object used to represent an application or
operating system process within a device. This object is used in conjunction with the
application functions of the application layer to control software applications.
Object coding:
This object has no defined format and is simply used as a placeholder. The free-
format qualifier of the application layer should be used to identify the application in
question. If the application is unknown, the $//qualifier should be used to specify
all relevant applications.
2.3. New object types definitions
2.3.1. Byte sequence (string)

Type: static
Description:
The byte sequence (string) object is an information object that represents strings.
This object is intended to be used for transferring string information such as device
name string, initialization, dialling or hang-up string for modem, etc.
This is an extension to the DNP 3.0 specification.
Object coding
This is not a fixed format object, but it is a variable format/size object.
Size 8-bit Data

n Byte 0 Byte 1 ... Byte n-1
Note:
• Value Q(size) is treated as unsigned and can be 0...255.
2.3.2. SPA message

Type: static
38 ABB Automation
for REC 523
Description:
The SPA message object is an information object that represents a transparent SPA
message. This object is intended to be used for transferring transparent SPA
messages.
This is an extension to the DNP 3.0 specification.
Object coding
This is not a fixed format object, but it is a variable format/size object.
Size 8-bit Data

n Byte 0 Byte 1 ... Byte n-1
Transparent SPA communication is a special case. It is divided into two steps. To

communicate using transparent SPA messages, the master station must first send a
DNP write request to the transparent SPA point in REC 523. This message should
contain the desired SPA message. After receiving a DNP response to this request
with an internal indications field showing that the SPA message was accepted
(format error bit reset), a DNP read request for the same point should be issued. The
DNP response to this request will contain a SPA response.
Format of the SPA message used in a DNP write request:
$GGUHVV!&RPPDQG!>&KDQQHO!>&KDQQHO!@@'DWDFDWHJRU\!>3RLQW!>
3RLQW!@@&5!
e.g.
5)&5!
5,&5!
Note: The start character ! and checksum are omitted.
In the returned response to the DNP read request a complete SPA response message
will be included (i.e. with start character , checksum and line feed character):
'5(&;;&5!/)!
';;&5!/)!
Notes:
• Value Q(size) is treated as unsigned and can be 0...255. Object coding is the same
as for a string object. Two different object numbers are used only for
distinguishing the semantics of these two types.
ABB Automation 39
for REC 523
3. Protocol Interface Implementation
3.1. Application to protocol mapping
3.1.1. POD concept

The Protocol Object Dictionary (POD) is a cross-reference table between the REC
523 application and the DNP 3.0 protocol. This table defines what information can
be accessed from the device using the protocol interface. As REC 523 is a
programmable device and may run various application setups (different sets of
function blocks), the POD is also re-configurable. This re-configurable table (called
visible POD) is used during device initialization to create POD used at runtime
(called operational POD). The visible POD can cover all possible device application
setups. At the start-up, all present function blocks will be automatically detected and
only data items of these blocks will be included in the operational POD.
3.1.2. POD configuration

A default version of the visible POD is available in the device software and includes
the mapping of process data and events from all available function blocks, and
communication interface parameters into the DNP protocol. Application settings,
parameters and recorded measurement and disturbance data are not included in this
mapping.
The default POD contents can be uploaded for review and modified using the
Protocol Editing Tool available in CAP 505 Tool Box. Following the changes, the
new POD contents can be downloaded to the REC 523 unit and activated by storing
the changes and resetting the device.
40 ABB Automation
for REC 523
PC POD editing
tool on PC
Edited
visible POD
Download of
Upload for modified POD
review/modification to the device
Default
POD Visible Operational
in program POD POD
memory only at
start-up of initialization of
unconfigured communication
device interface
PODconf
REC 523
)LJ 32'LQ5(&GHYLFH
Modifications of the POD contents may be required due to the following situations:
• a different addressing concept is used in the system because of the master
station’s requirements or limitations in protocol data addressing (re-addressing of
mapped application objects),
• elimination of obsolete function blocks (not used in the application setup),
• elimination of obsolete data and events from active function blocks (data items
not required or not processed by the master station),
3.1.2.1. DNP object map
Object name Object index Default variation Default class

Binary input 1 2 0 or not assigned
Binary input change 2 2 1
Binary output 10 1 0 or not assigned
Binary output block 12 1 Not assigned
Counter 20 5 Not assigned
Counter change event 22 5 3
Analogue input 30 4 0 or not assigned
Analogue input change 32 2 2
Analogue output status 40 2 Not assigned
Analogue output block 41 2 not assigned
Time 50 1 not assigned
Internal indications 80 1 not assigned
String 150 1 not assigned
ABB Automation 41
for REC 523
Transparent SPA 151 1 not assigned
3.1.2.2. DNP classes (default assignment)
Class Assignment
0 (static data) The set of static data important from the process point of view is assigned
to class 0. This solution makes it possible to read all these values using a
single request from the master station (e.g. to update the master station’s
database after communications trouble, power loss, etc.).
1 (event data) All points of type Binary input change event are assigned to this class. By
default, unsolicited reporting of these points is on.
2 (event data) All points of type Analogue input change event are assigned to this class.
By default, unsolicited reporting of these points is on.
3 (event data) All points of type Counter change event are assigned to this class. By
default, unsolicited reporting of these points is on.
3.1.3. Defining the POD contents
3.1.3.1. Visible POD entry format

A visible POD may contain maximum 2700 entries. The number of defined entries
is revision dependent, e.g. the default POD of revision D of REC 523 occupies 2621
entries.
The visible POD can be accessed using Protocol Editing Tool. The attributes in POD
table can be divided into two main categories: general and protocol attributes.
Protocol attributes of visible POD can be further divided into two categories:
• attributes of the application (application object name, data type and operation
type)
• attributes of the communication (object, point class, variation mask, function
mask and unsolicited reporting flag)
A flag parameter “in use” can be used to facilitate removing (masking) of POD
entries from operational POD.
The meaning of each item of a POD entry and its corresponding index is described
in the table below:
Index Name Description

0 Name of application object Application name of REC 523 object; in most cases in
SPA format e.g. F031I001 (input 1 from channel 31),
F031E000 (event 0 from channel 31) etc. with some
exceptions as, for example, LONSPAIN
1 Data type Type of item in the database or type of event
2 Operation type Type of operation that will be performed when
accessing this item
3 DNP object Id DNP object identifier (e.g. 1 for binary inputs, 10 for
binary outputs, etc.)
4 DNP point DNP point number
5 DNP class 0 - 3 number of class, 4 - not assigned
42 ABB Automation
for REC 523
6 Variation mask Mask indicating supported variations:

from lowest significant
bit 0 - variation 1, (00000001)
bit 1 - variation 2, (00000010) etc.
7 DNP function mask Mask indicating supported functions:
from lowest significant
bit 0 - function 1 (Read),
bit 1 - function 2 (Write),
bit 2 - function 3 (Select), etc.
Note: The mask does not cover function 129
(Response) and 130 (Unsolicited message).
8 Reporting flag 0 – disabled, 1- enabled (applies only to events, for
static data always 0)
9 In use flag 0 – not available, 1 – available
The structure of DNP POD is introduced in Fig. 3.1.3.1.-1.
)LJ 3URWRFRO(GLWLQJ7RROZLWK'1332'
The set of generic data types was enumerated for encoding the types of REC 523
application objects in the POD.
Data type codes:
Name Code Description

BOOL 0 Boolean value - 0 or 1
DPBOOL 1 Double point value: 00 - middle, 01 -closed (earthed), 10 - opened
(freed), 11 - faulty
SINT 2 16-bit signed integer
INT 3 16-bit signed integer
DINT 4 32-bit signed integer
USINT 5 16-bit unsigned integer
ABB Automation 43
for REC 523
UINT 6 16-bit unsigned integer

UDINT 7 32-bit unsigned integer
REAL 8 32-bit floating point
TIME 9 32-bit unsigned integer containing number of milliseconds
TOD 10 32-bit unsigned integer containing time of the day since midnight in
100us units
DATE 11 32-bit unsigned integer containing number of days since 01-01-
1980
CLOCK 12 Full time of DNP type used for time synchronization (function)
STRING 13 String value
SPA 14 Transparent SPA message (function)
BYTE 15 8-bit unsigned integer
WORD 16 16-bit unsigned integer
DWORD 17 32-bit unsigned integer
EV_NODAT 18 Event without data
EV_1BIT 19 Event with 1-bit data
EV_2BIT 20 Event with 2-bit data
EV_3BIT 21 Event with 3-bit data (treated as EV_NODAT - phase information
will be ignored)
EV_FLOAT 22 Event with floating point value
EV_INT16 23 Event with 16-bit integer value
EV_INT32 24 Event with 32-bit integer value
EV_COUNT 25 Event with counter value
EV_32BIT 26 Event with 32 bit value
Note:
The set of supported data types can be extended in future releases.
To enable the required conversion of data items before passing them in DNP
messages to the master station or vice versa, a set of operations (conversion routines)
has been defined. Each type of operation is assigned a numeric code used by the
POD.
Operation type codes associated with data:
44 ABB Automation
for REC 523
Operation type Code Description

No operation 0 No special handling, all actions according to DNP and
database type
Select trip 1 Item is used to select trip (open or free) operation
Select close 2 Item is used to select close (close or earth) operation
Operate 3 Item is used to perform selected operation
Direct trip 4 Item is used to perform trip (open or free) operation
Direct close 5 Item is used to perform close (close or earth) operation
Cancel selection 6 Item is used to clear previous selection
Scale by 10 7 Value will be multiplied by 10
Scale by 0.1 10 Value will be multiplied by 0.1
Inverse 1 bit logic 13 0<->1 conversion
Inverse 2 bit logic 14 01<->10 conversion
Always 01 (0 on-line) 15 Conversion for events used to set 01 value
Always 10 (1 on-line) 16 Conversion for events used to set 10 value
Always 00 (0 off-line) 17 Conversion for events used to set 00 value
Always 11 (1 off-line) 18 Conversion for events used to set 11 value
Dummy 0 19 Used for write only items
Operation ACK 20 Meaning is the same as for index 16, but in addition
notification will be sent to application layer about accepting
requested relay operation
Operation NACK 21 Meaning is the same as for index 16, but in addition
notification will be sent to application layer about
NOT accepting requested relay operation
Software reset 22 This entry will be used by reset function
Stay silent 23 This entry will be used to set silent flag (this flag is
not mapped into the database)
Two point low 24 Low order bit of 2-bit value
Two point high 25 High order bit of 2-bit value
Note:
The set of supported operation types can be extended in future releases.
3.1.3.2. POD diagnostics

Each POD table that has been downloaded into the unit has an identification string.
The identification string is used to check the consistency between the POD stored
into REC 523 and the visible POD opened by Protocol Editing Tool. Refer to POD
Tool Operator’s Manual for further information.
ABB Automation 45
for REC 523
)LJ 3URWRFRO(GLWLQJ7RROZLWK2SHQGLDORJRI'1332'
After POD has been downloaded and stored into the unit, it is possible to upload
POD diagnostics from the unit.
)LJ 3URWRFRO(GLWLQJ7RROZLWK32'GLDJQRVWLFV
The meaning of each parameter has been introduced in the table below.
46 ABB Automation
for REC 523
Name Description SPA parameter

Total number of entries Total number of visible POD entries F503V060
This value is determined by the POD structure
size. Both used and unused entries are
counted.
Number of Not In Use Number of entries not in use (“in use” field set F503V061
entries to 0)
This number covers all defined POD entries
with the “in use” flag reset as well as all empty
POD entries which by default have the “in use”
flag also reset.
Number of entries Translation applies only to the entries with “in F503V066
translated into use” flag set, correct or corrected contents, and
operational POD referring to valid objects or events of the
function blocks included in the application
project.
Number of This checking applies only to the entries with F503V062
uncorrectable invalid “in use” flag set.
entries (INV)
Number of corrected This checking applies only to the entries with F503V063
entries (COR) “in use” flag set.
Number of nonexistent This checking applies only to the entries with F503V064
function block entries “in use” flag set.
(NBL)
Number of entries This checking applies only to the entries with F503V065
referring to invalid “in use” flag set.
objects (NOB)
If seen necessary, one can further analyze the result of diagnostics by selecting
“Show data...” (see Fig. 3.1.3.2.-3). Diagnostic details introduces a list of items
belonging to the selected category. The list is sorted out based on the row number of
the item. Using this information, required changes and corrections can be made to
the POD.
ABB Automation 47
for REC 523
)LJ 'LDJQRVWLF'HWDLOV
3.1.3.3. Examples of mapping application data into the DNP protocol

([DPSOHVZLWFKVWDWHPDSSLQJLQWRWKHSURWRFRO
The function block COIND1 is used to report changes in the state of a monitored
switch.
Two kinds of information are available from the COIND1 block:
• current state of the switch - database item F127V001,
• events indicating changes of the switch position: E0, E1, E2 and E3.
The switch can be in one of four states: open, closed, middle, faulty.
State information is encoded on 2 bits.
In the DNP protocol, this information is mapped as:
• ELQDU\LQSXWZLWKVWDWXV point - for the current state of the switch,
• related ELQDU\LQSXWFKDQJH points - for events.
Two consecutive binary inputs are used to transfer switch state. The following
encoding of the switch state is used in the DNP protocol:
• open values 1/0,
• closed values 0/1,
• middle values 0/0,
• faulty values 1/1.
48 ABB Automation
for REC 523
Function Op. In
Meaning* DB name DB type Object Point Class VM FM UR
block* type use
COIND1 Position LO F127V001 DPBOOL 24 1 1400 0 0x0003 0x00000001 0 1
Position HI F127V001 DPBOOL 25 1 1401 0 0x0003 0x00000001 0 1
Change to F127E000 EV_2BIT 15 2 1400 1 0x0002 0x00380001 1 1
open
close
faulty
middle
open
close
faulty
middle
*These columns are not part of the POD.

)LUVWWZRHQWULHVVWDWLFGDWDVZLWFKSRVLWLRQGDWDEDVHREMHFW
• Database type: double-point binary
• Operation type: no operation (data not converted)
• Object: binary input (1)
• DNP points: 1400, 1401
• Data item assigned to class 0 (containing important static data)
• Variation supported: 3 - binary input with status (mask: 00000011)
• Function supported: 1 - read function
• Not reported spontaneously (available only on read request)
• Entry in use
1H[WHQWULHVHYHQWGDWDVZLWFKSRVLWLRQFKDQJH
• Database type: 2-bit event
• Operation type: according to the meaning conversion to on-line value 0, on-line
value 1, on-line value 1, on-line value 0, on-line value 1, on-line value 0, on-line
value 1, on-line value 0
• Object: binary input change: 2
• DNP points: 1400, 1401 (must be the same as for static data)
• Data item assigned to class 1 (containing all binary input change events)
• Variation supported: 2 - binary input change with time (mask: 00000010)
• DNP functions supported: 1 - read , 22 - assign class, 20 and 21 - spontaneous
reporting on and off
• Reported spontaneously
• Entries in use
([DPSOHFRQWUROFRPPDQGPDSSLQJWRWKHSURWRFRO
ABB Automation 49
for REC 523
The function block CODC1 is used to control and monitor the position of a
disconnector switch. Two types of control operations are available:
• one-step GLUHFWcommand - F122V004 and F122V005 for direct open and direct
close,
• two-step VHOHFWH[HFXWH commands - F122V006 and F122V007 to select open and
close, F122V011 to execute the selected operation and F122V010 to cancel the
selection.
Feedback information about the current state of the switch is available from the
F122V001 object.
In the DNP protocol these data items are mapped as:
• control relay output block - for control commands,
• related binary output with status - for the current state of the switch.
The following encoding of the switch state is used in the DNP protocol:
• open - the input is on-line and has the value 1,
• closed - the input is on-line and has the value 0,
• middle - the input is off-line and has the value 0,
• faulty - the input is off-line and has the value 1,
The DNP protocol provides close and trip commands (trip command corresponds to
open).
Function Op. In
block* type use
CODC1 Direct open F122V004 BOOL 4 12 2200 4 0x0001 0x0000003C 0 1
Direct close F122V005 BOOL 5 12 2200 4 0x0001 0x0000003C 0 1
Open select F122V006 BOOL 1 12 2200 4 0x0001 0x0000003C 0 1
Close select F122V007 BOOL 2 12 2200 4 0x0001 0x0000003C 0 1
Execute F122V010 BOOL 3 12 2200 4 0x0001 0x0000003C 0 1
Cancel F122V011 BOOL 6 12 2200 4 0x0001 0x0000003C 0 1
Position F122V001 DPBOOL 0 10 2200 0 0x0002 0x00000001 0 1

6L[HQWULHVFRQWUROFRPPDQGV
• Database type: binary value
• Operation type: according to the meaning - direct open, direct close, select open,
close select, execute, cancel selection
• Object: control relay output block: 12
• DNP point: 2200
• Data item not assigned to any class
• Variation supported: 1 (the only available, mask: 00000001)
• DNP functions supported: 3-select, 4-operate, 5-direct operate and 6-direct
operate no ACK
• Not reported spontaneously
• Entries in use
50 ABB Automation
for REC 523
/DVWHQWU\VWDWLFGDWDSRVLWLRQ
• Database type: double-point binary value
• Operation type: no operation (data not converted)
• Object: binary output (10)
• DNP point: 2200 must be the same as for command
• Data item assigned to class 0 (containing important static data)
• Variation supported: 2 - binary input with status (mask: 00000010)
• DNP function supported: 1- read
• Entry in use
([DPSOHPDSSLQJRIDQDORJXHLQSXWZLWKOLPLWDQGGHOWDVXSHUYLVLRQWRWKH
SURWRFRO
The MECU1A function block provides neutral current measurement and two
methods of supervising this signal - limit (high warning and high alarm) and
threshold (delta change).
Two kinds of information are available from the MECU1A block:
• neutral current value - database item F201I001,
• events that indicate crossing of the limit levels (E0, E1, E2 and E3) or the
threshold level (E5).
In the DNP protocol these items are mapped as:
• DQDORJXHLQSXWpoint - for static value of neutral current,
• related DQDORJXHLQSXWFKDQJHZLWKRXWWLPHpoints - for events.
In addition, since the DQDORJXHLQSXWFKDQJHtype does not identify the cause of
event (which level has been crossed), the events E0, E1, E2 and E3 are mapped as
ELQDU\LQSXWFKDQJHZLWKWLPH points (separate for warning and for alarm).
Function Op. In
block* type use
MECU1A Io F201I001 REAL 7 30 50 0 0x0004 0x00000001 0 1
Io HW reset F201E000 EV_FLOAT 15 1 50 4 0x0003 0x00000001 0 1
Io HW activated F201E001 EV_FLOAT 16 1 50 4 0x0003 0x00000001 0 1
Io HA reset F201E002 EV_FLOAT 15 1 51 4 0x0003 0x00000001 0 1
Io HA activated F201E003 EV_FLOAT 16 1 51 4 0x0003 0x00000001 0 1
Io delta F201E005 EV_FLOAT 7 32 50 2 0x0001 0x00380001 1 1
ABB Automation 51
for REC 523
)LUVWHQWU\DQDORJXHVWDWLFGDWD'%REMHFW
• Database type: floating point
• Operation type: multiplied by 10 (to achieve maximum accuracy since data will
be sent as 32-bit integers)
• Object: analogue input (30)
• Point: 50
• Data item assigned to class 0 containing important static data
• Variation: 3 - 32-bit analogue input without status (mask: 00000100)
• DNP function supported: 1 - read
• Entry in use
/DVWHQWULHVDQDORJXHHYHQWGDWD
• Database type: floating-point event
• Operation type: value multiplied by 10 (to achieve maximum accuracy since data
will be sent as 32-bit integers)
• Object: analogue input change event (32)
• Point: 50 (the same as for static data)
• Data item assigned to class 2 (containing analogue change events)
• Variation supported: 1 - 32-bit analogue input change without time
(mask: 00000001)
• Entries in use
(QWULHVELQDU\LQSXWGDWD
• Operation type: according to the meaning (on line 1 when warning/alarm
activated and on line 0 when alarm/warning deactivated)
• Object: binary input (1)
• Points: 50 for warning and 51 for alarm state (note that these point numbers have
nothing in common with point numbers for analogue measurements as they
represent different kind of information - binary, NOT analogue)
• Data item not assigned to class (4)
• Variation supported: 1 – one bit binary input and 2 - binary input with status
(mask: 00000011)
• DNP functions supported: 1 - read
• Entries in use
(QWULHVELQDU\HYHQWGDWD
52 ABB Automation
for REC 523
• Operation type: according to the meaning (on line 1 when warning/alarm

activated and on line 0 when alarm/warning deactivated)
• Object: binary input change event (2)
• Points: 50 for warning and 51 for alarm state (must be the same point numbers as
assigned to corresponding binary input data defined in entries 2-5)
• Data item assigned to class 1 (containing binary change events)
• Variation supported: 2 - binary input change with time (mask: 00000010)
• Entries in use
Note:
REC 523 application provides only dynamic information (events) on warning or
alarm condition in analogue signal supervision. These events are mapped to DNP
binary input change events (e.g. entries 6-9 defined above). Static data objects
corresponding to the present warning or alarm condition can be, however, supported
by the protocol interface with value updates based on the received events. These
“shadow” static data objects are mapped to DNP binary inputs (entries 2-5 defined
above).
Generally, for any pair of REC 523 events representing on/off state it is possible to
define a “shadow” static data object. This extension was made due to some DNP
master devices that require corresponding static data for all change events.
3.2. Protocol address map based on default POD

The mapping presented in this section corresponds to the default POD.
For a given application setup, the visible POD can be reconfigured to omit unused
function blocks and data items, and to change the point numbers if required. Each
data item in the DNP protocol is uniquely addressed using the pair object/point.
Object describes the type of the data item (digital input, counter, analogue output,
etc.) and point indicates the specific instance of the data item. In this section all data
accessible via the DNP interface are placed in separate tables for each REC 523
function block.
Please refer to chapter “Point numbering overall rules” on page 24 for more
information about the rule 3, which applies to such groupings as binary inputs and
outputs, counters, analogue outputs and inputs.
Function block MEAI1

Description Name Object Point Variation Class Access function Values
Input MEAI1 value valid/invalid F213E008 1 5400 1,2 - Read 0 – valid
F213E009 1 – invalid
Input MEAI1 high warning reset/ F213E000 1 5401 1,2 - Read 0 – reset
activated F213E001 1 – activated
Input MEAI1 high alarm reset/ F213E002 1 5402 1,2 - Read 0 – reset
Input MEAI1 low warning reset/ F213E004 1 5403 1,2 - Read 0 – reset
ABB Automation 53
for REC 523

Input MEAI1 low alarm reset/ F213E006 1 5404 1,2 - Read 0 – reset
Input MEAI1 value valid/invalid F213E008 2 5400 2 1 Read/Unsolicited 0 – valid
F213E009 response 1 – invalid
Input MEAI1 high warning reset/ F213E000 2 5401 2 1 Read/Unsolicited 0 – reset
activated F213E001 response 1 – activated
Input MEAI1 high alarm reset/ F213E002 2 5402 2 1 Read/Unsolicited 0 – reset
Input MEAI1 low warning reset/ F213E004 2 5403 2 1 Read/Unsolicited 0 – reset
Input MEAI1 low alarm reset/ F213E006 2 5404 2 1 Read/Unsolicited 0 – reset
Input MEAI1 F213I001 30 5400 3 0 Read -10000000...10000000
-10000.000...10000.000
Input MEAI1 delta/high/low/ F213E000 32 5400 1 2 Read/Unsolicited -10000000...10000000
warning alarm F213E001 response -10000.000...10000.000
F213E002
F213E003
F213E004
F213E005
F213E006
F213E007
F213E011

Input MEAI2 F214I001 30 5410 3 0 Read -10000000..10000000
-10000.000...10000.000
F214E002
F214E003
F214E004
F214E005
F214E006
F214E007
F214E011
54 ABB Automation
for REC 523

-10000.000...10000.000
F215E002
F215E003
F215E004
F215E005
F215E006
F215E007
F215E011

-10000.000...10000.000
ABB Automation 55
for REC 523

F216E002
F216E003
F216E004
F216E005
F216E006
F216E007
F216E011

-10000.000...10000.000
F217E002
F217E003
F217E004
F217E005
F217E006
F217E007
F217E011

56 ABB Automation
for REC 523

-10000.000...10000.000
F218E002
F218E003
F218E004
F218E005
F218E006
F218E007
F218E011


-10000.000...10000.000
F219E002
F219E003
F219E004
F219E005
F219E006
F219E007
F219E011
ABB Automation 57
for REC 523

-10000.000...10000.000
F220E002
F220E003
F220E004
F220E005
F220E006
F220E007
F220E011
Function block MECU1A

Io high warning reset/activated F201E000 1 50 1, 2 - Read 0 – reset
F201E001 1- activated
Io high alarm reset/activated F201E002 1 51 1, 2 - Read 0 – reset
Io high warning reset/activated F201E000 2 50 2 1 Read/Unsolicited 0 – reset
F201E001 response 1- activated
Io high alarm reset/activated F201E002 2 51 2 1 Read/Unsolicited 0 – reset
Io F201I001 30 50 3 0 Read 0..200000
0.0A..20000.0A
Io delta/high warning/alarm F201E000 32 50 1 2 Read/Unsolicited 0..200000
F201E001 response 0.0A..20000.0A
F201E002
F201E003
F201E005
Function block MECU1B

Io high warning reset/activated F203E000 1 150 1, 2 - Read 0 - reset
58 ABB Automation
for REC 523

Io high alarm reset/activated F203E002 1 151 1 ,2 - Read 0 - reset
Io high warning reset/activated F203E000 2 150 2 1 Read/Unsolicited 0 - reset
Io high alarm reset/activated F203E002 2 151 2 1 Read/Unsolicited 0 - reset
Io (LV side) F203I001 30 150 3 0 Read 0..200000
0.0A..20000.0A
Io delta/high warning/alarm F203E000 32 150 1 2 Read/Unsolicited 0..200000
F203E001 response 0.0A..20000.0A
F203E002
F203E003
F203E005
Function block MECU3A

IL1 high warning reset/activated F200E000 1 200 1, 2 - Read 0 – reset
IL1 high alarm reset/activated F200E006 1 203 1, 2 - Read 0 – reset
IL1 low warning reset/activated F200E012 1 206 1, 2 - Read 0 – reset
IL1 low alarm reset/activated F200E018 1 209 1, 2 - Read 0 – reset
IL1 high warning reset/activated F200E000 2 200 2 1 Read/Unsolicited 0 – reset
IL1 high alarm reset/activated F200E006 2 203 2 1 Read/Unsolicited 0 – reset
IL1 low warning reset/activated F200E012 2 206 2 1 Read/Unsolicited 0 – reset
ABB Automation 59
for REC 523

IL1 low alarm reset/activated F200E018 2 209 2 1 Read/Unsolicited 0 – reset
IL1 F200I001 30 200 3 0 Read 0..200000
0.0A..20000.0A
IL2 F200I002 30 201 3 0 Read 0..200000
0.0A..20000.0A
IL3 F200I003 30 202 3 0 Read 0..200000
0.0A..20000.0A
IL1 delta/high/low/warning/alarm F200E000 32 200 1 2 Read/Unsolicited 0..200000
F200E001 response 0.0A..20000.0A
F200E006
F200E007
F200E012
F200E013
F200E018
F200E019
F200E025
F200E003 response 0.0A..20000.0A
F200E008
F200E009
F200E014
F200E015
F200E020
F200E021
F200E027
F200E005 response 0.0A..20000.0A
F200E010
F200E011
F200E016
F200E017
F200E022
F200E023
F200E029
Function block MECU3B

60 ABB Automation
for REC 523

IL1 (LV side) F202I001 30 250 3 0 Read 0..200000
0.0A..20000.0A
IL2 (LV side) F202I002 30 251 3 0 Read 0..200000
0.0A..20000.0A
IL3 (LV side) F202I003 30 252 3 0 Read 0..200000
0.0A..20000.0A
F202E001 response 0.0A..20000.0A
F202E006
F202E007
F202E012
F202E013
F202E018
F202E019
F202E025
F202E003 response 0.0A..20000.0A
F202E008
F202E009
F202E014
F202E015
F202E020
F202E021
F202E027
ABB Automation 61
for REC 523

F202E005 response 0.0A..20000.0A
F202E010
F202E011
F202E016
F202E017
F202E022
F202E023
F202E029
Function block MEDREC16

Recorder memory is full off/on F225E000 2 800 2 1 Read/Unsolicited 0 – off

F225E001 response 1- on
Overwrite of recording F225E003 2 801 2 1 Read/Unsolicited 1- overwritten
response
Configuration error F225E005 2 802 2 1 Read/Unsolicited 1- error
response
Recorder triggered F225E031 2 803 2 1 Read/Unsolicited 1- triggered
response
Reset memory F225M002 10/12 804 1 - Read/Write 1 or trip - reset
Function block MEFR1

Frequency high warning reset/ F208E000 1 700 1,2 - Read 0 – reset
activated F208E001 1- activated
Frequency high alarm reset/ F208E002 1 701 1,2 - Read 0 – reset
Frequency low warning reset/ F208E004 1 702 1,2 - Read 0 – reset
Frequency low alarm reset/ F208E006 1 703 1,2 - Read 0 – reset
Frequency high warning reset/ F208E000 2 700 2 1 Read/Unsolicited 0 – reset
activated F208E001 response 1- activated
Frequency high alarm reset/ F208E002 2 701 2 1 Read/Unsolicited 0 – reset
Frequency low warning reset/ F208E004 2 702 2 1 Read/Unsolicited 0 – reset
Frequency low alarm reset/ F208E006 2 703 2 1 Read/Unsolicited 0 – reset
Frequency F208I001 30 700 3 0 Read 1000..7500
10.00Hz..75.00Hz
Frequency delta/high/low/warning F208E000 32 700 1 2 Read/Unsolicited 1000..7500
alarm F208E001 response 10.00Hz..75.00Hz
F208E002
F208E003
F208E004
F208E005
F208E006
F208E007
F208E009
62 ABB Automation
for REC 523
Function block MEPE7

Reset flag F207V418 1 400 1,2 - Read 0= All values valid
1= "Last save Pos." values
valid
P3 high warning reset/activated F207E000 1 401 1,2 - Read 0 – reset
P3 high alarm reset/activated F207E002 1 402 1,2 - Read 0 – reset
Q3 high warning reset/activated F207E004 1 403 1,2 - Read 0 – reset
Q3 high alarm reset/activated F207E006 1 404 1,2 - Read 0 – reset
P3 low warning reset/activated F207E008 1 405 1,2 - Read 0 – reset
P3 low alarm reset/activated F207E010 1 406 1,2 - Read 0 – reset
Q3 low warning reset/activated F207E012 1 407 1,2 - Read 0 – reset
Q3 low alarm reset/activated F207E014 1 408 1,2 - Read 0 – reset
P3 high warning reset/activated F207E000 2 401 2 1 Read/Unsolicited 0 – reset
P3 high alarm reset/activated F207E002 2 402 2 1 Read/Unsolicited 0 – reset
Q3 high warning reset/activated F207E004 2 403 2 1 Read/Unsolicited 0 – reset
Q3 high alarm reset/activated F207E006 2 404 2 1 Read/Unsolicited 0 – reset
P3 low warning reset/activated F207E008 2 405 2 1 Read/Unsolicited 0 – reset
P3 low alarm reset/activated F207E010 2 406 2 1 Read/Unsolicited 0 – reset
Q3 low warning reset/activated F207E012 2 407 2 1 Read/Unsolicited 0 – reset
Q3 low alarm reset/activated F207E014 2 408 2 1 Read/Unsolicited 0 - reset
P3 F207I001 30 400 3 0 Read -999999..
999999
-999999kW..
999999kW
Q3 F207I002 30 401 3 0 Read -999999..
999999
-999999kvar..
999999kvar
Power factor PDF F207I003 30 404 3 - Read -100..100
-1.00..1.00
Power factor PF F207I004 30 405 3 - Read -100..100
-1.00..1.00
P3 demand F207I005 30 406 3 - Read -999999..
999999
-999999kW..
999999kW
Q3 demand F207I006 30 407 3 - Read -999999..
999999
-999999kvar..
999999kvar
ABB Automation 63
for REC 523

Last registered active energy F207V414 30 408 3 - Read 0...999999
0...999999 kWh
Last registered reversed active F207V415 30 409 3 - Read 0...999999
energy 0...999999 kWh
Last registered reactive energy F207V416 30 410 3 - Read 0...999999 0...999999
kvah
Last registered reversed reactive F207V417 30 411 3 - Read 0...999999 0...999999
energy kvah
P3 delta/high/low/warning/alarm F207E000 32 400 1 2 Read/Unsolicited -999999..
F207E001 response 999999
F207E002 -999999kW..
F207E003 999999kW
F207E008
F207E009
F207E010
F207E011
F207E017
Q3 delta/high/low/warning/alarm F207E004 32 401 1 2 Read/Unsolicited -999999..
F207E005 response 999999
F207E006 -999999kvar..
F207E007 999999kvar
F207E012
F207E013
F207E014
F207E015
F207E019
S3 delta F207E021 32 402 1 2 Read/Unsolicited -999999...999999
response -999999 kVa
DPF delta F207E023 32 404 1 2 Read/Unsolicited -100...100
response -1.00...1.00
Active energy delta F207E025 32 408 1 2 Read/Unsolicited 0...899999
response 0 kWh...999999
Reversed active energy delta F207E027 32 409 1 2 Read/Unsolicited 0...899999
response 0 kWh...999999
Reactive energy delta F207E029 32 410 1 2 Read/Unsolicited 0...899999
response 0 kVarh...999999
Reversed reactive energy delta F207E030 32 411 1 2 Read/Unsolicited 0...899999
response 0 kVarh...999999
Function block MEVO1A

Uo high warning reset/activated F205E000 1 100 1, 2 - Read 0 - reset
Uo high alarm reset/activated F205E002 1 101 1, 2 - Read 0 - reset
Uo high warning reset/activated F205E000 2 100 2 1 Read/Unsolicited 0 - reset
Uo high alarm reset/activated F205E002 2 101 2 1 Read/Unsolicited 0 - reset
Uo F205I001 30 100 3 0 Read 0..150000
0.000kV..150.000kV
Uo delta/high alarm/warning F205E000 32 100 1 2 Read/Unsolicited 0..150000
F205E001 response 0.000kV..150.000kV
F205E002
F205E003
F205E005
64 ABB Automation
for REC 523
Function block MEVO1B

Uo high warning reset/activated F226E000 1 120 1, 2 - Read 0 - reset
Uo high alarm reset/activated F226E002 1 121 1, 2 - Read 0 - reset
Uo high warning reset/activated F226E000 2 120 2 1 Read/Unsolicited 0 - reset
Uo high alarm reset/activated F226E002 2 121 2 1 Read/Unsolicited 0 - reset
Uo (LV side) F226I001 30 120 3 0 Read 0..150000
0.000kV..150.000kV
Uo delta/high alarm/warning F226E000 32 120 1 2 Read/Unsolicited 0..150000
F226E001 response 0.000kV..150.000kV
F226E002
F226E003
F226E005
Function block MEVO3A

U1 high warning reset/activated F204E000 1 300 1, 2 - Read 0 – reset
U1 high alarm reset/activated F204E006 1 303 1, 2 - Read 0 – reset
U1 low warning reset/activated F204E012 1 306 1, 2 - Read 0 – reset
U1 low alarm reset/activated F204E018 1 309 1, 2 - Read 0 – reset
ABB Automation 65
for REC 523

U1 high warning reset/activated F204E000 2 300 2 1 Read/Unsolicited 0 – reset
U1 high alarm reset/activated F204E006 2 303 2 1 Read/Unsolicited 0 – reset
U1 low warning reset/activated F204E012 2 306 2 1 Read/Unsolicited 0 – reset
U1 low alarm reset/activated F204E018 2 309 2 1 Read/Unsolicited 0 – reset
66 ABB Automation
for REC 523

U1 U12 F204I001 30 300 3 0 Read 0..99999
0.00kV..999.99kV
U2 U23 F204I002 30 301 3 0 Read 0..99999
0.00kV..999.99kV
U3 U31 F204I003 30 302 3 0 Read 0..99999
0.00kV..999.99kV
U1 delta/high/low/warning/alarm F204E000 32 300 1 2 Read/Unsolicited 0..99999
F204E001 response 0.00kV..999.99kV
F204E006
F204E007
F204E012
F204E013
F204E018
F204E019
F204E008
F204E009
F204E014
F204E015
F204E010
F204E011
F204E016
F204E017
F204E020
F204E021
F204E022
F204E023
F204E038
F204E039
F204E044
F204E045
F204E050
F204E051
F204E057
F204E040
F204E041
F204E046
F204E047
F204E052
F204E053
F204E059
F204E042
F204E043
F204E048
F204E049
F204E054
F204E055
F204E061
ABB Automation 67
for REC 523
Function block MEVO3B

68 ABB Automation
for REC 523

U1 U12 (LV side) F206I001 30 350 3 0 Read 0..99999
0.00kV..999.99kV
U2 U23 (LV side) F206I002 30 351 3 0 Read 0..99999
0.00kV..999.99kV
U3 U31 (LV side) F206I003 30 352 3 0 Read 0..99999
0.00kV..999.99kV
F206E006
F206E007
F206E012
F206E013
F206E018
F206E019
F206E025
ABB Automation 69
for REC 523

F206E008
F206E009
F206E020
F206E021
F206E014
F206E015
F206E027
F206E010
F206E011
F206E016
F206E017
F206E022
F206E023
F206E029
F206E038
F206E039
F206E044
F206E045
F206E050
F206E051
F206E057
F206E040
F206E041
F206E046
F206E047
F206E052
F206E053
F206E059
F206E042
F206E043
F206E048
F206E049
F206E054
F206E055
F206E061
Function block AR5FUNC

Status of LOCKOUT signal F080O014 1 5100 1,2 - Read 0 – Not active
1 - Active
AR-function currently in use or not F080S004 1 5101 1,2 - Read 0 – Not in use
1 – In use
Auto-reclosing sequence Ended/ F080E000 2 5102 2 1 Read/Unsolicited 0 – ended
Started F080E001 response 1 – started
AR (shots 1...5) initiated by AR1 - F080E002 2 5103 2 1 Read/Unsolicited 1 – initiated
response
response
response
70 ABB Automation
for REC 523

response
AR sequence initiated by AR1 F080E013 2 5107 2 1 Read/Unsolicited 1 – successful
successful response
successful response
successful response
successful response
CB opening failed via auto- F080E026 2 5111 2 1 Read/Unsolicited 1 – failed
recloser response
CB closing failed via auto-recloser F080E027 1 5112 2 1 Read/Unsolicited 1 – failed
response
CB closing inhibited F080E028 2 5113 2 1 Read/Unsolicited 1 – inhibited
response
AR not in use/in use F080E034 2 5101 2 1 Read/Unsolicited 0 – used
F080E034 response 1 – not in use
LOCKOUT Reset/activated F080E044 2 5100 2 1 Read/Unsolicited 0 – reset
F080E045 response 1 – activated
Reset Register F080V013 10/12 5100 2/1 - Read/Select/ 1or trip – reset
Operate/ Direct
operate
AR5Func status F080V001 30 5100 1,2 - Read 0...5
Current value of Shot Pointer F080V002 30 5101 1,2 - Read 1...7
Operation mode of AR-function F080S003 40/41 5100 1 - Read/Select/ 0 – OFF
Operate/ Direct 1 – ON
operate 2 – selected by ON input
Auto-reclose shot 1 Concluded/In F081E000 2 5140 2 1 Read/Unsolicited Concluded
progress F081E001 response In progress
AR shot 1 initiated via AR1 F081E002 2 5141 2 1 Read/Unsolicited 1 – initiated
response
response
response
response
AR short 1 succesfull F081E006 2 5145 2 1 Read/Unsolicited 1 – successful
response
Auto-reclose shot 2 Concluded/In F082E000 2 5150 2 1 Read/Unsolicited 0 - Concluded
progress F082E001 response 1 - In progress
response
response
response
response
response
Auto-reclose shot 3 Concluded/In F083E000 2 5160 2 1 Read/Unsolicited 0 -Concluded
progress F083E001 response 1 –In progress
response
response
ABB Automation 71
for REC 523

response
response
response
response
response
response
response
response
response
response
response
response
response
Final trip F086E000 2 5190 2 1 Read/Unsolicited 1- trip
response
Final trip via AR1 F086E001 2 5191 2 1 Read/Unsolicited 1- trip
response
response
response
response
Function block CUB3LOW

START signal from ∆ I > stage F051O001 1 1100 1,2 - Read 0 – reset
1 - activated
TRIP signal from ∆ I > stage

F051O002 1 1101 1,2 - Read 0 – reset
1 – activated
CBFP signal from ∆ I > stage

F051O003 1 1102 1,2 - Read 0 – reset
1 – activated
BS1 signal of ∆ I > stage

F051I005 1 1103 1,2 - Read 0 – reset
1 – activated
BS2 signal of ∆ I > stage

F051I006 1 1104 1,2 - Read 0 – reset
1 – activated
START signal from ∆ I > stage

F051E000 2 1100 2 1 Read/Unsolicited 0 – reset
F051E001 response 1 - activated
reset/activated
72 ABB Automation
for REC 523
TRIP signal from ∆ I > stage

reset/activated
CBFP signal from ∆ I > stage F051E004 2 1102 2 1 Read/Unsolicited 0 – reset

reset/activated
BS1 signal of ∆ I > stage reset/

activated
BS2 signal of ∆ I > stage reset/

activated
Test mode of ∆ I > stage off/on

F051E010 2 1114 2 1 Read/Unsolicited 0 – off
F051E011 response 1 – on
Function block DEF2HIGH

START signal from Io >>→ F041O001 1 1350 1,2 - Read 0 – reset
1 - activated
TRIP signal from Io >>→ F041O002 1 1351 1,2 - Read 0 – reset
1 – activated
CBFP signal from Io >>→ F041O003 1 1352 1,2 - Read 0 – reset
1 – activated
BS1 signal of Io >>→ F041I005 1 1353 1,2 - Read 0 – reset
1 – activated
BS2 signal of Io >>→ F041I006 1 1354 1,2 - Read 0 – reset
1 – activated
START signal from Io >>→ reset/ F041E000 2 1350 2 1 Read/Unsolicited 0 – reset
activated
TRIP signal from Io >>→ reset/ F041E002 2 1351 2 1 Read/Unsolicited 0 – reset
activated
CBFP signal from Io >>→ reset/ F041E004 2 1352 2 1 Read/Unsolicited 0 – reset
activated
BS1 signal of Io >>→ reset/ F041E006 2 1353 2 1 Read/Unsolicited 0 – reset
activated
BS2 signal of Io >>→ reset/ F041E008 2 1354 2 1 Read/Unsolicited 0 – reset
activated
Test mode of Io >>→ off/on F041E010 2 1355 2 1 Read/Unsolicited 0 – off
Function block DEF2LOW

START signal from Io >→ F040O001 1 1300 1,2 - Read 0 – reset
1 - activated
TRIP signal from Io >→ F040O002 1 1301 1,2 - Read 0 – reset
1 – activated
CBFP signal from Io >→ F040O003 1 1302 1,2 - Read 0 – reset
1 – activated
BS1 signal of Io >→ F040I005 1 1303 1,2 - Read 0 – reset
1 – activated
BS2 signal of Io >→ F040I006 1 1304 1,2 - Read 0 – reset
1 – activated
START signal from Io >→ reset/ F040E000 2 1300 2 1 Read/Unsolicited 0 – reset
activated
ABB Automation 73
for REC 523

TRIP signal from Io >→ reset/ F040E002 2 1301 2 1 Read/Unsolicited 0 – reset
CBFP signal from Io >→ reset/ F040E004 2 1302 2 1 Read/Unsolicited 0 – reset

BS1 signal of Io >→ reset/ F040E006 2 1303 2 1 Read/Unsolicited 0 – reset

activated
BS2 signal of Io >→ reset/ F040E008 2 1304 2 1 Read/Unsolicited 0 – reset
Test mode of Io >→ off/on F040E010 2 1320 2 1 Read/Unsolicited 0 – off

Function block DOC6HIGH

START signal from F036O003 1 1250 1,2 - Read 0 – reset
3I >>→ stage 1 - activated
TRIP signal from 3I >>→ stage F036O004 1 1251 1,2 - Read 0 – reset
1 – activated
CBFP signal from 3I >>→stage F036O005 1 1252 1,2 - Read 0 – reset
1 – activated
DIRECTION signal from F036O001 1 1253 1,2 - Read 0 – reset
3I >>→ stage 1 – activated
BSOUT signal from F036O002 1 1254 1,2 - Read 0 – reset

3I >>→ stage 1 – activated
BS1 signal of 3I >>→ stage F036I016 1 1255 1,2 - Read 0 – reset

1 – activated
BS2 signal of 3I >>→ stage F036I017 1 1256 1,2 - Read 0 – reset
1 – activated
START signal from 3I >>→stage F036E000 2 1250 2 1 Read/Unsolicited 0 – reset
reset/activated
TRIP signal from 3I >>→stage F036E002 2 1251 2 1 Read/Unsolicited 0 – reset
reset/activated
CBFP signal from 3I >>→stage F036E004 2 1252 2 1 Read/Unsolicited 0 – reset
reset/activated
DIRECTION signal from F036E008 2 1253 2 1 Read/Unsolicited 0 – reset
3I >>→stage F036E009 response 1 – activated
reset/activated
BSOUT signal from F036E006 2 1254 2 1 Read/Unsolicited 0 – reset
3I >>→stage F036E007 response 1 – activated
reset/activated
BS1 signal of 3I >>→ stage F036E010 2 1255 2 1 Read/Unsolicited 0 – reset
reset/activated F036E011 response 1 – activated
BS2 signal of 3I >>→ stage F036E012 2 1256 2 1 Read/Unsolicited 0 – reset

Test mode of 3I >>→ stage off/ F036E014 2 1257 2 1 Read/Unsolicited 0 – off

on
74 ABB Automation
for REC 523
Function block DOC6LOW

START signal from 3I >→stage F035O002 1 1200 1,2 - Read 0 – reset
1 - activated
TRIP signal from 3I >→ stage F035O003 1 1201 1,2 - Read 0 – reset
1 – activated
CBFP signal from 3I >→ stage F035O004 1 1202 1,2 - Read 0 – reset
1 – activated
DIRECTION signal from F035O001 1 1203 1,2 - Read 0 – reset
3I >→stage 1 – activated
BS1 signal of 3I >→ stage F035I016 1 1204 1,2 - Read 0 – reset

1 – activated
BS2 signal of 3I >→ stage F035I017 1 1205 1,2 - Read 0 – reset
1 – activated
START signal from 3I >→stage F035E000 2 1200 2 1 Read/Unsolicited 0 – reset
reset/activated
TRIP signal from 3I >→ stage F035E002 2 1201 2 1 Read/Unsolicited 0 – reset
CBFP signal from 3I >→ stage F035E004 2 1202 2 1 Read/Unsolicited 0 – reset

DIRECTION signal from F035E006 2 1203 2 1 Read/Unsolicited 0 – reset

3I >→ stage F035E007 response 1 – activated
reset/activated
BS1 signal of 3I >→ stage reset/ F035E008 2 1204 2 1 Read/Unsolicited 0 – reset
activated
BS2 signal of 3I >→ stage reset/ F035E010 2 1205 2 1 Read/Unsolicited 0 – reset
activated
Test mode of 3I >→ stage F035E012 2 1206 2 1 Read/Unsolicited 0 – off
off/on
Function block INRUSH3

START signal from Inrush3 stage F034O001 1 5300 1,2 - Read 0 – reset
1 – activated
START signal from Inrush3 stage F034E000 2 5300 2 1 Read/Unsolicited 0 – reset
change F034E001 response 1 – activated
Test mode of Inrush3 stage off/on F034E002 2 5301 2 1 Read/Unsolicited 0 – reset
Function block NEF1HIGH

START signal from Io >> stage F039O001 1 1050 1,2 - Read 0 – reset
1 - activated
TRIP signal from Io >> stage F039O002 1 1051 1,2 - Read 0 – reset
1 – activated
CBFP signal from Io >> stage F039O003 1 1052 1,2 - Read 0 – reset
1 – activated
BS1 signal of Io >> stage F039I002 1 1053 1,2 - Read 0 – reset
1 – activated
BS2 signal of Io >> stage F039I003 1 1054 1,2 - Read 0 – reset
1 – activated
START signal from Io >> stage F039E000 2 1050 2 1 Read/Unsolicited 0 – reset
Reset/activated F039E001 response 1 - activated
ABB Automation 75
for REC 523

TRIP signal from Io >> stage F039E002 2 1051 2 1 Read/Unsolicited 0 – reset
Reset/activated F039E003 response 1 – activated
CBFP signal from Io >> stage F039E004 2 1052 2 1 Read/Unsolicited 0 – reset
BS1 signal of Io >> stage reset/ F039E006 2 1053 2 1 Read/Unsolicited 0 – reset
BS2 signal of Io >> stage reset/ F039E008 2 1054 2 1 Read/Unsolicited 0 – reset
Test mode of Io >> stage off/on F039E010 2 1055 2 1 Read/Unsolicited 0 – off
Function block NEF1LOW

START signal from Io > stage F038O001 1 1000 1,2 - Read 0 – reset
1 - activated
TRIP signal from Io > stage F038O002 1 1001 1,2 - Read 0 – reset
1 – activated
CBFP signal from Io > stage F038O003 1 1002 1,2 - Read 0 – reset
1 – activated
BS1 signal of Io > stage F038I002 1 1003 1,2 - Read 0 – reset
1 – activated
BS2 signal of Io > stage F038I003 1 1004 1,2 - Read 0 – reset
1 – activated
START signal from Io > stage F038E000 2 1000 2 1 Read/Unsolicited 0 – reset
Reset/activated F038E001 response 1 - activated
TRIP signal from Io > stage F038E002 2 1001 2 1 Read/Unsolicited 0 – reset
CBFP signal from Io > stage F038E004 2 1002 2 1 Read/Unsolicited 0 – reset
BS1 signal of Io > stage reset/ F038E006 2 1003 2 1 Read/Unsolicited 0 – reset
BS2 signal of Io > stage reset/ F038E008 2 1004 2 1 Read/Unsolicited 0 – reset
Test mode of Io > stage off/on F038E010 2 1014 2 1 Read/Unsolicited 0 – off
Function block NOC3HIGH

START signal from 3I >> stage F032O002 1 950 1,2 - Read 0 – reset
1 - activated
TRIP signal from 3I >> stage F032O003 1 951 1,2 - Read 0 – reset
1 – activated
CBFP signal from 3I >> stage F032O004 1 952 1,2 - Read 0 – reset
1 – activated
BSOUT signal from 3I >> stage F032O001 1 953 1,2 - Read 0 – reset
1 – activated
BS1 signal of 3I >> stage F032I004 1 954 1,2 - Read 0 – reset
1 – activated
BS2 signal of 3I >> stage F032I005 1 955 1,2 - Read 0 – reset
1 – activated
START signal from 3I >> stage F032E000 2 950 2 1 Read/Unsolicited 0 – reset
TRIP signal from 3I >> stage F032E002 2 951 2 1 Read/Unsolicited 0 – reset
76 ABB Automation
for REC 523

CBFP signal from 3I >> stage F032E004 2 952 2 1 Read/Unsolicited 0 – reset
BSOUT signal from 3I >> stage F032E006 2 953 2 1 Read/Unsolicited 0 – reset
BS1 signal of 3I >> stage reset/ F032E008 2 954 2 1 Read/Unsolicited 0 – reset
BS2 signal of 3I >> stage reset/ F032E010 2 955 2 1 Read/Unsolicited 0 – reset
Test mode of 3I >> stage off/on F032E012 2 956 2 1 Read/Unsolicited 0 – off
Function block NOC3LOW

START signal from 3I > stage F031O001 1 900 1,2 - Read 0 – reset
1 - activated
TRIP signal from 3I > stage F031O002 1 901 1,2 - Read 0 – reset
1 – activated
CBFP signal from 3I > stage F031O003 1 902 1,2 - Read 0 – reset
1 – activated
BS1 signal of 3I > stage F031I004 1 903 1,2 - Read 0 – reset
1 – activated
BS2 signal of 3I > stage F031I005 1 904 1,2 - Read 0 – reset
1 – activated
START signal from 3I > stage F031E000 2 900 2 1 Read/Unsolicited 0 – reset
reset/activated F031E001 response 1 - activated
TRIP signal from 3I > stage F031E002 2 901 2 1 Read/Unsolicited 0 – reset
CBFP signal from 3I > stage F031E004 2 902 2 1 Read/Unsolicited 0 – reset
BS1 signal of 3I > stage reset/ F031E006 2 903 2 1 Read/Unsolicited 0 – reset
BS2 signal of 3I > stage reset/ F031E008 2 904 2 1 Read/Unsolicited 0 – reset
Test mode of 3I > stage off/on F031E010 2 917 2 1 Read/Unsolicited 0 – off
Function block UV3HIGH

START signal from 3U<< stage F065O001 1 5200 1,2 - Read 0 – reset
1 – activated
TRIP signal from 3U<< stage F065O002 1 5201 1,2 - Read 0 – reset
1 – activated
BS1 signal of 3U<< stage F065I004 1 5202 1,2 - Read 0 – reset
1 – activated
BS2 signal of 3U<< stage F065I005 1 5203 1,2 - Read 0 – reset
1 – activated
START signal from 3U<< stage F065E000 2 5200 2 1 Read/Unsolicited 0 – reset
TRIP signal from 3U<< stage F065E002 2 5201 2 1 Read/Unsolicited 0 – reset
BS1 signal of 3U<< stage change F065E004 2 5202 2 1 Read/Unsolicited 0 – reset
BS2 signal of 3U<< stage change F065E006 2 5203 2 1 Read/Unsolicited 0 – reset
ABB Automation 77
for REC 523

Test mode of 3U<< stage off/on F065E008 2 5204 2 1 Read/Unsolicited 0 – reset
Function block UV3LOW

START signal from 3U< stage F064O001 1 5250 1,2 - Read 0 – reset
1 – activated
TRIP signal from 3U< stage F064O002 1 5251 1,2 - Read 0 – reset
1 – activated
BS1 signal of 3U< stage F064I004 1 5252 1,2 - Read 0 – reset
1 – activated
BS2 signal of 3U< stage F064I005 1 5253 1,2 - Read 0 – reset
1 – activated
START signal from 3U< stage F064E000 2 5250 2 1 Read/Unsolicited 0 – reset
TRIP signal from 3U< stage F064E002 2 5251 2 1 Read/Unsolicited 0 – reset
BS1 signal of 3U< stage change F064E004 2 5252 2 1 Read/Unsolicited 0 – reset
BS2 signal of 3U< stage change F064E006 2 5253 2 1 Read/Unsolicited 0 – reset
Test mode of 3U< stage off/on F064E008 2 5254 2 1 Read/Unsolicited 0 – reset
Function block CO3DC1

Opening time alarm status F139O005 1 2700 1,2 - Read 0 – normal
1 – alarm
Closing time alarm status F139O006 1 2701 1,2 - Read 0 – normal
1 – alarm
Earthing time alarm status F139O007 1 2702 1,2 - Read 0 – normal
1 – alarm
Freeing time alarm status F139O008 1 2703 1,2 - Read 0 – normal
1 – alarm
Position open/close* F139V001 1 2704 1,2 0 Read 01 – closed
2705 10 – open
00 – middle
11 – faulty
Position earth/free* F139V002 1 2706 1,2 0 Read 01 – earth
2707 10 – free
00 – middle
11 – faulty
Interlock close F139V030 1 2708 1,2 0 Read 0 – disabled
1 – enabled
Interlock open F139V031 1 2709 1,2 0 Read 0 – disabled
1 – enabled
Interlock earth F139V032 1 2710 1,2 0 Read 0 – disabled
1 – enabled
Interlock free F139V033 1 2711 1,2 0 Read 0 – disabled
1 – enabled
Invalid state F139V034 1 2712 1,2 - Read 0 – inactive
1 – active
Command blocking status F139V035 1 2713 1,2 0 Read 0 – deactivated
1 – activated
78 ABB Automation
for REC 523

Position open/close change to: F139E000 2 2704 2 1 Read/Unsolicited 01 – closed
open/close/faulty/middle* F139E001 2705 response 10 – open
F139E002 00 – middle
F139E003 11 – faulty
Open command enabled/disabled F139E004 2 2709 2 1 Read/Unsolicited 0 – disabled
F139E005 response 1 – enabled
Close command enabled/disabled F139E006 2 2708 2 1 Read/Unsolicited 0 – disabled
Invalid state inactive/active F139E008 2 2712 2 1 Read/Unsolicited 0 – inactive
F139E009 response 1 – active
Command sequence completed/ F139E010 2 2714 2 1 Read/Unsolicited 0 – completed
started F139E011 response 1 – started
Open output deactivated/ F139E012 2 2715 2 1 Read/Unsolicited 0 – deactivated
Close output deactivated/ F139E014 2 2716 2 1 Read/Unsolicited 0 – deactivated
Opening time normal/alarm F139E016 2 2700 2 1 Read/Unsolicited 0 – normal
F139E017 response 1 – alarm
Closing time normal/alarm F139E018 2 2701 2 1 Read/Unsolicited 0 – normal
Command status NACK/ACK F139E024 2 2717 2 1 Read/Unsolicited 0 – NACK
F139E025 response 1 – ACK
Command blocking inactive/active F139E026 2 2713 2 1 Read/Unsolicited 0 – deactivated
Command unsuccessful F139E028 2 2718 2 1 Read/Unsolicited 1 – failed
response
Earth output deactivated/activated F139E030 2 2719 2 1 Read/Unsolicited 0 – deactivated
Free output deactivated/activated F139E032 2 2720 2 1 Read/Unsolicited 0 – deactivated
Earthing time normal/alarm F139E034 2 2702 2 1 Read/Unsolicited 0 – normal
Freeing time normal/alarm F139E036 2 2703 2 1 Read/Unsolicited 0 – normal
Position earth/free change to: F139E038 2 2706 2 1 Read/Unsolicited 01 – earth
open/close/faulty/middle* F139E039 2707 response 10 – free
Earth command enabled/disabled F139E042 2 2710 2 1 Read/Unsolicited 0 – disabled
Free command enabled/disabled F139E044 2 2711 2 1 Read/Unsolicited 0 – disabled
Open/close relay** F139V001 10/12 2700 1,2/1 0/- Read/Select/ 0 – closed
F139V004 Operate/Direct 1 – open
F139V005 operate close – close
F139V006 trip – open
F139V007
F139V010
F139V011
Earth/free relay** F139V002 10/12 2701 1,2/1 0/- Read/Select/ 0 – earth
F139V020 Operate/Direct 1 – free
F139V023
F139V010
F139V011
Alarm ACK*** F139V099 10/12 2702 1,2/1 -/- Read/Select/ 1 or trip – ACK
Operate/Direct
operate
ABB Automation 79
for REC 523
* Because this item provides double-point information, two concecutive DNP points are used to
represent its value. Values in last column of the table should be read as follows: 01 means point with
higher address has value 0 and point with lower address has value 1.
** Binary output status is read only, and provides only one point information about state of the
disconnector switch: 1-open (freed) or faulty, 0-closed (earthed) or middle. Full information about the
state is available from binary inputs 2704 and 2705 (O/C position) or from binary inputs 2706 and
2707 (F/E position).
*** Because this point is write only, a dummy 0 value will be reported while reading.
Function block CO3DC2

1 – alarm
1 – alarm
Earthing time alarm status F140O007 1 2802 1,2 - Read 0 – normal
1 – alarm
Freeing time alarm status F140O008 1 2803 1,2 - Read 0 – normal
1 – alarm
Position open/close* F140V001 1 2804 2 0 Read 01 – closed
2805 10 – open
00 – middle
11 – faulty
Position earth/free* F140V002 1 2806 2 0 Read 01 – earth
2807 10 – free
00 – middle
11 – faulty
Interlock close F140V030 1 2808 1,2 0 Read 0 – disabled
1 – enabled
Interlock open F140V031 1 2809 1,2 0 Read 0 – disabled
1 – enabled
Interlock earth F140V032 1 2810 1,2 0 Read 0 – disabled
1 – enabled
Interlock free F140V033 1 2811 1,2 0 Read 0 – disabled
1 – enabled
Invalid state F140V034 1 2812 1,2 - Read 0 – inactive
1 – active
Command blocking status F140V035 1 2813 1,2 0 Read 0 – deactivated
1 – activated
Position open/close change to: F140E000 2 2804 2 1 Read/Unsolicited 01 – closed
free/earth/faulty/middle* F140E001 2805 response 10 – open
Invalid state inactive/active F140E008 2 2812 2 1 Read/Unsolicited 0 – inactive
Open output deactivated/ F140E012 2 2815 2 1 Read/Unsolicited 0 – deactivated
Close output deactivated/ F140E014 2 2816 2 1 Read/Unsolicited 0 – deactivated
80 ABB Automation
for REC 523

Command blocking inactive/active F140E026 2 2813 2 1 Read/Unsolicited 0 – deactivated
Command unsuccessful F140E028 2 2818 2 1 Read/Unsolicited 1 – failed
response
Earth output deactivated/activated F140E030 2 2819 2 1 Read/Unsolicited 0 – deactivated
Free output deactivated/activated F140E032 2 2820 2 1 Read/Unsolicited 0 – deactivated
Earthing time normal/alarm F140E034 2 2802 2 1 Read/Unsolicited 0 – normal
Freeing time normal/alarm F140E036 2 2803 2 1 Read/Unsolicited 0 – normal
Position earth/free change to: F140E038 2 2806 2 1 Read/Unsolicited 01 – earth
Free/earth/faulty/middle* F140E039 2807 response 10 – free
Earth command enabled/disabled F140E042 2 2810 2 1 Read/Unsolicited 0 – disabled
Free command enabled/disabled F140E044 2 2811 2 1 Read/Unsolicited 0 – disabled
Open/close relay** F140V001 10/12 2800 2/1 0/- Read/Select/ 0 – closed
F140V007
F140V010
F140V011
Earth/free relay** F140V002 10/12 2801 1,2/1 0/- Read/Select/ 0 – earth
F140V020 Operate/Direct 1 – free
F140V023
F140V010
F140V011
Operate/Direct
operate
* Because this item provides double-point information, two concecutive DNP points are used to
disconnector switch: 1-open (freed) or faulty, 0-closed (earthed) or middle. Full information about the
state is available from binary inputs 2804 and 2805 (O/C position) or from binary inputs 2806 and
2807 (F/E position).
*** Because this point is write only, a dummy 0 value will be reported while reading.
Function block COCB1

Position* F120V001 1 2900 1,2 0 Read 01 – closed
2901 10 – open
00 – middle
11 – faulty
1 – alarm
1 – alarm
ABB Automation 81
for REC 523

Inactive time alarm status F120O005 1 2904 1,2 - Read 0 – normal
1 – alarm
Cycle count alarm status F120O006 1 2905 1,2 - Read 0 – normal
1 – alarm
Open command F120V031 1 2906 1,2 0 Read 0 – disabled
1 – enabled
Close command F120V030 1 2907 1,2 0 Read 0 – disabled
1 – enabled
Invalid state F120V034 1 2908 1,2 - Read 0 – off
1 – on
Control blocking F120V035 1 2909 1,2 - Read 0 – deactivated
1 – activated
Position change to: F120E000 2 2900 2 1 Read/Unsolicited 01 – closed
Invalid state on/off F120E008 2 2908 2 1 Read/Unsolicited 0 – off
Open output activated/ F120E012 2 2911 2 1 Read/Unsolicited 0 – inactive
deactivated F120E013 response 1 – active
Close output activated/ F120E014 2 2912 2 1 Read/Unsolicited 0 – inactive
Inactive time normal/alarm F120E020 2 2904 2 1 Read/Unsolicited 0 – normal
Cycle count normal/alarm F120E022 2 2905 2 1 Read/Unsolicited 0 – normal
Control blocking inactive/active F120E026 2 2909 2 1 Read/Unsolicited 0 – deactivated
Command failed F120E028 2 2913 2 1 Read/Unsolicited 1 – failed
response
Open/close relay** F120V001 10/12 2900 2/1 0/- Read/Select/ 0 – close
F120V007
F120V010
F120V011
Operate/Direct
operate
* Because this data item provides double-point information two consecutive DNP points are used to
** Binary output status is read only, and provides only one point information about state of the breaker:
1-open or faulty, 0-closed or middle. Full information about the state is available from binary inputs
2900 and 2901.
*** Because this point is write only, a dummy 0 value will be reported while reading
82 ABB Automation
for REC 523
Function block COCB2

Position* F121V001 1 3000 2 0 Read 01 – closed
3001 10 – open
00 – middle
11 – faulty
1 – alarm
1 – alarm
Inactive time alarm status F121O005 1 3004 1,2 - Read 0 – normal
1 – alarm
Cycle count alarm status F121O006 1 3005 1,2 - Read 0 – normal
1 – alarm
Open command F121V031 1 3006 1,2 0 Read 0 – disabled
1 – enabled
Close command F121V030 1 3007 1,2 0 Read 0 – disabled
1 – enabled
1 – on
1 – activated
Inactive time normal/alarm F121E020 2 3004 2 1 Read/Unsolicited 0 – normal
Cycle count normal/alarm F121E022 2 3005 2 1 Read/Unsolicited 0 – normal
response
Open/close relay** F121V001 10/12 3000 2/1 0/- Read/Select/ 0 – close
F121V007
F121V010
F121V011
ABB Automation 83
for REC 523

Operate/Direct
operate
** Binary output status is read only, and provides only one point information about state of the breaker:
1-open or faulty, 0-closed or middle. Full information about the state is available from binary inputs
3000 and 3001.
Function block CODC1

1 – alarm
1 – alarm
2203 10 – open
00 – middle
11 – faulty
Open command F122V030 1 2204 1,2 0 Read 0 – enabled
1 – disabled
Close command F122V031 1 2205 1,2 0 Read 0 – enabled
1 – disabled
1 – on
Control blocking F122V035 1 2207 1,2 0 Read 0 – deactivated
1 – activated
Position change to: F122E000 2 2202 2 1 Read/ Unsolicited 01 – closed
open/close/faulty/ middle* F122E001 2203 response 10 – open
Open command enabled/disabled F122E004 2 2204 2 1 Read/ Unsolicited 0 – disabled
Close command enabled/disabled F122E006 2 2205 2 1 Read/ Unsolicited 0 – disabled
Invalid state on/off F122E008 2 2206 2 1 Read/ Unsolicited 0 – off
Command sequence completed/ F122E010 2 2208 2 1 Read/ Unsolicited 0 – completed
Open output activated/ F122E012 2 2209 2 1 Read/ Unsolicited 0 – inactive
Close output activated/ F122E014 2 2210 2 1 Read/ Unsolicited 0 – inactive
Opening time normal/alarm F122E016 2 2200 2 1 Read/ Unsolicited 0 – normal
Closing time normal/alarm F122E018 2 2201 2 1 Read/ Unsolicited 0 – normal
Control blocking inactive/active F122E026 2 2207 2 1 Read/ Unsolicited 0 – deactivated
Command failed F122E028 2 2211 2 1 Read/ Unsolicited 1 – failed
response
Command NACK/ACK F122E024 2 2212 2 1 Read/Unsolicited 0 – NACK
F122E025 response 1 - ACK
84 ABB Automation
for REC 523

Open/close relay** F122V001 10/12 2200 1,2/1 0/- Read/Select/ 0 – close
F122V004 Operate/ Direct 1 – open
F122V007
F122V010
F122V011
Alarm ACK*** F122V099 10/12 2201 1,2/1 -/- Read/Select/ 1 or trip - ACK
Operate/ Direct
operate
disconnector: 1-open or faulty, 0-closed or middle. Full information about the state is available from
binary inputs 2202 and 2203.

1 – alarm
1 – alarm
2303 10 – open
00 – middle
11 – faulty
1 – disabled
1 – disabled
1 – on
1 – activated
Position change to: F123E000 2 2302 2 1 Read/ Unsolicited 01 – closed
open/close/faulty/ middle* F123E001 2303 response 10 – open
Open command enabled/disabled F123E004 2 2304 2 1 Read/ Unsolicited 0 – enabled
F123E005 response 1 – disabled
Close command enabled/disabled F123E006 2 2305 2 1 Read/ Unsolicited 0 – enabled
Invalid state on/off F123E008 2 2306 2 1 Read/ Unsolicited 0 – off
Command sequence completed/ F123E010 2 2308 2 1 Read/ Unsolicited 0 – completed
Open output activated/ F123E012 2 2309 2 1 Read/ Unsolicited 0 – inactive
Close output activated/ F123E014 2 2310 2 1 Read/ Unsolicited 0 – inactive
Opening time normal/alarm F123E016 2 2300 2 1 Read/ Unsolicited 0 – normal
Closing time normal/alarm F123E018 2 2301 2 1 Read/ Unsolicited 0 – normal
Control blocking inactive/active F123E026 2 2307 2 1 Read/ Unsolicited 0 – deactivated
ABB Automation 85
for REC 523

Command failed F123E028 2 2311 2 1 Read/ Unsolicited 1 – failed
response
Open/close relay** F123V001 10/12 2300 2/1 0/- Read/ Select/ 0 – close
F123V004 Operate/ Direct 1 – open
F123V007
F123V010
F123V011
Alarm ACK*** F123V099 10/12 2301 1,2/1 -/- Read/ Select/ 1 or trip - ACK
Operate/ Direct
operate

1 – alarm
1 – alarm
2403 10 – open
00 – middle
11 – faulty
1 – disabled
1 – disabled
1 – on
1 – activated
Open command enabled/disabled F124E004 2 2404 2 1 Read/Unsolicited 0 – enabled
Close command enabled/disabled F124E006 2 2405 2 1 Read/Unsolicited 0 – enabled
86 ABB Automation
for REC 523

response
F124V007
F124V010
F124V011
Operate/Direct
operate

1 – alarm
1 – alarm
2503 10 – open
00 – middle
11 – faulty
1 – disabled
1 – disabled
1 – on
1 – activated
ABB Automation 87
for REC 523

response
F125V007
F125V010
F125V011
Operate/Direct
operate

1 – alarm
1 – alarm
2603 10 – open
00 – middle
11 – faulty
1 – disabled
1 – disabled
1 – on
1 – activated
88 ABB Automation
for REC 523

response
F126V007
F126V010
F126V011
Operate/Direct
operate
Function block COIND1

1401 10 – open
00 – middle
11 – faulty
1 – on
Open/close/faulty/middle* F127E001 1401 response 10 – open
ABB Automation 89
for REC 523

1501 10 – open
00 – middle
11 – faulty
1 – on

1601 10 – open
00 – middle
11 – faulty
1 – on

1701 10 – open
00 – middle
11 – faulty
1 – on
90 ABB Automation
for REC 523

1801 10 – open
00 – middle
11 – faulty
1 – on

1901 10 – open
00 – middle
11 – faulty
1 – on

Position F133V001 1 2000 1,2 0 Read 01 – closed
2001 10 – open
00 – middle
11 – faulty
1 – on
ABB Automation 91
for REC 523

2101 10 – open
00 – middle
11 – faulty
1 – on
Function block COLOCAT

Logic position setting F142V001 1 4600 1,2 - Read 0 – inactive
1 – active
Logic position setting inactive/ F142E000 2 4600 2 1 Read/Unsolicited 0 – inactive
active F142E001 response 1 – active
Function block COPFC

P3 (kW) F143I001 30 6000 3 - Read -999999...999999
Q3 (kvar) F143I002 30 6001 3 - Read -999999...999999
Power factor PDF F143I004 30 6002 3 - Read 0.00...1.00
Connected banks F143I003 30 6003 3 - Read 0...65535
Block F143I005 1 6000 1,2 - Read 0 – Not active
1 – Active
Day/night phi switch F143I006 1 6001 1,2 - Read 0 - Day target PF
1 - Night target PF
Disconnect F143I007 1 6002 1,2 - Read 0 – Not active
1 – Active
Reset F143I008 1 6003 1,2 - Read 0 – Not active
1 – Active
REQ_UP F143O001 1 6004 1,2 - Read 0 – Not active
1 – Active
REQ_DOWN F143O002 1 6005 1,2 - Read 0 – Not active
1 – Active
Control opration status F143O003 1 6006 1,2 - Read 0 – Not active
1 – Active
Q not within limits indication F143O004 1 6007 1,2 - Read 0 – Not active
1 – Active
Pumping situation alarm status F143O005 1 6008 1,2 - Read 0 – Not active
1 – Active
Automatic testing mode status F143O006 1 6009 1,2 - Read 0 - Not activated
1 - In progress
Manual commands allowed F143V015 1 6010 1,2 - Read 0 – Disabled
indication 1 – Enabled
Control operation failed reset / F143E000 2 6006 2 1 Read/Unsolicited 0 – Reset
activated F143E001 response 1 – Activated
92 ABB Automation
for REC 523

Q not within limits indication reset F143E002 2 6007 2 1 Read/Unsolicited 0 – Reset
/ activated F143E003 response 1 – Activated
Pumping situation alarm reset / F143E004 2 6008 2 1 Read/Unsolicited 0 – Reset
Not discharged yet reset / F143E006 2 6011 2 1 Read/Unsolicited 0 – Reset
Automatic testing mode reset / F143E008 2 6009 2 1 Read/Unsolicited 0 – Reset
Testing finished OK / failed F143E010 2 6012 2 1 Read/Unsolicited 0 – Reset
F143E011 response 1 – Activated
Overvoltage inhibition reset / F143E012 2 6013 2 1 Read/Unsolicited 0 – Reset
BLOCK signal reset / activated F143E014 2 6000 2 1 Read/Unsolicited 0 – Reset
F143E015 response 1 – Activated
DISCONNECT signal reset / F143E016 2 6002 2 1 Read/Unsolicited 0 – Reset
Number of switching operations F143V011 30 6000 3 - Read 0...65535
per day
Operation mode F143V001 40 / 41 6000 1 - Read/Select/ 0 - Not in use
Operate/ Direct 1 - Automatic mode
operate 2 - Manual mode
3 - Testing mode
Day&night switch F143V006 40 / 41 6001 1 - Read/Select/ 0 - Not in use
Operate/ Direct 1 - Binary input
operate 2 - Internal clock
3 - By setting
Day & night command F143V008 40 / 41 6002 1 - Read/Select/ 0 - Not activated
Operate/ Direct 1 - Day target PF
operate 2 - Night target PF
Function block CMBWEAR1

Alarm state F187O001 1 3500 1,2 0 Read 0 – normal
1 – alarm
Breaker electric wear alarm reset/ F187E000 2 3500 2 1 Read/Unsolicited 0 – normal
activated F187E001 response 1 – alarm
Alarm ACK F187V099 10/12 3500 1,2/1 - Read*/Write/Select/ 1 or trip – ACK
Operate/Direct
operate
Accumulated breaker wear at pole F187V001 40/41 3500 1 - Read/Select/ 0..10000
1 Operate/ Direct
operate
2 Operate/ Direct
operate
3 Operate/ Direct
operate
* Because this point is write only, a dummy 0 value will be reported while reading
Function block CMBWEAR2

Alarm state F188O001 1 3600 1,2 0 Read 0 – normal
1 – alarm
Breaker electric wear alarm reset/ F188E000 2 3600 2 1 Read/Unsolicited 0 – normal
ABB Automation 93
for REC 523

Alarm ACK F188V099 10/12 3600 1,2/1 - Read*/Write/Select/ 1 or trip – ACK
Operate/Direct
operate
1 Operate/ Direct
operate
2 Operate/ Direct
operate
3 Operate/ Direct
operate
Function block CMCU3

Input current circuit alarm F181O001 1 3200 1,2 0 Read 0 – normal
1 – alarm
Input current circuit alarm off/on F181E000 2 3200 2 1 Read/Unsolicited 0 – normal
Function block CMGAS1

Low gas density alarm state F186O001 1 3400 1,2 0 Read 0 – normal
1 – alarm
Gas pressure invalid F186I001 1 3401 1,2 - Read 1 – invalid
0 – valid
Low gas density alarm reset/ F186E000 2 3400 2 1 Read/Unsolicited 0 – normal
Low gas density warning inactive/ F186E002 2 3401 2 1 Read/Unsolicited 0 – normal
active F182E003 response 1 – warning
Alarm ACK* F186V099 10/12 3400 1,2/1 - Read/Write/Select/ 1 or trip – ACK
Operate/Direct
operate
Function block CMGAS3

Alarm state F194O001 1 6300 1,2 0 Read 0 – Inactive
1 – Active
Gas pressure L1 F194I001 1 6301 1,2 - Read 1 – Invalid
0 – Valid
0 – Valid
0 – Valid
Low gas density alarm reset / F194E000 2 6300 2 1 Read/Unsolicited 0 – Reset
Low gas density warning L1 F194E002 2 6301 2 1 Read/Unsolicited 0 – Inactive
inactive / active F194E003 response 1 – Active
94 ABB Automation
for REC 523

Alarm ACK* F194V099 10/12 6300 1,2 / 1 - Read/Write/Select/ 1 or trip – ACK
Operate/Direct
operate
Function block CMSCHED

Scheduled maintenance alarm F189O001 1 3700 1,2 0 Read 0 – normal
state 1 – alarm
Scheduled maintenance alarm F189E000 2 3700 2 1 Read/Unsolicited 0 – normal
reset/activated F189E001 response 1 – alarm
Alarm ACK* F189V099 10/12 3700 1,2/1 - Read/Write/Select/ 1 or trip - ACK
Operate/Direct
operate
Function block CMSPRC1

Spring 1 max. charging alarm F190O002 1 4900 1,2 0 Read 0 – inactive
state 1 – active
Spring 1 min. charging alarm F190O003 1 4901 1,2 0 Read 0 – inactive
state 1 – active
Spring 1 charge status F190I002 1 4902 1,2 - Read 0 – uncharged
1 – charged
Operate/Direct
operate
Spring 1 max. charging alarm F190E002 2 4900 2 1 Read/Unsolicited 0 – reset
inactive/active F190E003 response 1 – activated
Spring 1 min. charging alarm F190E004 2 4901 2 1 Read/Unsolicited 0 – inactive
inactive/active F190E005 response 1 – active
Spring 1 charge status F190E008 2 4902 2 1 Read/Unsolicited 0 – uncharged
uncharged/charged F190E009 response 1 – charged
Spring 1 charging motor active/ F190E000 2 4903 2 1 Read/Unsolicited 0 – inactive
inactive F190E001 response 1 – active
Spring 1 charge command F190E007 2 4904 2 1 Read/Unsolicited 1 – activated
activated response
* Because this point is write only, while reading a dummy 0 value will be reported
Function block CMTIME1

Accumulated time 1 alarm state F184O001 1 4800 1,2 0 Read 0 – reset
1 – activated
Accumulated time 1 F184I001 1 4801 1,2 - Read 0 – inactive
measurement state 1 – active
Operate/Direct
operate
ABB Automation 95
for REC 523

Accumulated time 1 alarm reset/ F184E000 2 4800 2 1 Read/Unsolicited 0 – reset
Accumulated time 1 F184E002 2 4801 2 1 Read/Unsolicited 0 – inactive
measurement inactive/active F184E003 response 1 – active
Function block CMTIME2

Accumulated time 2 alarm state F185O001 1 4850 1,2 0 Read 0 – reset
1 – activated
Accumulated time 2 F185I001 1 4851 1,2 - Read 0 – inactive
measurement state 1 – active
Operate/Direct
operate
Accumulated time 2 alarm reset/ F185E000 2 4850 2 1 Read/Unsolicited 0 – reset
Accumulated time 2 F185E002 2 4851 2 1 Read/Unsolicited 0 – inactive
measurement inactive/active F185E003 response 1 – active
Function block CMTRAV1

Breaker 1 open travel alarm F193O001 1 5500 1,2 0 Read 0 – inactive
1 – active
Breaker 1 close travel alarm F193O002 1 5501 1,2 0 Read 0 – inactive
1 – active
Breaker 1 open travel alarm F193E000 2 5500 2 1 Read/Unsolicited 0 – inactive
Breaker 1 close travel alarm F193E002 2 5501 2 1 Read/Unsolicited 0 – inactive
Alarm ACK* F193V099 10/12 5500 1,2/1 - Read/Write/Select/ 1 or trip - ACK
Operate/Direct
operate
Function block CMVO3

Input voltage circuit alarm F182O001 1 3300 1,2 0 Read 0 – normal
1 – alarm
Input voltage circuit alarm off/on F182E000 2 3300 2 1 Read/Unsolicited 0 – normal
Function block PQCU3H

Status of output HAR_HIGH F512O001 1 6100 1,2 0 Read 0 - Not active
1 - Active
Status of output CUM_HIGH F512O002 1 6101 1,2 0 Read 0 - Not active
1 - Active
Current harmonic limit reset / F512E000 2 6100 2 1 Read, Unsolicited 0 – reset
exceeded F512E001 response 1 – exceeded
96 ABB Automation
for REC 523

Current cum. limit F512E002 2 6101 2 1 Read, Unsolicited 1 – exceeded
response
Observation period near end F512E003 2 6102 2 1 Read, Unsolicited 1 – near end
response
Observation period ended F512E004 2 6103 2 1 Read, Unsolicited 1 – ended
response
Reset registers* F512V025 10 / 12 6100 1,2 / 1 -/- Read, Write/Select, 1 or trip – reset
Operate, Direct
operate
THD 3s average value F512I002 30 6100 3 - Read 0.0...1000.0
Fundamental component 3s F512I003 30 6101 3 - Read 0.0...1000.0
average value
2nd harmonic 3s average value F512I004 30 6102 3 - Read 0.0...1000.0
3rd harmonic 3s average value F512I005 30 6103 3 - Read 0.0...1000.0

th
4 harmonic 3s average value F512I006 30 6104 3 - Read 0.0...1000.0
th
th
7th harmonic 3s average value F512I009 30 6107 3 - Read 0.0...1000.0

th

th

th
THD short time sliding average F512I018 30 6114 3 - Read 0.0...1000.0
value
2nd harmonic short time sliding F512I019 30 6115 3 - Read 0.0...1000.0
average value
3rd harmonic short time sliding F512I020 30 6116 3 - Read 0.0...1000.0
average value
4th harmonic short time sliding F512I021 30 6117 3 - Read 0.0...1000.0
average value
average value
average value
average value
average value
average value
average value
average value
average value
average value
Max THD at last obs. period F512V206 30 6127 3 - Read 0.0...1000.0
Max THD at active obs. period F512V306 30 6128 3 - Read 0.0...1000.0
ABB Automation 97
for REC 523

THD F512V404 30 6129 3 - Read 0.0...1000.0
Function block PQVO3H

Status of output HAR_HIGH F513O001 1 6200 1,2 0 Read 0 - Not active
1 - Active
Status of output CUM_HIGH F513O002 1 6201 1,2 0 Read 0 - Not active
1 - Active
Harmonic limit reset / exceeded F513E000 2 6200 2 1 Read, Unsolicited 0 – reset
F513E001 response 1 – exceeded
Cumulative limit exceeded F513E002 2 6201 2 1 Read, Unsolicited 1 – exceeded
response
Observation period near end F513E003 2 6202 2 1 Read, Unsolicited 1 – near end
response
Observation period ended F513E004 2 6203 2 1 Read, Unsolicited 1 – ended
response
Reset registers* F513V024 10 / 12 6200 1,2 / 1 -/- Read, Write / Select, 1 or trip – reset
Operate, Direct
operate
THD 3s average value F513I002 30 6200 3 - Read 0.0...120.0
Fundamental component 3s F513I003 30 6201 3 - Read 0.0...120.0
average value
2nd harmonic 3s average value F513I004 30 6202 3 - Read 0.0...120.0
3 rd
harmonic 3s average value F513I005 30 6203 3 - Read 0.0...120.0
th

th

th
th
THD short time sliding average F513I018 30 6214 3 - Read 0.0...120.0
value
2nd harmonic short time sliding F513I019 30 6215 3 - Read 0.0...120.0
average value
3rd harmonic short time sliding F513I020 30 6216 3 - Read 0.0...120.0
average value
average value
average value
average value
average value
average value
98 ABB Automation
for REC 523

9thharmonic short time sliding F513I026 30 6222 3 - Read 0.0...120.0
average value
average value
average value
average value
average value
Max THD at last obs. period F513V206 30 6227 3 - Read 0.0...120.0
Max THD at active obs. period F513V306 30 6228 3 - Read 0.0...120.0
THD F513V404 30 6229 3 - Read 0.0...120.0
Function block BIO

Binary input 1 state F013I001 1 4500 1,2 - Read 0 – reset
1 - activated
1 – activated
1 – activated
1 – activated
1 – activated
1 – activated
1 – activated
1 – activated
1 – activated
1 – activated
1 – activated
1 – activated
Binary output 1 state F013O001 1 4512 1,2 - Read 0 – reset
1 – activated
1 – activated
1 – activated
1 – activated
1 – activated
1 – activated
Binary input 1 oscillate F013I021 1 4518 1,2 - Read 0 – stop
1 – start
ABB Automation 99
for REC 523

1 – start
1 – start
1 – start
1 – start
1 – start
1 – start
1 – start
1 – start
1 – start
1 – start
1 – start
Binary input 1 reset/activated F013E000 2 4500 2 1 Read/Unsolicited 0 – reset
Binary output 1 reset/activated F013E024 2 4512 2 1 Read/Unsolicited 0 – reset
100 ABB Automation

for REC 523

Binary input 1 oscillate stop/start F013E036 2 4518 2 1 Read/Unsolicited 0 – stop
F013E037 response 1 – start
CH000, CH001 and CH002

Analogue configuration error F000E048 2 3801 2 1 Read/Unsolicited 1 – error
response
Module startup F000E050 2 3802 2 1 Read/Unsolicited 1- startup
response
Event buffer overflow F000E051 2 3803 2 1 Read/Unsolicited 1 – overflow
response
IRF error reset/activated F000E056 2 3800 2 1 Read/Unsolicited 0 – reset
Watchdog error F000E059 2 3804 2 1 Read/Unsolicited 1 – error
response
Store F000V151 40/41 3800 1 - Read/Select/ 0 – store completed
Operate/ Direct 1 – store in progress
operate 2 – error
160 – fast store in
progress
Reset indication F001V011 10/12 3900 1,2/1 - Read*/Write/Select/ 1 or trip – reset
Operate/Direct
operate
Reset outputs F001V012 10/12 3901 1,2/1 - Read*/Write/Select/ 1 or trip – reset
Operate/Direct
operate
Reset registers F001V013 10/12 3902 1,2/1 - Read*/Write/Select/ 1 or trip – reset
Operate/Direct
operate
IRF error state F001V015 1 3800 1,2 0 Read 0 – reset
1 – activated
Recent control position F002V005 1 4700 2 - Read onLine 0 – local
onLine 1 – remote
offLine 0 – disable
ABB Automation 101

for REC 523

Interlocking bypass mode F002V004 1 4701 1,2 - Read 0 – inactive
1 – active
Recent control position F002E000 2 4700 2 1 Read/Unsolicited onLine 0 – local
F002E001 response onLine 1 – remote
F002E002 offLine 0 – disable
Interlocking bypass mode F002E004 2 4701 2 1 Read/Unsolicited 0 – inactive
Function block PSC1

Binary output 1 off/on status F017O001 1 4200 1,2 - Read 0 – reset
1 – activated
1 – activated
1 – activated
Binary input 1 off/on status F017I001 1 4203 1,2 - Read 0 – reset
1 – activated
1 – activated
1 – activated
AC status F017I004 1 4206 1,2 - Read 0 – OK
1 – fail
Overheat status F017I005 1 4207 1,2 - Read 0 – OK
1 – overheated
Battery status F017I006 1 4208 1,2 - Read 0 – good
1 – low
Heating status F017I009 1 4209 1,2 - Read 0 – off
1 – on
Binary input 1 stop/start status F017I021 1 4210 1,2 - Read 0 – stop
1 – start
1 – start
1 – start
Battery test status F017I010 1 4213 1,2 - Read 0 – not active
1 – active
AC fail reset/activated F017E006 2 4206 2 1 Read/Unsolicited 0 – reset
Overheat temperature reset/ F017E008 2 4207 2 1 Read/Unsolicited 0 – reset
Binary output 2 reset/activated F017E012 2 4201 2 1 Read/Unsolicited 0 – OK
F017E013 response 1 – fail
Binary output 3 reset/activated F017E014 2 4202 2 1 Read/Unsolicited 0 – OK
F017E015 response 1 – overheated
102 ABB Automation

for REC 523

Binary input 1 stop/start F017E016 2 4210 2 1 Read/Unsolicited 0 – good
F017E017 response 1 – low
Binary input 2 stop/start F017E018 2 4211 2 1 Read/Unsolicited 0 – off
Binary input 3 stop/start F017E020 2 4212 2 1 Read/Unsolicited 0 – stop
Battery voltage good/low F017E022 2 4208 2 1 Read/Unsolicited 0 – stop
Heating status off/on F017E024 2 4209 2 1 Read/Unsolicited 0 – stop
Battery test F001V011 10/12 4200 1,2/1 - Read/Write/Select/ 1 or trip – start test
Operate/Direct
operate
Temperature updated F017I007 30 4200 3 - Read -40..60
-40°C..+60°C
Battery voltage updated F017II008 30 4201 3 - Read 150..300
15.0Vdc..30.0Vdc
Temperature changed F017E026 32 4200 1 2 Read/Unsolicited -40..60
response -40°C..+60°C
Battery voltage changed F017E027 32 4201 1 2 Read/Unsolicited 180..330
response 18.0Vdc..33.0Vdc
Read/reset recorded minimum F017I011 40/41 4200 1 - Read/Select/ 180..330
battery voltage Operate/ 18.0Vdc..33.0Vdc
Direct operate
SWITCH groups
Actual checksum SWGRP1 F030S001 30 7100 3 - Read 0...255
Group 1 checksum SWGRP1 F030S041 40/41 7100 1 - Read/Select, 0...255
Operate, Direct
operate
Operate, Direct
operate
ABB Automation 103

for REC 523

Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
104 ABB Automation

for REC 523

Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Group selection for SWGRP1 F030V001 40/41 7140 1 - Read/Select, 0 = checksum1
Operate, Direct 1 = checksum2
operate 2 = group input
ABB Automation 105

for REC 523

106 ABB Automation

for REC 523
REC-CH231 (LON events)

LON problem F231E000 2 4300 2 1 Read/Unsolicited 1 – LON problem
response
RECCH025 and RECCH026 (LON virtual inputs and outputs)

COMM IN1 F025I001 30/32 7000 3/1 -/2 Read/Read, 0...65535
Unsolicited response
ABB Automation 107

for REC 523

COMM IN33 F025I017 1/2 7032 1,2/1 -/1 Read/Read, 0...1
108 ABB Automation

for REC 523

COMM OUT1 F025O001 40/41 7000 1 - Read/Select, 0...65535
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
ABB Automation 109

for REC 523

Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
COMM OUT33 F025O017 10/12 7032 1,2/1 - Read, Write/Select, 0...1 / Close...Trip
Operate, Direct
operate
110 ABB Automation

for REC 523

Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
ABB Automation 111

for REC 523

Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Operate, Direct
operate
Link handler
Remote protocol CTS usage F500V217 10/12 4000 1,2/1 - Read/Write/Select/ 0 – not used
Operate/Direct 1 – in use
operate
Remote protocol RTS usage F500V218 10/12 4001 1,2/1 - Read/Write/Select/ 0 – not used
Operate/Direct 1 – in use
operate
Remote protocol connection F500V220 10/12 4002 1,2/1 - Read/Write/Select/ 0 – fixed line
mode Operate/Direct 1 – dial up
operate
Remote protocol baud rate F500V211 40/41 4000 1 - Read/Write/Select/ 300/600/1200/4800/9600/
Operate/Direct 19200/38400 bps
operate
Remote protocol stop bits F500V212 40/41 4001 1 - Read/Write/Select/ 0...2
Operate/Direct
operate
Remote protocol CTS delay F500V213 40/41 4002 1 - Read/Write/Select/ 0...10000
Operate/Direct 0ms...10000ms
operate
Remote protocol RTS delay F500V214 40/41 4003 1 - Read/Write/Select/ 0...10000
Operate/Direct 0ms...10000ms
operate
112 ABB Automation

for REC 523

Remote protocol next character F500V215 40/41 4004 1 - Read/Write/Select/ 0...10000
timeout Operate/Direct 0 – not in use
operate 1ms...10000ms
Remote protocol end of frame F500V216 40/41 4005 1 - Read/Write/Select/ 1...10000
timeout Operate/Direct 1ms...10000ms
operate
Remote protocol parity F500V230 40/41 4006 1 - Read/Select, 0...2
Operate, Direct 0 – no parity
operate 1 – odd parity
2 – even parity
Remote protocol data bits F500V231 40/41 4007 1 - Read/Select, 5...8
Operate, Direct
operate
Remote protocol modem F500V221 150 4000 1 - Read, Write 75 characters
initialization string
Remote protocol modem primary F500V222 150 4001 1 - Read, Write 20 characters
dialing string
Remote protocol modem hang up F500V223 150 4002 1 - Read, Write 20 characters
string
Remote protocol modem 1st F500V224 150 4003 1 - Read, Write 20 characters
spare dialing string
Remote protocol modem 2nd F500V225 150 4004 1 - Read, Write 20 characters
Remote protocol modem 3rd F500V226 150 4005 1 - Read, Write 20 characters
Remote protocol modem 4th F500V227 150 4006 1 - Read, Write 20 characters
Remote protocol modem F500V228 150 4007 1 - Read, Write 20 characters
emergency dialing string
PIN code string F500V229 150 4008 1 - Read, Write 40 characters
DNP protocol
Stay silent SILENTFL 10/12 4100 1, 2 / 1 - Read, Write/ Select, 0 or close – normal
Operate, Direct operation*
operate 1 or trip – stay silent
Station address F503V001 40/41 4100 1 - Read, Write/ Select, 0...65534
Operate, Direct
operate
Designated master address F503V002 40/41 4101 1 - Read, Write/ Select, 0...65534
Operate, Direct
operate
Data link layer response timeout F503V003 40/41 4102 1 - Read, Write/ Select, 0...65535
Operate, Direct 0ms...65535ms
operate
Data link layer retry count F503V004 40/41 4103 1 - Read, Write/ Select, 0...65535
Operate, Direct
operate
Data link layer transmitter timeout F503V005 40/41 4104 1 - Read, Write/ Select, 0...65535
Operate, Direct 0ms...65535ms
operate
Application layer response F503V006 40/41 4105 1 - Read, Write/ Select, 0...65535
timeout Operate, Direct 0ms...65535ms
operate
Application layer retry count F503V007 40/41 4106 1 - Read, Write/ Select, 0..65535
Operate, Direct
operate
ABB Automation 113

for REC 523

DNP confirmation type selector F503V009 40/41 4108 1 - Read, Write/ Select, 0..5
Operate, Direct 0 – no data link layer ACK,
operate no application layer
confirmation
1 – data link layer ACK, no
application layer
confirmation
2 – no data link layer ACK,
unsolicited responses
confirmation
3 – data link layer ACK,
unsolicited responses
confirmation
4 – no data link layer ACK,
all responses confirmation
5 – data link layer ACK, all
responses confirmation
Channel idle watchdog F503V008 40/41 4107 1 - Read, Write/ Select, 0...65535
Operate, Direct 0s...65535s
operate
Time synchronization
Device time DEVCLK 50 0 1 - Read/Write ms since 1970-01-01
00:00:00.000
Internal indications
All stations message received INTINDIC 80 0 1 - Write 1 – received
Class 1 data available INTINDIC 80 1 1 - Write 1 - available
Class 2 data available INTINDIC 80 2 1 - Write 1 – available
Class 3 data available INTINDIC 80 3 1 - Write 1 – available
Time sync. Required INTINDIC 80 4 1 - Write 1 - required
Outputs in local state INTINDIC 80 5 1 - Write 1 – local state
Device trouble INTINDIC 80 6 1 - Write 1 – device trouble
Device restart INTINDIC 80 7 1 - Write 1 – device restarted
Function not implemented INTINDIC 80 8 1 - Write 1 – function not
implemented
Object unknown INTINDIC 80 9 1 - Write 1 – object unknown
Format error INTINDIC 80 10 1 - Write 1 – format error
Buffer overflow INTINDIC 80 11 1 - Write 1 – buffer overflow
Operation in progress INTINDIC 80 12 1 - Write 1 – operation in progress
Invalid configuration INTINDIC 80 13 1 - Write 1 – invalid configuration
Reserved for future use INTINDIC 80 14 1 - Write 0
Reserved for future use INTINDIC 80 15 1 - Write 0
Internal indications cannot be read directly. The current state of the internal
indications field is returned in every application layer response (function code 129
or 130) as a part of the response header and follows function code field (see chapter
1.5.4.2 “$SSOLFDWLRQUHVSRQVHIRUPDW”). Although every bit of internal indications
can be written it is not recommended to clear other bits than 'HYLFHUHVWDUW, because
important information about the current status of the device can be lost.
114 ABB Automation

for REC 523
Application
Variatio
Description Name Object Point Class Access function Values
n
Application APPLICAT 90 0 1 - Start/Stop application -
Transparent SPA
Transparent SPA message LONSPAIN 151 0 1 - Read/Write SPA message e.g. “>1RF:<CR>”
Note that object 151 is an extension to the protocol and the use of this type can be
limited by the capabilities of the master station.
3.3. Protocol software version
)LJ 6RIWZDUHYHUVLRQ
ABB Automation 115

for REC 523
Name Description of coding scheme

Software build System software version (e.g. 3.00) followed by a letter indicating the
remote protocol included (D – for DNP protocol) and remote protocol
version (e.g. 20 for the initial version 2.0)
Software revision Revision letter (e.g. “C”)
Software version The number of the CPU card delivered with the DNP 3.0 protocol
CPU card number Serial number of the CPU card
3.4. Interface configuration

This section describes the communication parameters required to configure REC
523 to communicate using the DNP 3.00 protocol over a given link.
These parameters can be uploaded, reviewed and modified using the Relay Setting
Tool from the CAP 501/505 package by choosing the Communication library and
the General, Link Handler or DNP pages.
3.4.1. Communication start-up procedure

Before the start-up of the DNP 3.0 based communication with REC 523, the link and
protocol parameters should be verified using the Relay Setting Tool from the CAP
501/505 package. To properly configure the interface of REC 523, it is necessary to
know the setup of the master station and the characteristics of the utilized
communication channel. At the end of the configuration process the tool should
enforce storing of updated parameters in the non-volatile memory, after which the
REC 523 unit must be reset to activate the new parameters. In some cases it may also
be required to modify the application mapping in the POD table using a Protocol
Editing Tool.
3.4.2. Port assignment

There are three communication ports in REC 523: two RS 232 and one RS 485.
DNP 3.0 protocol can be assigned to each one of them (but only one at a time). The
port assignment to the protocol can be done by choosing the Communication library
and the General pages in the Relay Setting Tool. Default values for the REC 523
ports are as follows:
Port X5.1: DNP 3.0
Port X5.2: None
Port X5.3: LON.
In Relay Setting Tool, the parameter “Protocol1” refers to the REC 523 port X5.1,
“Protocol2” to the port X5.2 and “Protocol3” to the port X5.3.
116 ABB Automation

for REC 523
)LJ *HQHUDOSDJHV
Note that the port assignments for protocols are revision dependent. This product
supports only following protocols: DNP 3.0, SPA and LON. Refer to Technical
Reference Manual for revision history.
3.4.3. Link parameters

The link parameters of REC 523 can be accessed by choosing the Communication
library and the Link Handler pages in the Relay Setting Tool.
Group Object
Description Notes
description name
Transmission F500V220 Connection mode 0 - in case of fixed line or
settings 0 – fixed line leased line connection
1 – dial-up (with preconfigured
modems)
1 – in case of dial-up
connection (modem
controlled by REC 523)
F500V211 Communication speed (in bps) The same as configured in
the master station (fixed
Baud rate line) or in the modem
(dial-up).
F500V212 Number of stop bits The same as configured in
the master station (fixed
line) or in the modem
(dial-up).
ABB Automation 117

for REC 523
F500V230 Parity The same as configured in

0 – no parity the master station
1 – odd parity (normally even parity, but
2 – even parity (standard) with some modems no
parity may be used).
F500V231 Number of data bits 8 is a default value for the
DNP protocol
as defined by the protocol
Timeout F500V215 Next character timeout (in ms): Not in use in the DNP
settings maximum allowed time gap between protocol.
(frame received characters of the same
transmission frame; 0 – not in use.
delays)
F500V216 End of frame timeout (in ms): Must be tuned according
minimum idle time following the to the link characteristics,
frame transmission to REC 523 recommended minimum:
longer than the character
transmission time.
Handshaking F500V217 CTS usage In use if required by the
settings 0 – not used DCE (modem in half
(connection to 1 – in use duplex mode) and
DCE) supported by the
connection cable.
F500V218 RTS usage In use if required by the
0 – not used DCE (modem in half
1 – in use duplex mode) and
supported by the
connection cable.
F500V213 CTS delay value (in ms) In REC 523 controlled by
hardware, set to 0.
F500V214 RTS delay value (in ms) In REC 523 controlled by
hardware, set to 0.
Group Object
Description Notes
description name
Modem F500V221 Modem initialization string According to the modem
settings (max. 75 characters) type (refer to the modem
(only to be manual).
used in dial-up
connection
mode)
F500V222 Modem dialing string According to the modem
(max. 20 characters) type (refer to the modem
Note: This parameter will be used manual).
only if REC 523 is permitted to
activate the dial-up connection with
the master station (unsolicited
reporting of events will be allowed).
F500V223 Modem hang-up string According to the modem
Note: This parameter will be used in manual).
case of enforced interface restart or
unknown modem state.
118 ABB Automation

for REC 523
F500V224 1st spare modem dialing string According to the modem

only if REC 523 is permitted to Set to “NOTUSED” if not
activate the dial-up connection with in use.
Add dial str 1

F500V225 2nd spare modem dialing string According to the modem
Add dial str 2

F500V226 3rd spare modem dialing string According to the modem
Add dial str 3

F500V227 4th spare modem dialing string According to the modem
Add dial str 4

F500V228 Emergency dialing string According to the modem
F500V229 PIN code string According to the modem
Note: This parameter is used only manual).
with GSM modems. Set to “NOTUSED” if not
in use.
According to the specification of the protocol, the following transmission

parameters are required (when using fixed line connection):
• 8 data bits
• parity odd, even or none
• 1 or 2 stop bits
ABB Automation 119

for REC 523
• next character timeout - not active

• end of frame timeout 10 ms
• baud rate in the range supported by the REC 523 link handler
)LJ /LQN+DQGOHU
3.4.4. Protocol parameters

The DNP 3.0 protocol parameters can be accessed by choosing the communication
library and the DNP page in the Relay Setting Tool.
For a consistent setup, the protocol parameters can be analysed in two groups:
• address parameters,
• timeout and delay parameters,
120 ABB Automation

for REC 523
Group Object
Description Notes
description name
Address F503V001 Station address The same as configured in the
parameters 0..65534 master station.
Unit Address Address of the REC 523 unit in

the DNP network
F503V002 Master station address The same as configured in the
(destination address for master station.
unsolicited responses)
0..65534 Address of the REC 523 unit in
Master Address the DNP network
Timeout and F503V003 Data link layer primary Must be greater than time needed
delay timeout to process the data link frame in
parameters the master station and transmit
acknowledgment.
This timeout is activated

whenever REC 523 is acting as a
primary station and sending
Link TO LPDU using confirmed service.
Value in milliseconds.
F503V004 Number of retries of the Irrelevant if unconfirmed data link
data link layer when the unit layer service is used, otherwise
is acting as a primary station must be set to value greater than
0.
Number of retries of the data link

Link retrans. No layer when the unit is acting as a
primary station
F503V005 Line idle timeout (used to Can be set to 0 when unsolicited
avoid collision of frames) reporting of events is not used
and the link is not multidrop. For
other cases see next section.
Minimum delay (in milliseconds)

after frame receipt or sending
before a data link layer frame can
be transmitted. This timeout is
activated whenever REC 523 is
sending or receiving data. Before
the end of this timeout, the station
will not send any data link layer
Transmit idle No frames to the link handler. Value
in milliseconds.
F503V006 Application layer Must be greater than time needed
confirmation timeout to transmit the whole application
layer frame, process it in the
master station and transmit
confirmation.
This timeout is activated

whenever REC 523 is acting as a
primary station and sending
APDU with confirmation bit set.
Apl TO Value in milliseconds.
ABB Automation 121

for REC 523
F503V007 Number of retries of the Irrelevant if CON bit is not used,

application layer when CON otherwise must be set to value
bit is set. greater than 0
Number of retries of the

Apl. retrans. No application layer when CON bit is
set.
F503V009 Type of confirmation Depends on quality of the used
supported: link. See next section
0..5
Type of confirmation supported:
0: data link conf:0 application
conf: 0
conf: 0
conf: 1
conf: 1
conf: 2
conf: 2
See table below.
Confirm type
F503V008 Channel idle timeout (in Set acccording to the expected
seconds). master station request send
interval.
In the dial-up environment:

After this time of channel inactivity
connection will be closed by REC
523. Parameter unit is 1s. When
Reconnection TO set to 0 – not in use.
Confirmation setup (explanation to the parameter F503V009):
Type of
Min. Max. Description
confirmation
Data link layer user 0 1 If the value is 1 then confirmation on the data link layer
data confirmation is enabled. This means that User Data With Confirm
and ACK will be used for all user data transmissions to
the host. Otherwise, Unconfirmed User Data frames will
be used.
Application layer 0 2 If the value is 2 then confirmation for all outgoing data
confirmation on the application layer is enabled. This means that
CON bit will be set in the application control byte for all
response headers sent by REC 523. The value 1
enables confirmations only for unsolicited responses.
The value 0 disables application layer confirmation.
Note: Event mask 1 in the function block parameters should be used to select events
for being reported via DNP protocol.
• This item is handled internally by the protocol and is not accessible via SPA. The
given name is used only in POD configuration.
122 ABB Automation

for REC 523
)LJ 5HOD\6HWWLQJ7RROZLWK'13SDUDPHWHUV
3.4.4.1. Recommendations for parameter tuning due to specific medium

or link characteristics
)L[HGOLQH56WRFRQQHFWLRQ
There is no risk of frame collisions on the link. Unsolicited responses from REC 523
can be enabled and the data link layer transmit after receive timeout can be set to 0.
Depending on the link reliability and capabilities of the master station, different data
transfer security levels can be chosen:
• Minimum security – when connection can be trusted 100% - no data link layer
acknowledgements and no application layer confirmations (confirmation type
selector set to 0).
• Maximum security on the data link layer – when the master station does not
support application layer confirmations - data link layer acknowledgements but
no application layer acknowledgements (confirmation type selector set to 1).
• Average security on application layer – when the master station supports
application layer confirmations – no data link layer acknowledgements, and
application layer confirmations used only for unsolicited responses (confirmation
type selector set to 2). This situation is optimum from the link load point of view
(all messages containing process data will be protected: when an unsolicited
response has been lost there will be no confirmation, when a response to the
master station request has been lost, the master station will repeat the request).
• Full security on the application layer – when the master station supports
application layer confirmations, but does not support request retransmissions – no
ABB Automation 123

for REC 523
data link layer acknowledgements, and application layer confirmations used for
all responses (confirmation type selector set to 4).
• Full security on both layers - when the master station supports application layer
confirmations and the connection is of very poor quality - data link layer
acknowledgements and application layer confirmations used for all responses
(confirmation type selector set to 5).
Note:
If confirmations or acknowledgements are used, the number of retransmissions on
the link layer or on the application layer must be set to a value greater than 0
(otherwise, the configuration will be the same as with the confirmation type selector
0)
)L[HGOLQHEXVWRSRORJ\
Many RTUs can be connected to one (or more) master stations. Collisions on the
link are possible. To limit the risk of collisions caused by simultaneous responses
from different REC 523 units, the “data link layer transmit after receive timeout”
parameter can be used to assign time slots for every REC 523 unit. The most
privileged unit can have this timeout set to 0 ms and each next unit to a multiple of
the time needed to transmit a link layer frame of maximum size. For example, if we
have one master station connected to three REC 523 units at a speed of 9600 bps,
then we should assign a 0 ms timeout to the first REC 523 unit (the most privileged),
300 ms timeout to the second and 600 ms to the third (the least privileged). 300 ms
is the time needed to transmit the biggest possible link layer frame (292 bytes) at
9600 bps.
This approach can only be applied when it is possible to set this timeout in all
secondary (controlled) stations. Otherwise, acknowledgements or confirmations
have to be relied on (the best solution for this case is to use the confirmation type
selector 2 because of the minimal use of the link throughput).
'LDOXSFRQQHFWLRQ±UHTXHVWLQJFRQQHFWLRQWRPDVWHUVWDWLRQQRWDOORZHG
Only the master station can initiate the connection (dial the number). Unsolicited
reporting should be switched off (by setting the unsolicited reporting flag for all
events to 0 in the POD). There is no risk of frame collisions on the link.
If the master station supports request retransmissions, the confirmation type selector
can be set to 0. Otherwise, data link layer acknowledgements (confirmation type
selector 1) or application confirmations (confirmation type selector 4) have to be
used.
'LDOXSFRQQHFWLRQ±UHTXHVWLQJFRQQHFWLRQWRPDVWHUVWDWLRQDOORZHG
Unsolicited reporting can be switched on. REC 523 will try to connect again in
random intervals after an unsuccessful attempt. There is no risk of frame collisions
on the link. If the master station supports request retransmissions, the confirmation
type selector can be set to 0. Otherwise, data link layer acknowledgements
(confirmation type selector 1) or application confirmations (confirmation type
selector 4) have to be used.
'LDOXSFRQQHFWLRQZLWKEDFNXSPDVWHUVWDWLRQ±UHTXHVWLQJFRQQHFWLRQWR
PDVWHUVWDWLRQDOORZHG
124 ABB Automation

for REC 523
Unsolicited reporting can be switched on. REC 523 will try to connect again in
random intervals after an unsuccessful attempt. To connect to the backup master
station 1st spare dialling string should be used. There is no risk of frame collisions
on the link. If the master station supports request retransmissions, the confirmation
type selector can be set to 0. Otherwise, data link layer acknowledgements
(confirmation type selector 1) or application confirmations (confirmation type
selector 4) have to be used.
Note:
• For communication over leased line, REC 523 should be configured as in the
fixed line connection mode. The utilized modem must be set up from the terminal
program. For this kind of communication, the end of frame timeout should be set
according to the channel characteristics.
• For communication in the dial-up connection mode, the utilized modem is
configured by REC 523. The modem initialization string must not include any
command that establishes connection with the remote modem. Only the dialling
string shall be used for this purpose.
• The longest processing time (approx. 440 ms) is required to build a response to
the request for data of all classes. The application layer timeout set on the DNP
master end must take into account this maximum latency and the required
transmission time for both request and response.
• Emergency dialling string can be used to indicate that REC 523 could not connect
to the master station. In this string telephone number of the operator GSM phone
should be included. Caller identification feature should be supported in the
network to make it usable.
• If GSM modem is used and it requires PIN code after start-up then PIN code
string should be used for this purpose. Modem initialization string should not
include any command that send PIN code to the modem.
• If modem signals are to be used only port X5.1 can be used.
• RS485 can be used only in balanced mode (event reporting should be disabled).
To make possible communication via this port RTS signal must be used
3.4.4.2. Application mapping review

In most of the system configurations the application mapping defined by the default
POD should be acceptable. However, there might occur some cases when the
modification of the visible POD table is necessary:
• when a different addressing concept is used in the system because of the master
station’s requirements or limitations in the protocol data addressing (re-
addressing of mapped application objects),
• to eliminate obsolete data and events from active function blocks (data items not
required or not processed by the master station).
The visible POD table can be uploaded, reviewed and modified using a Protocol
Editing Tool. The most common operations are:
• removing selected data items from the mapping – this can be done by setting the
“in use” flag (column 10) to 0
• disabling spontaneous reporting for selected events – this can be done by setting
the “unsolicited reporting flag” (column 9) to 0
ABB Automation 125

for REC 523
• removing the assignment of selected static data items to class 0 – this can be done
by setting the “class” value (column 6) to 4
In the default POD the mapped function blocks occupy the assigned ranges of
addresses (DNP point numbers). Therefore, for a downloaded application the overall
addressing of data will not be continuous. Some master stations, however, may
accept only a continuous address map. In this case the addresses of data items will
have to be changed. When doing this, a certain rule must be obeyed. For further
information about the rule, please refer to the rule 3 in chapter “Point numbering
overall rules” on page 24.
A detailed description of the contents of visible POD and examples of mapping are
given in section “Defining the POD contents” on page 42.
After changing the contents of the visible POD, the table can be downloaded to REC
523 and the tool will enforce the storing of data in the non-volatile memory followed
by the device reset. In this way the updated table will be used to generate the
operational POD.
3.4.4.3. DNP/LON gateway function

It is possible to use REC523 as DNP/LON gateway. There are 32 analogue inputs,
32 analogue outputs, 32 binary inputs and 32 binary outputs (from DNP point of
view) that represent LON network variables. Change of any input network variable
(seen from DNP side as an analogue or binary input) will be reported as a change
event on DNP side. Setting a new value of binary output or analogue output will
result in sending an appropriate output network variable update message on LON
side.
DNP/LON gateway function can be used in two ways:
• Directly - by using LON network variables as data points (data from channels 25
and 26)
• As remote I/O - by connecting LON network variables to inputs and outputs of
function blocks in the application.
Example of using remote I/O:
126 ABB Automation

for REC 523
MEAI1_1
BOOL2INT_1
MEAI1
SysAI MeasOut BOOL2INT PSC_7_LED9_16
RawAI HighWarning B0 Q
IV HighAlarm B1
RESET LowWarning B2
LowAlarm B3
ERR B4
B5
B6
UINT_TO_REAL
COMM_IN1 B7
B8
B9
B10
UINT_TO_BOOL COIND1_1
COMM_IN33 COIND1 B11
BINOPEN B12
BINCLOSE B13
UINT_TO_BOOL
COMM_IN34 IV B14
B15
LED 9: blink - measured signal high warning, on - measured signal high alarm
LED 10: blink - measured signal low warning, on - measured signal high alarm
LED 11: on - remote indication open
remote
LED 12: on - remote indication closed
Note:
LON interface must be properly configured to use DNP/LON gateway function.
ABB Automation 127

DNP 3.0 1MRS 750958-MUM
4. Appendix A: Profile Checklist
DNP V3.00
DEVICE PROFILE DOCUMENT

Vendor Name: ABB Substation Automation Oy
Device Name: REC 523 rev. D
Highest DNP Level Supported: Device Function:
Slave
For Requests: L2
For Responses: L2
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported (the
complete list is described in the attached table):
Additions to level 2 are marked as shaded in the implementation table
Maximum Data Link Frame Size Maximum Application Fragment Size
(octets): (octets):
Transmitted 292 Transmitted 2048

Received (must be 292) Received 2048
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
Configurable, range from 0 to 255 with Configurable, range from 0 to 255 with
primary data link layer retransmission application layer retransmission count
count
Requires Data Link Layer Confirmation:
Configurable, with confirmation type selector, default NO ACK
Requires Application Layer Confirmation:
Configurable with confirmation type selector when reporting Event Data (Slave devices only)
Always after response to reset request
Always when sending multi-fragment responses (Slave devices only)
Configurable, with confirmation type selector
Timeouts while waiting for:
Data Link Confirm Configurable with primary data link layer timeout, not relevant when no ACK
Complete Appl. Fragment No, multi-fragment application frames not supported
Application Confirm Configurable with application layer timeout
Complete Appl. Response

No, not relevant in slave
128 ABB Automation

1MRS 750958-MUM DNP 3.0
Sends/Executes Control Operations:

WRITE Binary Outputs Only for software points
SELECT/OPERATE Always
DIRECT OPERATE Always
DIRECT OPERATE - NO Always
ACK
Count Always 1
Code 1, 2 or 3
Trip/Close 1,2 according direction
Pulse On Ignored
Queue Always 0
Clear Queue 0 or 1
),//2877+()2//2:,1*,7(06)256/$9('(9,&(621/<
Reports Binary Input Change Events Reports time-tagged Binary Input
when no specific variation requested: 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
Configurable to send both, one or the
Time
other (attach explanation)
Configurable, depends of objects
basic variation. (variation used at
initialisation)
Sends Unsolicited Responses: Sends Static Data in Unsolicited
Responses:
Never
Never
Configurable, by UR flag in POD
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, default object and Configurable (attach explanation)
variation
16 Bits
Default Object 20
32 Bits, but roll-over bits not used
Default Variation 5
Other Value _____________
Point-by-point list attached
Point-by-point list attached
Sends Multi-Fragment Responses: Yes No
ABB Automation 129

DNP 3.0 1MRS 750958-MUM
6XSSRUWHGIXQFWLRQFRGHV
CODE FUNCTION DESCRIPTION Supported

Transfer Function Codes
0 Confirm Message fragment confirmation Yes
No response
1 Read Request objects from outstation Yes
Respond with requested objects
2 Write Store specified objects to outstation Yes
Respond with status of operation
Control Function Codes
3 Select Select output point of outstation Yes
Respond with status of control point
4 Operate Set output that has previously Yes
selected
5 Direct operate Set output directly Yes
6 Direct operate Set output directly Yes
- no ack No response
Freeze Function Codes
7 Immediate Freeze Copy specified objects to freeze buffer No
8 Immediate Freeze Copy specified objects to freeze buffer No
-no ack No response
9 Freeze and Clear Copy specified objects to freeze buffer No
and clear objects
10 Freeze and Clear Copy specified objects to freeze buffer No
-no ack and clear objects
No response
11 Freeze with time Copy specified objects to freeze buffer No
at specified time
12 Freeze with time Copy specified objects to freeze buffer No
-no ack at specified time
No response
Application Control Function Codes
13 Cold Restart Perform desired reset sequence Yes
Respond with a time object
14 Warm Restart Perform desired partial reset operation Yes
Respond with a time object
15 Initialise Data to Defaults Initialise the specified data to default No
16 Initialise Application Ready the specified application to run No
17 Start Application Start the specified application to run Yes
18 Stop Application Stop the specified application to run Yes
Configuration Function Codes
130 ABB Automation

1MRS 750958-MUM DNP 3.0
19 Save configuration Save configuration No

20 Enable Unsolicited Messages Enable Unsolicited Messages Yes
21 Disable Unsolicited Disable Unsolicited Messages Yes
Messages Respond with status of operation
22 Assign Class Assign specified objects to a class Yes
Time Synchronisation Function Codes
23 Delay Measurement Perform propagation delay Yes
measurement
Response Function Codes
0 Confirm Message fragment confirmation Yes
129 Response Response to request message Yes
130 Unsolicited Message Spontaneous message without Yes
request
6XSSRUWHGREMHFWV
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Qual Func Qual

Obj Var Description Codes Codes Codes Codes
(dec) (hex) (dec) (hex)
1 0 Binary Input - 1 06 129 27
All Variations
1 1 Binary Input 1 all except 129 same as in
0B and 06 request
1 2 Binary Input with Status 1 all except 129 27 when
0B all points
were
requested
otherwise
same as in
request
2 0 Binary Input Change - All 1 06
Variations
2 1 Binary Input Change without 1,20, 21, 06 129, 130 27
Time 22
2 2 Binary Input Change with Time 1,20, 21, 06 129, 130 27
22
2 3 Binary Input Change with
Relative Time
10 0 Binary Output - 1,20, 21, 06 129, 130 27
All Variations 22
10 1 Binary Output 1 all except 129 same as in
2 0B and 06 request
10 2 Binary Output Status 1 all except 129 27 when
2 0B and 06 all points
in case of were
function 2 requested
otherwise
same as in
request
12 0 Control Block -
All Variations
ABB Automation 131

DNP 3.0 1MRS 750958-MUM
REQUEST RESPONSE
OBJECT
Func Qual Func Qual

12 1 Control Relay Output Block 3, 4, 5, 6 17, 27,28 129 echo of
request +
status
12 2 Pattern Control Block
12 3 Pattern Mask
20 0 Binary Counter - 1 06 129 27
All Variations
20 1 32-Bit Binary Counter
20 3 32-Bit Delta Counter
20 5 32-Bit Binary Counter without 1 all except 129 27 when
Flag 2 0B all points
were
requested
otherwise
same as in
request
20 6 16-Bit Binary Counter without
Flag
20 7 32-Bit Delta Counter without
Flag
20 8 16-Bit Delta Counter without
Flag
21 0 Frozen Counter -
All Variations
21 1 32-Bit Frozen Counter
21 2 16-Bit Frozen Counter
21 3 32-Bit Frozen Delta Counter
21 5 32-Bit Frozen Counter with
Time of Freeze
21 6 16-Bit Frozen Counter with
Time of Freeze
with Time of Freeze
with Time of Freeze
21 9 32-Bit Frozen Counter without
Flag
21 10 16-Bit Frozen Counter without
Flag
without Flag
without Flag
22 0 Counter Change Event - All 1,20, 21, 06 129,130 27
Variations 22
22 1 32-Bit Counter Change Event
without Time
without Time
132 ABB Automation

1MRS 750958-MUM DNP 3.0
REQUEST RESPONSE
OBJECT
Func Qual Func Qual

22 3 32-Bit Delta Counter Change 1 20, 21, 06 129, 130 27
Event without Time 22
22 4 16-Bit Delta Counter Change
Event without Time
with Time
with Time
Event with Time
Event with Time
23 0 Frozen Counter Event - All
Variations
23 1 32-Bit Frozen Counter Event
without Time
without Time
Event without Time
Event without Time
with Time
with Time
Event with Time
Event with Time
30 0 Analogue Input - All Variations 1 06 129 27
30 1 32-Bit Analogue Input
30 2 16-Bit Analogue Input
30 3 32-Bit Analogue Input without 1 all except 129 27 when
Flag 0B all points
were
requested
otherwise
same as in
request
30 4 16-Bit Analogue Input without
Flag
31 0 Frozen Analogue Input - All
Variations
31 1 32-Bit Frozen Analogue Input
with Time of Freeze
with Time of Freeze
without Flag
ABB Automation 133

DNP 3.0 1MRS 750958-MUM
REQUEST RESPONSE
OBJECT
Func Qual Func Qual

without Flag
32 0 Analogue Change Event - All 1, 20, 21, 06 129,129 27
Variations 22
32 1 32-Bit Analogue Change Event 1 20, 21, 06 129,130 27
without Time 22
32 2 16-Bit Analogue Change Event
without Time
with Time
with Time
33 0 Frozen Analogue Event - All
Variations
33 1 32-Bit Frozen Analogue Event
without Time
without Time
with Time
with Time
40 0 Analogue Output Status - All 1 06 129 27
Variations
40 1 32-Bit Analogue Output Status 1 all except 129 27 when
0B all points
were
requested
otherwise
same as in
request
40 2 16-Bit Analogue Output Status
41 0 Analogue Output Block - All
Variations
41 1 32-Bit Analogue Output Block 3, 4, 5, 6 all except 129 echo of
0B and 06 request +
status
41 2 16-Bit Analogue Output Block
50 0 Time and Date - All Variations 1 06 129 27
50 1 Time and Date 1 all except 129 27 when
2 0B and 06 all points
with were
otherwise
same as in
request
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 129 07
134 ABB Automation

1MRS 750958-MUM DNP 3.0
REQUEST RESPONSE
OBJECT
Func Qual Func Qual

52 2 Time Delay Fine 129 07
60 0 All classes 1 06 129 27
60 1 Class 0 Data 1 06 129 27
60 2 Class 1 Data 1 06 129 27
60 3 Class 2 Data 1 06 129 27
60 4 Class 3 Data 1 06 129 27
70 1 File Identifier
80 1 Internal Indications 2 all except 129 -
0B and 06
81 1 Storage Object
82 1 Device Profile
83 1 Private Registration Object
83 2 Private Registration Object
Descriptor
90 1 Application Identifier 17, 18 06 129 -
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
150 0 String - All Variations 1 06 129 27
150 1 String 1, 2 all except 129 27 when
0B and 06 all points
in case of were
otherwise
same as in
request
151 1 Transparent SPA – All 1 06 129 27
Variations
151 1 Transparent SPA 1, 2 all except 129 27 when
0B and 06 all points
in case of were
otherwise
same as in
request
No Object 13, 14
No Object 23
ABB Automation 135

DNP 3.0 1MRS 750958-MUM
5. Appendix B: List of Used Abbreviations
$3&, Application Protocol Control Information

$3'8 Application Protocol Data Unit
&5& Cyclic Redundancy Check
&76 Clear To send
'&' Data Carrier Detect
'&( Data Circuit terminating Equipement
',5 DIRection of physical transmission
'13 Distributed Network Protocol
(3$ Enhanced Performance Architecture
)&% Frame Control Bit
)&9 Frame Count Valid
),1 FINal fragment bit
),5 FIRst fragment bit
,(& International Electrotechnical Commission
,62 International Organization for Stardardization
/3'8 Link Protocol Data Unit
26, Open System Interconnection
3'8 Protocol Data Unit
32' Protocol Object Dictionary
350 PRimary Message
361 Public Switched Network
576 Request To Send
578 Remote Terminal Unit
6'8 Service Data Unit
136 ABB Automation

1MRS 750958-MUM DNP 3.0
ABB Automation 137

1MRS 750958-MUM EN 2000
ABB Substation Automation Oy

P.O. Box 699
FIN-65101 VAASA
Finland
Tel. +358 10 224 000
Fax. +358 10 224 1094
www.abb.fi

Rec523 dnpprotmanENc

Uploaded by

Copyright:

Available Formats

Rec523 dnpprotmanENc

Uploaded by

Document Information

Original Title

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

Rec523 dnpprotmanENc

Uploaded by

Copyright:

Available Formats

DNP 3.

We reserve the right to change data without prior notice.

2.3.1. Byte sequence (string) ..................................................... 38

1. Overview of the Protocol

1.1. Physical layer

1.2. Data link layer

• performing collision avoidance/detection procedures to ensure the reliable

1.3. Transport pseudo-layer

1.4. Application layer

1.5. Frame formats

1.5.1. Overall information

1.5.2. Data link layer frame format

Fixed length header 10 octets Body

1 FCB FCV Primary to Secondary

Field Sub-field Description

1.5.3. Transport layer frame format

Transport header User data (1 - 249 octets)

FIN FIR SEQUENCE

1.5.4. Application layer frame format

1.5.4.1. Application request format

DUI IO...IO DUI IO

Application Control Function Code

FIN FIR CON SEQUENCE

1.5.4.2. Application response format

DUI IO…IO DUI IO

Application Control Function Code Internal Indications

FIN FIR CON SEQUENCE

Bit 5 Current configuration of the outstation is corrupt

Object Qualifier Range

first octet second octet

Range field for messages without data objects

Start 8 bit Stop 8 bit

Qualifier Code 1 or 4, index size 0, points I1 to I2 inclusive

Start 16 bit Stop 16 bit

Qualifier Code 2 or 5, index size 0, points I1 to I2 inclusive

Start 32 bit Stop 32 bit

Qualifier Code 7, index size 1, points are I1, I2 … IQ inclusive

Quantity Index ... Index

Qualifier Code 7, index size 2, points are I1, I2 … IQ inclusive

Quantity Index ... Index

Qualifier Code 7, index size 3, points are I1, I2 … IQ inclusive

Quantity Index ... Index

Qualifier Code 8, index size 0, points are 0…Q-1 inclusive

Qualifier Code 8, index size 1, points are I1, I2 … IQ inclusive

Quantity Index ... Index

Qualifier Code 8, index size 2, points are I1, I2 … IQ inclusive

Quantity Index ... Index

Qualifier Code 8, index size 3, points are I1, I2 … IQ inclusive

Quantity Index ... Index

Qualifier Code 9, index size 0, points are 0…Q-1 inclusive

Qualifier Code 9, index size 1, points are I1, I2 … IQ inclusive

Quantity Index ... Index

Qualifier Code 9, index size 2, points are I1, I2 … IQ inclusive

Quantity Index ... Index

Qualifier Code 9, index size 3, points are I1, I2 … IQ inclusive

Quantity Index ... Index

Start 8 bit Stop 8bit DO DO ... DO

Qualifier Code 1 or 4, index size 0, points I1 to I2 inclusive

Start 16 bit Stop 16 bit DO DO ... DO

• The ELWDQDORJXHLQSXWis an information object used to represent a hardware