The Energy Meter Standard Event Log

Reading Time: 2 min
DLMS-EVENT-LOG
DLMS-EVENT-LOG

The energy meter event log-book

All extraordinary things happen inside or close to an electronic meter are called “events”. An event has at least one time record (date & time of occurrence). Some events can also have an end-time stamp. Depending on the energy meter type the records are collected in the event log books. Events are handled as FIFO objects (first in, first out). The capacity for event logs can be different.

All events are captured by the DLMS object structure. For interoperability IDIS has set up best practice log book classifications. A typical log-book structure for a high-end smart meter can look like this:

Event log objectNumber of records
Standard event log255
Tamper event log255
Power quality event log255
Disconnection event log64
Power down event log64
Power failure event log64
Communication event log255
Certification data log100
Overview for event classification

Standard event log

Today we only look at the standard event log. The description for the other logs will follow in different blogs.
The standard event log contains all events that are not recorded in other event logs.

Standard event logOBIS
Standard event log, event object96.11.0.255
Standard event log99.98.0.255
OBIS definitions for standard event log
IDISEventDescription
3DST enabled or disabledIndicates the regular change from and to daylight saving time. The time stamp shows the time before the change. This event is not set in case of manual clock changes and in case of power failures.
4Before Clock adjustedClock has been adjusted. The date/time stored is the old date/time before adjusting the clock.
5After Clock adjustedClock has been adjusted. The date/time stored is the new date/time after adjustment
6Clock invalidClock maybe invalid, e.g. if the power reserve of the clock is exhausted. It is set at power up of the meter.
7Replace batteryBattery has reached expected end of lifetime and must be replaced.
9TOU activatedIndicates that the former passive TOU has been activated
12Program memory errorPhysical or logical error in the program memory
13RAM errorPhysical or logical error in RAM
14NV memory errorPhysical or logical error in non-violate memory
15Watchdog errorIndicates watch dog reset or hardware reset of the microcontroller
16Measurement system errorLogical or physical error in the measurement system
17Firmware ready for activationIndicates that the new firmware has been successfully downloaded and verified. The firmware is ready for activation.
18Firmware verification failedThe transferred firmware verification failed. Firmware cannot be activated.
19Passive TOU programmedA new passive TOU structure or a new activation date/time were programmed.
48Global key changedOne or more global keys changed
88Wrong phase sequenceWrong mains connection. Indicates tamper or wrong installation.
89Missing neutralIndicates that the neutral connection from the supplier to the meter is interrupted. The phase voltages measured by the meter may differ from the nominal values with neutral.
230Fatal errorIndicates occurrence of a fatal error
231Billing resetBilling reset was executed
254Load profile clearedAny load profile was cleared
255Event log clearedIndicates that the event log was cleared. This is always the first entry in an event log. It is only stored in the affected event log.
Commonly used IDIS event codes for the standard event log

What do we learn?

The standard event log provides mainly meter status information. It can be downloaded cyclic from the meter to have the whole meter history available for review and action in the system database. All events can also be pushed to the system if necessary and reasonable.

For end-customer support the event log can be read out on demand. Please contact us if you have specific questions or use the comments section below.

Thank you for reading.

Leave a Reply

Your email address will not be published. Required fields are marked *