EasyManua.ls Logo

LEM DCBM 400 Series - 7.6. Event Logbook

LEM DCBM 400 Series
95 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Page 83/95
21January2021/Version 0
LEM International SA
Chemin des Aulx 8
1228 PLAN-LES-OUATES Switzerland
www.lem.com

The DCBM features an event logbook,
tracing metrological events as well as
other events linked to the application
software.
When an event occurs, it is permanently
stored into the DCBM logbook, along
with the current status register and the
corresponding UTC timestamp.
!
Logbook entries cannot be erased.
In case the logbook reaches maximal
capacity, the DCBM is out of order (error
logbookIsFull is raised irrevocably,
preventing new transactions).
i
The DCBM can store approximately
40 000 events.
The content of the event logbook can be
retrieved using the /logbook API (see
§7.1). When a large number of events is
stored, retrieving the logbook can take
several minutes. The logbook cannot be
retrieved partially.
The logbook is digitally signed to ensure
its authenticity (authentication and integrity). Refer to section "7.4. Data authenticity".
i
The list of events is available in the Communication Protocols manual.
{
"meterId": "1202531106",
"logbook": [
{
"timestamp": "2020-09-14T10:05:05Z",
"eventCode": "EV_COMMISSIONING",
"status": [
"STATUS_SENSOR_LINK",
"STATUS_TAMPERING",
"STATUS_TIME_SYNC"
]
},
{
"timestamp": "2020-09-14T10:06:03Z",
"eventCode": "EV_POWER_SUPPLY_FAILURE",
"status": [
"STATUS_SENSOR_LINK",
"STATUS_TIME_SYNC"
]
},
{
"timestamp": "2020-09-18T07:34:33Z",
"eventCode": "EV_TIME_SYNC_SUCCEEDED",
"status": [
"STATUS_SENSOR_LINK",
"STATUS_TIME_SYNC"
]
}
}

Table of Contents