← All Products
Data Concentrator M-Bus
ZENNER EDC B.One ZENNER EDC — M-Bus iletişim modülü. Pulse çıkışlı mekanik sayaçları M-Bus ağına dahil eder, IP68.
🔗
Schneider Electric
Official product page (se.com)
● 6 Argus Registers — Ready Template
ZENNER EDC

EDC B.One

The ZENNER EDC B.One is a compact communication module that brings mechanical water meters with a pulse output onto the M-Bus network. Mounted on the meter, it converts the reed switch pulse signal into the M-Bus EN 13757 protocol, so older mechanical meters can join the Argus EMS infrastructure. Its IP68 rating lets it work safely in wet and buried environments.

Measurement Channels
EntryReed switch pulse (from the mechanical meter)
OutputM-Bus EN 13757-2/-3
Pulse CompatibilityISO 22158
ApplicationMechanical water meter retrofit → M-Bus
Technical Specifications
ProtocolM-Bus EN 13757-2/-3
ConnectionVia an M-Bus TCP gateway (Argus EMS compatible)
PowerBattery powered
Protection ClassIP68
MountingMeter-mounted — retrofit
StandardsEN 13757, ISO 22158

Integration with Argus EMS

The EDC B.One 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 template6 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 not a meter in itself; it collects the M-Bus meters on a loop and serves them from a single point. In buildings with a high meter count it is used to split the loop and shorten the polling round.

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 EDC B.One 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 EDC B.One need a register map to be worked out separately?
No. A ready template with 6 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.
Do the meters on a EDC B.One loop appear individually in Argus EMS?
Yes. Every meter read through the collector has its own device record in Argus EMS; the indexes are stored separately, and billing and leak analysis run per meter.

See Argus at Your Facility

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