← All Products
Data Concentrator M-Bus
ZENNER D1205 EDC-MBus ZENNER EDC — M-Bus veri toplayıcı (data concentrator). 60 sayaca kadar otomatik okuma, lokal depolama.
🔗
Schneider Electric
Official product page (se.com)
● 6 Argus Registers — Ready Template
ZENNER EDC

D1205 EDC-MBus

The ZENNER D1205 EDC-MBus is an electronic data concentrator that reads many M-Bus meters from a single point. It polls a large number of ZENNER M-Bus meters (water, heat, electricity) on a schedule, stores the readings in internal memory and forwards them to upstream systems such as SCADA, BMS or Argus EMS. At dense metering points it is used instead of, or in addition to, an M-Bus TCP gateway.

Measurement Channels
Max. Meter Capacity60 M-Bus devices (primary M-Bus)
Supported MediaWater · Heat · Cooling · Gas · Electricity (M-Bus)
Reading IntervalProgrammable: 15 min – 24 h
Internal StorageMonthly + daily historical index
Protocol (upstream)M-Bus TCP / RS485 Modbus RTU (model-dependent)
Technical Specifications
M-Bus InterfaceEN 13757-2 master — 60 slave
Upstream ConnectionVia an M-Bus TCP gateway (Argus EMS compatible)
Power230 V AC mains + battery backup
MountingDIN rail or wall
Protection ClassIP20 (indoor panel)
Operating Temperature−10 – +55 °C
StandardsEN 13757-2, EN 13757-3

Integration with Argus EMS

The D1205 EDC-MBus 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 D1205 EDC-MBus 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 D1205 EDC-MBus 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 D1205 EDC-MBus 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.