7.14. Alarm and event management
7.14.1. Logbook
The meter is factory programmed with a list of pre-defined metering Events. Using the meter support tool, events
from the list can be selected so that if they occur, a time-stamped record is made in the meter Logbook.
Then, whenever necessary, an analysis of meter behaviour can be made by investigating the logbook contents.
The logbook has a maximum capacity of 500 recorded events. Therefore, to ensure the logbook doesn't become
full too quickly, it is recommended that only events related to the installation requirements and the metering
context are selected, for example:
specific action events
communication events
fatal and non-fatal alarm events (appearance and disappearance)
asynchronous events
The selection of all other events should be carefully considered with regard to logbook capacity, for example:
If the event Periodical EOI is selected with a period equal to 15 minutes, then 96 Periodical EOI events will be
recorded each day, filling the logbook in about 5 days.
An integrated functional element called the Event Manager controls and manages all metered events.
7.14.2. Event histories
In addition to the typical event data (event type and time stamp) recorded in the logbook, some specific events
have further associated data elements that also require storage.
These extra data elements are stored in Event History buffers.
The buffer architecture is circular and operates in a first-in first-out (FIFO) fashion, so when the buffer becomes
full, the oldest data elements are overwritten with the latest entries. Therefore, if the data to be overwritten has
not been read, it will be lost.
Event history storage is non-configurable and any data associated with these specific events is always stored,
even if the event itself is not selected to be recorded in the logbook.
The following table contains a typical list of events that are stored in history buffers (these may change due to
meter firmware revision):
To Next Page
Loading...
Need help?
General
