---
title: 'Supported meters and correctors'
section: 'Reference'
weight: 2
description: 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.
related:
  - equipment
  - equipment/connection-schemes
  - equipment/equipment-types
  - protocols
---

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](/en/platform/v3/equipment/connection-schemes); for the broader hardware classes the platform integrates with, see [Supported equipment types](/en/platform/v3/equipment/equipment-types).

## European market families

These are the families encountered on European distribution networks. Each has a documented connection diagram for the [VADTel-IIoTU3](/en/devices/vadtel-iiotu3) and [VADTel-AIIoTU8](/en/devices/vadtel-aiiotu8) industrial telemetry units.

| Family | Manufacturer | Wiring diagram                                             | Notes                        |
| ------ | ------------ | ---------------------------------------------------------- | ---------------------------- |
| EK-260 | Elster       | [Yes](/en/platform/v3/equipment/connection-schemes#ek-260) | Natural gas volume corrector |
| EK-270 | Elster       | [Yes](/en/platform/v3/equipment/connection-schemes#ek-270) | Keeps event archives         |
| TC-220 | Elster       | [Yes](/en/platform/v3/equipment/connection-schemes#tc-220) | Natural 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.

| Family             | Device type | Battery reading       | Event archives |
| ------------------ | ----------- | --------------------- | -------------- |
| Flowgaz / ULTRAMAG | 2           | charge in percent     | Yes            |
| Type-J devices     | 7           | —                     | Yes            |
| Irvis              | 14          | —                     | Yes            |
| BBT-DDT            | 23          | voltage in millivolts | —              |
| BK                 | 1           | —                     | —              |

The BK family accounts for half of the channel reference table in the API; see [Directories](/en/api/v1/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](/en/platform/v3/equipment/ai-drivers) for how manufacturer documentation is turned into a working driver, and [Connection diagrams](/en/platform/v3/equipment/connection-schemes) for the wiring side.

## Where the type identifier is used

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

- [List device messages](/en/api/v1/events-and-messages/list-device-messages) — the event and error code reference is per device type.
- [Channels](/en/api/v1/directories/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](/en/platform/v3/ai-analytics/node-reports/battery-forecast) for the thresholds in use.