Supported meters and correctors

Consolidated list of the gas volume correctors and metering device families the IIoT Platform reads, with their device type identifiers and the interface used for each.

The platform reads archives from several corrector and metering device families. Each family is identified in the API by a numeric device type identifier (equipment_type_id), which selects the driver used to decode its archives.

This page consolidates that list. For wiring, see Connection diagrams for telemetry units; for the broader hardware classes the platform integrates with, see Supported equipment types.

European market families

These are the families encountered on European distribution networks. Each has a documented connection diagram for the VADTel-IIoTU3 and VADTel-AIIoTU8 industrial telemetry units.

FamilyManufacturerWiring diagramNotes
EK-260ElsterYesNatural gas volume corrector
EK-270ElsterYesKeeps event archives
TC-220ElsterYesNatural gas volume corrector

Additional regional families

The families below are in production use outside the European Union, where they are read from live installations. They are unlikely to appear on a European network, but they are what proves the driver layer in practice: each has its own archive layout and read sequence, and all of them are read through the same API. None has a published wiring diagram in this documentation.

FamilyDevice typeBattery readingEvent archives
Flowgaz / ULTRAMAG2charge in percentYes
Type-J devices7Yes
Irvis14Yes
BBT-DDT23voltage in millivolts
BK1

The BK family accounts for half of the channel reference table in the API; see Directories for its full channel and archive breakdown.

Adding a family

Support for a new corrector family is a driver task, not a configuration change: each family has its own archive layout and read sequence. See Using AI in driver development for how manufacturer documentation is turned into a working driver, and Connection diagrams for the wiring side.

Where the type identifier is used

The device type identifier is required by several endpoints and reports:

  • List device messages — the event and error code reference is per device type.
  • Channels — the channel set differs by device type.
  • Events explorer and Battery forecast reports — the breakdown is requested per device type, and only types that keep event archives can be analyzed.

Battery-forecast thresholds are family-specific because the families report the battery differently: some in percent of charge, others in volts or millivolts. See Battery forecast for the thresholds in use.

Sujets connexes

Dernière mise à jour le

Cette page vous a-t-elle été utile ?