Skip to main content

16.13 M-Bus

Overview

M-Bus or Meter-Bus is a protocol for the remote reading of water, gas, or electricity meters. M-Bus is also usable for other types of consumption meters, such as heating systems or water meters. The M-Bus interface is made for communication on two wires, making it cost-effective. M-bus over TCP is also supported. When configured, meters will deliver the data they have collected to a WCC Lite RTU that is connected at periodic intervals (scan_rate_ms) to read all utility meters.

Configuration

M-Bus parameters for the Device tab
Parameter

Type

Description

Required

Default Value

(when not specified)

Range

TCP RTU Min Max
name string  User-friendly device name Yes Yes

 



description string Description of a device No No

 



device_alias string Alphanumeric string to identify a device Yes Yes


enable boolean Enabling/disabling a device No No 1 0 1
protocol string Protocol to be used. Yes Yes
mbus serial, mbus tcp
scan_rate_ms integer All reads and writes will be executed within the timeframe in milliseconds. No No 10000


poll_delay_ms integer Minimum time delay in milliseconds to wait
before sending any data on port.
No No 200


timeout_ms integer Timeout of waiting for an incoming response in milliseconds Yes Yes
0 60000
address string Device address Yes Yes


device string Communication port - Yes
PORT1 PORT2
baudrate integer

Communication speed (baud/s)

-

No

9600

300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200

databits integer

Data bit count for communication

-

No

8

6

9

stopbits integer

Stop bit count for communication

-

No

1

1

2

parity

string

Communication parity option

-

No

none

none, even, odd

serial_close_delay
integer Delay before closing the serial connection. - No 400

ip string The IP address of the TCP slave device Yes -


port integer

TCP communication port

Yes 

-


0 65535
M-Bus parameters for the Signals tab
Parameter

Type

Description

Required

Default Value

(when not specified)

Range

TCP RTU Min Max
signal_name

string

User-­friendly signal name

Yes Yes



device_alias

string

Device alias from a Devices tab

Yes Yes



signal_alias

string

Unique alphanumeric name of the signal to be used

Yes Yes



enable

boolean

Enabling/disabling of an individual signal

No No 1

0

1

log

integer

Enable logging in the event log

No No 0



number_type string Type of a number (FLOAT, DOUBLE, DIGITAL, etc.) Yes Yes


job_todo

string

Tag job as single or multiple comma-separated OBIS codes

Yes Yes



tag_job_todo string Tag sub job Yes Yes