CMe3100 BACnet Plugin

Product Overview

Application description

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.

The service simplifies the configuration process, allowing users to swiftly set up and deploy M-Bus to BACnet mappings.

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

This BACnet plugin requires CMe3100 to have firmware 1.11.0 or later in order to be activated.

BACnet standard

Our BACnet plugin for CMe3100 follow the BACnet standard, ANSI/ASHRAE Standard 135.

Note

Elvaco has been assigned the vendor ID 1473 as a supplier of BACnet products, by ASHRAE.

Installation

Uploading a new license file

The installation of the plugin is done by uploading a license file and activating the license.

  1. Log in to the web interface.

  2. Go to System > Licenses.

  3. Select Choose file in the Upload new license file section.

  4. Locate the license file you want to upload.

  5. Select Upload

  6. Select Save

    The license is now visible in the Current license(s) window.

  7. Select System > Reboot device to finalize the installation of the plugin.

Note

Important! Reboot the CMe3100 in order to start using the BACnet plugin.

Activating/deactivating the license

  1. Log in to the web interface.

  2. Go to Dashboard > System panel.

  3. Activate or deactivate the plugin in the Service section.

    1. To activate, toggle Enabled to the right.

    2. To deactivate, toggle Enabled to the left.

Configuration

Accessing 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

BACnet settings

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, e.g. 123456.

  • Internal measurements

    • Receiving system will then display available free RAM and CPU temperature of the CMe3100.

M-Bus to BACnet mappings

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]-[decoded M-Bus value] 

For example, 0016123456-Building1-ext-temp 0,0,0,0,0

  • Secondary address static value, serial number of the meter.

  • MOID Editable value, the meter object identification (MOID) is preferably set to describe the location of each meter.

  • Decoded M-Bus VIB 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.

Examples on M-Bus to BACnet mappings

Table 130. Temperature and humidity sensor mappings table

MOID (meter object ID)

Secondary address (meter)

M-Bus Identification

BACnet object name

Unit

House_1

82000019

act-duration.0.0.0.0.0

82000019;House_1;act-duration.0.0.0.0.0

minutes

House_1

82000019

ext-temp.0.0.0.0.0

82000019;House_1;ext-temp.0.0.0.0.0

degrees-celsius

House_1

82000019

voltage.0.0.0.0.0

82000019;House_1;voltage.0.0.0.0.0

volts

House_1

82000019

rf-level.0.0.0.0.0

82000019;House_1;rf-level.0.0.0.0.0

no-units

House_1

82000019

relative-humidity.0.0.0.0.0

82000019;House_1;relative-humidity.0.0.0.0.0

percent-relative-humidity

House_2

82000028

act-duration.0.0.0.0.0

82000028;House_2;act-duration.0.0.0.0.0

minutes

House_2

82000028

ext-temp.0.0.0.0.0

82000028;House_2;ext-temp.0.0.0.0.0

degrees-celsius

House_2

82000028

voltage.0.0.0.0.0

82000028;House_2;voltage.0.0.0.0.0

volts

House_2

82000028

rf-level.0.0.0.0.0

82000028;House_2;rf-level.0.0.0.0.0

no-units

House_2

82000028

relative-humidity.0.0.0.0.0

82000028;House_2;relative-humidity.0.0.0.0.0

percent-relative-humidity


Meter readout

It is important to configure a suiting 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.

Scheduling meter readouts

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.

  1. Go to Meters > Readout schedule and activate scheduled meter readouts.

  2. Set a meter readout Schedule. By for example setting “Every 15th minute”, a readout of all meters in the Meter List will be performed every 15th minute.

  3. Select Save.

The continuous readout mode

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.

Replacing or adding a new meter

To replace a meter means that a new meter is installed in the CMe3100, while the old meter will either stop sending values, or is entirely removed from the CMe3100 meter list.

  • The new meter will automatically translate its measured quantities into BACnet objects, as soon as meter data is collected. This is seen in the M-Bus Mappings table in the device. Furthermore, the new BACnet objects will also be sent to the receiving system automatically. No manual handling is needed within the CMe3100.

  • The old meter will stop sending values, and the CMe3100 will send an alarm about it to the receiving system.

Alarm

If the connection is lost to a meter, the CMe3100 sends the alarm "Communication error" to the receiving system.

Integration

BACnet object identifier

BACnet object identifier is set by object type + "instance" number to create a unique object within its BACnet device. This implementation uses the object type Analog value and the "instance" number is set by the CMe3100 to make the object identifier unique.

Note

The Object identifier will be identical for a BACnet object of a meter, regardless of which CMe3100 is collecting the information. This because the "instance" number of the object identifier is created using the secondary address and the specific measured quantity, which stays the same.

Receiving system

The CMe3100 can be find within the network via the port set in the BACnet plugin settings. The responsibility of setting up the BMS using all the information distributed by the CMe3100 is on the installer.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Article is closed for comments.