CMe3100 BACnet Plugin
The CMe3100 BACnet plugin bridges the gap between M-Bus metering infrastructure and BACnet systems, enabling the extraction and conversion of M-Bus meter values into BACnet value objects. This integration ensures compatibility and interoperability between diverse metering devices and building management systems using BACnet IP.
The service simplifies the configuration process, allowing users to swiftly set up and deploy M-Bus data to BACnet analog values.
Note
This BACnet plugin does not change anything in the ordinary meter collection of the CMe3100. What it does is to translate all collected values and translate it to BACnet objects.
Note
Elvaco strongly recommends to update your CMe3100 to firmware version 1.12.1, or the latest released firmware for best performance. The BACnet plugin requires CMe3100 to have firmware 1.11.0 or later in order to be able to activate the plugin.
The installation of the plugin is done by uploading a license file and activating the license.
-
Log in to the web interface.
-
Go to System>Licenses.
-
Select Choose file in the Upload new licenses section.
-
Locate the license file you want to upload.
-
Select Upload.
-
Select Save.
The license is now visible in the Current license (s) window.
-
Select System> Reboot device to finalize the installation of the plugin.
Note
Important! Reboot the CMe3100 in order to start using the BACnet plugin.
Go to the BACnet Plugin in the web interface of the CMe3100. This page can be accessed in two ways:
-
Configuration> Services>BACnet
-
Dashboards>System Panel > BACnet
Available subpages are:
-
Settings
-
M-Bus mappings
-
Import
This section shows configurable settings for this CMe3100 BACnet plugin.
-
Port
-
Standard port för BACnet/IP devices is set by default, port 47808 (BAC0), but can be configured to another port.
-
-
Name
-
Name representation of the CMe3100. By default is the hostname of the device, e.g. CMe3100-0016123456.
-
-
Instance number
-
Identification of the device which need to be unique to avoid collisions in the network. By default, the instance number is extracted from the last six numbers in the serial number without starting zeros, e.g. 123456 or 3456.
-
-
Internal measurements
-
If checked, the receiving system will then display available free RAM and CPU temperature of the CMe3100.
-
This section shows all available meter values read by the CMe3100. M-Bus meter values are automatically translated into BACnet objects. The BACnet object is named according to:
[secondary address]-[MOID]-[M-Bus DIB]
For example, 0016123456-Building1-ext-temp 0,0,0,0,0
-
Secondary addressstatic value, serial number of the meter.
-
MOID Editable value, the meter object identification (MOID) is preferably set to describe the location of each meter.
-
M-BUS DIB static value, one of several meter values received from a meter.
For all units that exist in both the M-Bus standard and the BACnet standard, the units are transferred together with the BACnet object. If not, the unit field will state no-units. By pressing Export all, a csv file is downloaded containing the same information seen in the graphical user interface.
Note
The CMe3100 must have done at least one readout from the meter before the M-bus to BACnet mappings has been created, otherwise the list will be empty. If no values has been read yet, you can manually perform the command Read all & store to collect meter values from all installed meters.
BACnet object identifier (Object ID) is set and saved automatically by the CMe3100. The Object ID is built up by a maximum of 6 numbers, and the convention is XXXXYY, where XXXX state which meter and YY state the measured quantity. For instance, the Object IDs 900 and 901 are the first two measured quantities for meter number 9 and 20700, 20701 and 20702 are the three first measured quantities for meter number 207.
Note
In firmware version 1.12.0 and forward, the Object ID is automatically set and saved by the CMe3100 depending on the order values has been collected from meters. In firmware version 1.11.0 however, the BACnet object ID was was a calculated value extracted from the secondary address of the meters.
Warning
How the CMe3100 sets the BACnet object IDs changes between firmware version 1.11.0 and 1.12.0. This means that when upgrading to firmware 1.12.0 the M-Bus to BACnet mappings will receive new Object IDs. It is possible to change this back using the import functionality.
Table 128. Temperature and humidity sensor mappings table
MOID (meter object ID) |
Secondary address (meter) |
M-Bus DIB |
BACnet Object ID |
BACnet Object Name |
Unit |
---|---|---|---|---|---|
House_1 |
82000019 |
act-duration.0.0.0.0.0 |
100 |
82000019;House_1;act-duration.0.0.0.0.0 |
minutes |
House_1 |
82000019 |
ext-temp.0.0.0.0.0 |
101 |
82000019;House_1;ext-temp.0.0.0.0.0 |
degrees-celsius |
House_1 |
82000019 |
voltage.0.0.0.0.0 |
102 |
82000019;House_1;voltage.0.0.0.0.0 |
volts |
House_1 |
82000019 |
rf-level.0.0.0.0.0 |
103 |
82000019;House_1;rf-level.0.0.0.0.0 |
no-units |
House_1 |
82000019 |
relative-humidity.0.0.0.0.0 |
104 |
82000019;House_1;relative-humidity.0.0.0.0.0 |
percent-relative-humidity |
House_2 |
82000028 |
act-duration.0.0.0.0.0 |
200 |
82000028;House_2;act-duration.0.0.0.0.0 |
minutes |
House_2 |
82000028 |
ext-temp.0.0.0.0.0 |
201 |
82000028;House_2;ext-temp.0.0.0.0.0 |
degrees-celsius |
House_2 |
82000028 |
voltage.0.0.0.0.0 |
202 |
82000028;House_2;voltage.0.0.0.0.0 |
volts |
House_2 |
82000028 |
rf-level.0.0.0.0.0 |
203 |
82000028;House_2;rf-level.0.0.0.0.0 |
no-units |
House_2 |
82000028 |
relative-humidity.0.0.0.0.0 |
204 |
82000028;House_2;relative-humidity.0.0.0.0.0 |
percent-relative-humidity |
The tab import enables the user to change the Object IDs of the different objects in the CMe3100. This is done by
-
Exporting the M-Bus mappings to a csv file
-
Edit the Object IDs
-
Import the csv file and the Object IDs will be updated
Note
It can take some time for the M-Bus mappings table to load after an import is performed.
Warning
This import functionality is created to change Object IDs. Do not change anything other that it.
It is important to configure a suitable readout schedule in CMe3100, in order to have a proper steering from the BACnet data. This can be done by either setting a meter readout interval or by activating Continuous readout.
When all meters have been installed, a readout schedule can be set. It will determine the time interval by which the Metering Gateway will perform readouts of the meters in its Meter List.
The Metering Gateway offers the possibility of performing meter readouts continuously. The device will then constantly collect meter values, which can for example be used by a control system to regulate a heating system. Note that meter values collected through the Continuous Readout Mode will only be held in the internal memory of the M-Bus Metering gateway (not stored in the database) and can only be accessed using integration protocols such as REST, BACnet, Modbus, JSON or DLMS. They will therefore not be included in Push reports. To use Continuous Readout Mode in combination with Push Reports, the meter readout schedule still needs to be set.
Adding a meter to the CMe3100 results in that the new BACnet objects are created with Object IDs in the end of the list. Thus, there is no risk of retaking object IDs of previous meters.
-
The new meter will automatically translate M-Bus values into BACnet objects, as soon as meter data is collected. This is seen in the M-Bus Mappings table in the device.
When replacing a meter, the new meter will receive object IDs according above. However, it is possible to use the CMe3100 to change the object IDs using the import functionality. This way the old meter's object IDs can be replaced by the new meters BACnet objects.
For the removed meter when it stops sending values, the CMe3100 will send an alarm about it to the receiving system.
Comments (0 comments)