← All Products
Water Meter M-Bus
ZENNER MTKD-N ZENNER — Çok jikli soğuk su sayacı, M-Bus, DN15–DN50. Orta ve büyük tesis uygulamaları.
🔗
Schneider Electric
Official product page (se.com)
● 8 Argus Registers — Ready Template
ZENNER

MTKD-N

The ZENNER MTKD-N is a multi-jet water meter for commercial and industrial buildings that need high accuracy across a wide flow range. Diameter options from DN15 to DN50 suit high-flow applications such as hotels, hospitals and shopping centres. Its integrated M-Bus module connects directly to Argus EMS.

Measurement Channels
Diameter (DN)DN15, DN20, DN25, DN32, DN40, DN50
Q3 Nominal Flow2,5–16 m³/h (by diameter)
Q1 Min. FlowQ3/100 (Class C)
Accuracy ClassClass C (EN 14154) / MID MI-001
Ambient TemperatureMax. 30 °C (cold water)
Max. Operating PressurePN 10 or PN 16
Pressure Loss≤ 0,063 MPa @ Q3
Technical Specifications
ProtocolM-Bus EN 13757-2 / EN 13757-3
ConnectionVia an M-Bus TCP gateway (Argus EMS compatible)
Battery≥ 12 years
Storage unitm³ total + sub-index records
Protection ClassIP54
MountingHorizontal / vertical / inclined
StandardsEN 14154, MID 2014/32/EU Annex MI-001, OIML R49

Integration with Argus EMS

The MTKD-N connects to Argus EMS over M-Bus (EN 13757) two-wire meter loop, and because a ready register template ships with the platform you do not have to work out a point map on site. The field agent polls the device every 60 seconds by default, writes the reading into a local queue first and then forwards it to the server over MQTT/TLS; nothing is deleted before the server acknowledges it. Hourly and daily summaries are derived from these raw readings, and the consumption and cost screens are fed from the same series.

ProtocolM-Bus (EN 13757) two-wire meter loop
Connection pathThe M-Bus loop is read through an M-Bus TCP gateway
Default polling period60 seconds (field agent)
Points in the ready template8 registers
Consumption calculationDifference of the m³ index over the period
Data assuranceLocal queue plus server acknowledgement; nothing is deleted before it is confirmed

When Is This Model the Right Choice?

It is used to meter water consumption per flat, tenant or zone; the index is read remotely, so the monthly manual reading round is no longer needed. The same measurement forms the basis both for billing and for hunting leaks through night-flow analysis.

The M-Bus loop is two-wire and meters connect in parallel on the same pair, so no dedicated cable is pulled per meter. Loop length, conductor cross-section and the number of meters on the loop are assessed together, because an M-Bus gateway can only drive a limited load. Meter addresses (primary/secondary) are verified one by one during commissioning.

Frequently Asked Questions

How is the MTKD-N connected to Argus EMS?
It connects over M-Bus (EN 13757) two-wire meter loop: the M-Bus loop is read through an M-Bus TCP gateway. The field agent polls the device every 60 seconds by default, writes the readings into a local queue and forwards them to the server over MQTT/TLS. If the link drops the data waits in the queue and is backfilled once the connection returns.
Does the MTKD-N need a register map to be worked out separately?
No. A ready template with 8 points is defined in Argus EMS; you pick the template when adding the device and enter its address and slave ID. The point-by-point mapping step on site disappears, and the same model is read with the same template in every project.
Can the MTKD-N be used for per-flat or per-tenant water billing?
Yes. Each meter's index is read separately, the period difference is computed in m³ and multiplied by the water tariff in force. The gap between the main meter and the sum of the sub-meters is tracked as well, and that gap is where leak and loss hunting starts.

See Argus at Your Facility

Explore the system with your own data in a demo session.