99Address Signal name Range Comment673 Unread records left 0...99674 Time stamp of the event, date 2 bytes: YY.MM675 Time stamp of the event, date and time 2 bytes: DD.HH676 Time stamp of the event, time 2 bytes: MM.SS677 Time stamp of the event, time 0...999 0...999 ms678 Modbus DI point or informative event (SPA channel) 0/1* DI event 0 When MSB = 0, bits 14...0indicate the DI point.* Informative event 1 When MSB = 1, bits 14...0indicate the SPA channel.679 DI value or SPA event code* DI event 0/1 In case of a DI event, theregister will contain the DIvalue.* Informative event 0...63 In case of an informative event,the register will contain theSPA event code.a) Readable and writeable register.Structure 4The relay's real-time clock is stored in this structure. It can be updated by presettingthe whole register structure in one Modbus transaction.Table 5.1.15.1.-16 Real-time clock structureAddress Description Range721 Year 0...99722 Month 1...12723 Day 1...31724 Hour 0...23725 Minute 0...59726 Second 0...59727 Hundredth of a second 0...995.1.16. DNP 3.0 remote communication protocolThe DNP 3.0 protocol was developed by Harris Control based on the early versionsof the IEC 60870-5 standard telecontrol protocol specifications. Today, the DNPprotocol specifications are controlled by the DNP Users Group.The DNP protocol supports the ISO OSI (Open System Interconnection) basedmodel, which only specifies physical, data link and application layers. This reducedprotocol stack is referred to as Enhanced Performance Architecture (EPA). Tosupport advanced RTU functions and messages larger than the maximum framelength as defined in the IEC 60870-1, the DNP 3.0 Data Link is to be used with atransport pseudo-layer. As a minimum, the transport pseudo-layer implementsmessage assembly and disassembly services.Feeder Protection RelayTechnical Reference ManualREF 610REF 6101MRS755310