99
Address Signal name Range Comment
673 Unread records left 0...99
674 Time stamp of the event, date 2 bytes: YY.MM
675 Time stamp of the event, date and time 2 bytes: DD.HH
676 Time stamp of the event, time 2 bytes: MM.SS
677 Time stamp of the event, time 0...999 0...999 ms
678 Modbus DI point or informative event (SPA channel) 0/1
*
DI event 0 When MSB = 0, bits 14...0
indicate the DI point.
*
Informative event 1 When MSB = 1, bits 14...0
indicate the SPA channel.
679 DI value or SPA event code
*
DI event 0/1 In case of a DI event, the
register will contain the DI
value.
*
Informative event 0...63 In case of an informative event,
the register will contain the
SPA event code.
a)
Readable and writeable register.
Structure 4
The relay's real-time clock is stored in this structure. It can be updated by presetting
the whole register structure in one Modbus transaction.
Table 5.1.15.1.-16 Real-time clock structure
Address Description Range
721 Year 0...99
722 Month 1...12
723 Day 1...31
724 Hour 0...23
725 Minute 0...59
726 Second 0...59
727 Hundredth of a second 0...99
5.1.16. DNP 3.0 remote communication protocol
The DNP 3.0 protocol was developed by Harris Control based on the early versions
of the IEC 60870-5 standard telecontrol protocol specifications. Today, the DNP
protocol specifications are controlled by the DNP Users Group.
The DNP protocol supports the ISO OSI (Open System Interconnection) based
model, which only specifies physical, data link and application layers. This reduced
protocol stack is referred to as Enhanced Performance Architecture (EPA). To
support advanced RTU functions and messages larger than the maximum frame
length as defined in the IEC 60870-1, the DNP 3.0 Data Link is to be used with a
transport pseudo-layer. As a minimum, the transport pseudo-layer implements
message assembly and disassembly services.
Feeder Protection Relay
Technical Reference Manual
REF 610REF 610
1MRS755310
To Next Page
Loading...
