Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Home
  • Knowledge base
  • Contact Us
  • Home
  • Connectors
  • M-Bus

MBus - Instance & item setup

How to setup a MBus slave device and fetching data

Written by Mads Mikkelsen

Updated at April 15th, 2024

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Installation & Technical information
    Introduction SIA Connect Standalone SIA Connect ANY-Ware Cellular & WiFi connectivity
  • Configuration in the Web UI
    Getting started with the UI Connectors Instances Items Mapping Data System Network Tools & Add-ons DigiCert IoT Trust Manager
  • Connectors
    Siemens S7 Azure IoT Ethernet/IP Mitsubishi MELSEC OPC-UA Server SQL MQTT Omron Host Link REST API Omron FINS Keyence Beckhoff TwinCAT BACnet Virtual OPC-UA Client MS SQL File M-Bus Modbus
  • Scripting & Variables
    Data formatting
  • Developers
    API documentation Shadow API
  • Tutorials & Guides
    InfluxDB AWS IoT Core - Amazon Web Services Microsoft Power BI KaaIoT Siemens S7 AVEVA Insight SIA Connect Demo Rack Grafana Azure
  • General
+ More

Table of Contents

Automatic scanning of MBus slave devices Instance parameters Item parameters Video instruction Approved level converts

The MBus Connector requires a level converter to convert the MBus data bus to RS232. Most level converters for MBus to RS232 are supported. Contact the SIA Connect team for further details

 

 

Automatic scanning of MBus slave devices

The MBus Connector will automatically scan the network and detect any MBus slave devices and their respective data items

 

 

The MBus (Meter-Bus) protocol is a European standard designed primarily for the reading of heat, gas, water and electricity meters. The protocol supports both wired and wireless implementations, making it versatile for various metering infrastructures. This guide will describe how the Wired MBus Connector is used to acquire data from these energy meters.

 

Instance parameters

The instance contains the following custom parameters

Parameter Description
Name (instance default) The automatic generated name consists of the vendor code + address of the MBus slave device and the type of meter
Address (instance default) Secondary or Primary MBus address of the slave device
Unique ID (instance default) Serial number of the MBus slave device
Device interface The serial port to be used for communicating with the device or where the device has been automatically scanned at.
Timeout TImeout given in milliseconds to wait for a response from the device before considering it unavailable.
Baudrate

Baudrate to be used for communication with the device.

Default: 2400

 

Item parameters

The item parameters that is needed to read the tags in the PLC memory:

Parameter Description
Name (instance default) Name of the data point consists of the unit and the entity returned by the MBus slave device
Unit (instance default) Unit of the measuring returned by the device.

 

Video instruction

Below shows a video on how to get started with MBus:

 

 

Your browser does not support HTML5 video.

 

 

Approved level converts

Most level converts between MBus & RS232 will per default work. 
If you have an unlisted MBus converter please contact us with the vendor and model

 

 

Here is a list of already validated and approved level converts:

Vendor Model Supported MBus slaves
Techbase mBus 10 - 600 (depending on model)
Relay PW 20 - 250 (depending on model)
     

 

 

mbus energy meter electricity meter water meter heat meter gas meter smart building esg

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Virtual - Connector setup
  • Reset network configuration to default
  • Writing data from PLCs to InfluxDB

0
0
Expand