17
Modbus
Register Offset
Description Type
Comment
+0-1 Device serial number
UINT32
+2-4 Device MAC address
CHAR6
+5 Device address
UINT16
Device port address
+6-7 Device IP address
UINT32
Network byte order
+8 Event type
UINT16
See F22 in Section 5
+9 Event sequence number
UINT16
+10-11 Start event timestamp, seconds
UINT32
Local time since Jan 1, 1970
+12-13 Start event timestamp, seconds fraction, in
microseconds
UINT32
+14-15 End event timestamp, seconds
UINT32
Local time since Jan 1, 1970
+16-17 End event timestamp, seconds fraction, in
microseconds
UINT32
+18 Not used
UINT16
Written as 0
+19 Critical trigger ID
UINT16
See Table below
+20-21 Critical trigger value
UINT32
See Table below
+22-23 Reserved
UINT32
Written as 0
The reported trigger type and value depend on the event source and are described in the
following table.
Event Source
Trigger Type
Trigger Value
Setpoint events
Critical setpoint trigger caused setpoint
operation or release (see F12 in Section 5)
Trigger entering or return value
PQ events
PQ event trigger. For polyphase events, the
worst phase is reported (see Generic Data
in Section 3.4)
Maximum fault magnitude on the reported
phase
Fault events
Current phase with highest recorded fault
current (see Generic Data in Section 3.4)
Maximum fault current magnitude on the
reported phase
After receiving a write acknowledgement from a server, a TCP connection is still open for 10
seconds (20 seconds via GPRS) to give the server an opportunity to access meter registers
through an open socket. It may help you access the meter from outside your local
network when the server is located on another network, or when using wireless GPRS
communications. The notification client will respond to all server requests as if it were a
regular incoming connection.
In case a client connection is not used for following data transfers, it is recommended for
the server to close the connection immediately after sending a write acknowledgement;
otherwise there will be a 10-second delay before the next notification may be sent.
If there is no activity on the connection socket, it will be closed in 10 seconds. In the event
a connection attempt was unsuccessful, the notification client retries two more times before
announcing a connection failure.
The server’s IP address, port number and starting Modbus register address are
programmable in the meter. To configure and enable the notification client in your meter
via PAS, select Communication Setup in the Meter Setup menu, and click on the TCP
Notification Client Setup tab. See “Setting-up TCP Notification Client” in the meter manual
for more information on the client setup.
Client connections are triggered via programmable setpoints. To send event notifications to
a server, configure a setpoint to respond to desired triggers or to periodic time events and
add the "Send notification" action to the end of the setpoint actions list.
Setpoint operation events triggered by regular analog and digital triggers are
reported twice - when the event starts and when it ends, except of the pulsed events and
time triggers that will be reported once. In the start notification message, the event end
timestamp is zeroed, and the critical trigger value indicates its entering value, while the
second notification message gives both the event start and end time and shows the trigger
return value.
