CMe3100 DLMS Plugin User's Manual
CMe3100 DLMS Plugin User's Manual
page |
19
(
48
)
2022-02-23
Version 1.8
Example values:
0016000000;-2147483648;2000-01-01
01:00:00;00;HYD;37;water;10;0;0;47559461;47559461;85,946;0,000;0,000;27,300;14399;22525;
167;2016-01-06 16:50:00
Mapping sample
Below is a sample of how to map OBIS codes for getting decoded M-bus data:
...
{
"includeInPush": "ALL",
"mbusTelegram": 0,
"mbusKeys": ["mbus.telegram.decoded.value "],
"dlmsObisCode": "0.0.1.2.128.255",
"dlmsScaler": 0,
"dlmsUnit": 0,
"dlmsClass": "data",
"dlmsDataType": 10,
"dlmsDefaultValue": null,
"mbusUnit": null,
"mbusDescriptionLong": null,
"mbusTariff": null,
"mbusStorageNumber": 0,
"mbusSubUnit": null,
"mbusFunction": null
}
,
{
"includeInPush": "ALL",
"mbusTelegram": 0,
"mbusKeys": ["mbus.telegram.decoded.header "],
"dlmsObisCode": "0.0.1.3.128.255",
"dlmsScaler": 0,
"dlmsUnit": 0,
"dlmsClass": "data",
"dlmsDataType": 10,
"dlmsDefaultValue": null,
"mbusUnit": null,
"mbusDescriptionLong": null,
"mbusTariff": null,
"mbusStorageNumber": 0,
"mbusSubUnit": null,
"mbusFunction": null
},
...
5.3.5 Excluding OBIS codes from Push Reports
By default all OBIS codes included in a mapping file, will be included in all push reports for
matching meters. It is possible remove a specific OBIS code by removing it from the mapping file,
thus making it unavailable over DLMS, or setting the property “
includeInPush
” to “NONE”.
5.3.6 Meter mapping file properties
Top-level properties:
Property name
Type
Description
type
String
The type of meter that this translation applies to.
