Events and alerts
Issue 1.2
129/143
D000058620 en a
– E470 Series 3 SMETS2 100 mm – ZCX310 – User Manual and Functional Description
© Gyr
22
Events and alerts
The meter, as a minimum, supports all the relevant mandatory events and
alerts according SMETS2/GBCS plus those required for certification under
the Measuring Instruments Directive (MID).
These events and alerts are set out in the separate document
«E470
SMETS2 Events and Alerts».
22.1 Event logs
The meter records events into several event logs, sets and clears the
corresponding errors and triggers the corresponding alarms.
An event log is a profile in which events are stored asynchronously in the
order they occur. It is used as a logbook to track the behaviour of the
meter.
If an event occurs, the point in time as well as the event number and the
current device status is stored in the event log.
The event logs are organised as circular buffers. Once the buffer is full, the
oldest entry will be overwritten by the most recent one.
The event log entries can be read via communication.
The meter supports the following event logs:
Security Log
Event Log
Power Event Log
Auxiliary Load Control Switch (ALCS) Log
The classification of an event is grouped into one of the following
categories:
I
– Information – For information and input to the relevant DCC User’s
business processes.
E
– Exception – An exception may have occurred on the meter – which
should be monitored for repeat occurrences and may require further
investigation or action.
F
– Fault – A potential meter fault which requires follow up action and
possible meter replacement.
22.2 Alerts
The meters support the management of Alerts in the following manner.
Type (1) Alerts
– Alerts communicate the alert code and
date/timestamp,
Type (2) Alerts
– Alerts communicate the alert code, date/timestamp
plus additional payload data relevant to the alert.
Whether it is a Wide Area Network (WAN) alert sent via the DCC
Whether it is a Home Area Network (HAN) alert sent via HAN
devices
Whether it is ‘Always On’ or is configured by the responsible user
If it is configurable, who the relevant responsible party is for
configuration of the alert
If required, the payload data that is sent with the alert if it is a type
(2) alert.
