CMe3100 DLMS Plugin User's Manual
CMe3100 DLMS Plugin User's Manual
7.5.2.13 Fraud Event Log – Event Id
Data type: long-unsigned
This object holds the event id of the last event logged to Fraud Event Log.
7.5.2.14 Fraud Event Log – Event Message
Data type: visible-string
This object holds the event description of the last event logged to Fraud Event Log.
7.5.2.15 Specific Test Object
Data type: octet-string
This object is used for testing and it should be ignored. It doesn’t hold any information.
7.5.2.16 Billing profile and Load profile 1 & 2
The billing profile is a table with all registers read from the M-Bus meter which contains valid
mapping in the OBIS meter mapping. The billing profile resolution is configurable according to
section 5.2.5.
Attributes:
1: Logical name
2: Buffer (actual data)
Selector 0 (all data) and selector 1(from-to) implemented
3: Capture objects (list of OBIS codes)
4: N/A
5: N/A
6: N/A
7: Entries in use in the database
8: Same as 7
COSEM objects/OBIS codes:
Date/Time: 0.0.1.0.0.255
M-Bus registers: Depends on the OBIS meter mapping file (see section 5.3)
Limitations:
Maximum of 1000 rows can be read in one request.
7.5.2.17 Standard event log and fraud detection log
The standard event log is a table of log items of type Profile Generic with meter related log items.
The data which can be read from the log is date/time of event and event code. The event code is
the status byte read from the M-Bus meter + base value (4000). This gives the possibility to get
the actual M-Bus status code readable from the event code value (4000..4255). Log items will
only be created in the log if the M-Bus status byte changes between readout.
To Next Page
Loading...