Skip to main content
Home
for DLMS smart meters
Open source solutions for DLMS smart metering

Main navigation

  • Home
  • Products
  • About us
  • Open Source
  • Community
  • Forum
  • Downloads
User account menu
  • Log in

Breadcrumb

  1. Home
  2. Node
  3. M-Bus Client
Profile picture for user Administrator
By Administrator , 17 June, 2020

M-Bus Client

Represents an M-Bus device read by a DLMS meter or gateway. It links the communication port, selected data records and identity of the attached device.

When to use it

For example, configure a gateway to collect water meter readings every hour and map them to its DLMS objects.

Attributes

1. Logical name

Identifies this object instance by its six-part OBIS code. Use it to distinguish this object from other objects of the same class.

2. MBus Port Reference

Identifies the M-Bus port object used to communicate with the attached device.

3. Capture Definition

Identifies the M-Bus data records to capture using their data-information and value-information blocks.

4. Capture Period

Sets the interval between automatic data collections in seconds. A zero value disables periodic collection.

5. Primary Address

Contains the short M-Bus address used to select the attached device.

6. Identification Number

Contains the identification number reported by the attached device.

7. Manufacturer ID

Contains the manufacturer code reported in the M-Bus device identity.

8. Version

Contains the M-Bus product or device revision reported by the attached device.

9. Device Type

Identifies the type of device or measured medium, such as water, heat or gas.

10. Access Number

Contains the access number from the last M-Bus response, which helps identify successive telegrams.

11. Status

Contains status flags reported by the attached device, such as temporary or permanent errors.

12. Alarm

Contains alarm information reported by the attached device.

13. Configuration

Shows the configuration field received from the M-Bus device, including its encryption mode and number of encrypted bytes. Updated on each device readout.

14. Encryption Key Status

Reports the state of the encryption key used with the attached device.

Versions

Attribute availability depends on the object version reported by the meter (version 0: attributes 1-12; version 1: attributes 1-14). Use the version-specific descriptions above when an attribute's meaning or representation differs.

Actions

1. Slave install

Installs a unconfigured slave device.

2. Slave deinstall

De-installs the slave device.

3. Capture

Capture values.

4. Reset alarm

Reset alarm state of the M-Bus slave device.

5. Synchronize clock

Synchronize the clock of the M-Bus slave device.

6. Data send

Send data to the M-Bus slave device.

7. Set encryption key

Sets encryption key to be used with the M-Bus slave device.

8. Transfer key

Transfers an encryption key to the M-Bus slave.

.

  • Create new account
  • Reset your password

Book navigation

  • Activity calendar
  • Association Logical Name
  • Auto Connect
  • Auto answer
  • Clock
  • Compact data
  • Data
  • Demand register
  • Disconnect control
  • Extended register
  • GPRS modem setup
  • GSM diagnostic
  • IEC HDLC setup
  • IEC local port setup
  • IPv6 setup
  • Limiter
  • M-Bus Client
  • M-Bus master port setup
  • M-Bus slave port setup
  • MAC address setup
  • Modem configuration
  • PPP setup
  • Profile generic
  • Push Setup
  • Register
  • Register Monitor
  • Register table
  • SAP assignment
  • Script table
  • Security setup
  • Single action schedule
  • Special days table
  • Status mapping
  • Tcp Udp Setup
  • Trasferimento dell'immagine
  • Utility tables
  • Manufacturer custom objects
  • Account
  • Arbitrator
  • Array manager
  • Charge
  • CoAP diagnostics
  • CoAP setup
  • Communication port protection
  • Credit
  • Data protection
  • Function control
  • G3-PLC 6LoWPAN setup
  • G3-PLC MAC layer counters
  • G3-PLC MAC setup
  • LLC SSCS setup
  • LTE monitoring
  • M-Bus diagnostics
  • M-Bus port setup
  • Network time setup
  • Parameter monitor
  • PRIME application identification
  • PRIME MAC counters
  • PRIME MAC functional parameters
  • PRIME MAC setup
  • PRIME network administration data
  • PRIME physical layer counters
  • S-FSK active initiator
  • S-FSK MAC counters
  • S-FSK physical and MAC setup
  • S-FSK reporting system list
  • S-FSK synchronisation timeouts
  • Schedule
  • Short name association
  • STS payment token settings
  • Tariff plan
  • Token gateway
  • Twisted pair setup
  • Wireless mode Q channel
  • IPv4 setup
  • Register activation

Hire Us!

Latest Releases

  • Thu, 11/19/2026 - 10:57
    Gurux.DLMS.Python 1.0.204
  • Thu, 11/19/2026 - 10:12
    gurux.dlms.c 9.0.2611.1901
  • Tue, 10/13/2026 - 12:00
    gurux.dlms.java 4.0.97
  • Tue, 09/22/2026 - 14:02
    Gurux.DLMS.Net 9.0.2609.2201
  • Mon, 09/21/2026 - 10:18
    Gurux.DLMS.Net 9.0.2609.2101

New forum topics

  • PT.Srikandi Utama Valusindo Telp/Wa 083831618807
  • PT Yonglin Valas Jaya Telp/Wa 083831618807
  • Bank Mandiri Pulang Pisau call/wa 0813-627-9539.
  • Bank Mandiri Banjarmasin Mitra Plaza call/wa 0813-627-9539.
  • Bank Mandiri KC Tamiang Layang call/wa 0813-627-9539.
More
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin