rbAmp
EN
Shop

Solution · Sub-metering

A counter per tenant, not a cabinet of meters

Three tenants, or five machines, usually means three or five separate meters, each with its own wiring, its own box and its own reading trip. One rbAmp STD-U3I3 keeps an import and an export energy counter for every current channel instead — one device, one bus, a line per party.

What this is, and what it is not

STD is a sub-metering and monitoring instrument. It is not a utility settlement meter and it makes no certification claims.

That sentence decides what the page is for. Internal allocation — who used what, on your own premises, by your own agreement — is exactly the job. Anything that has to stand up as a utility's billing instrument is not, and no configuration changes that.

How one module keeps several accounts

A counter per channel, both directions

Every current channel carries its own import and export energy counter — so a tenant with a solar share is two numbers, not one net value.

Written every second

The counters are saved on the module itself every second, so a controller reboot or a power cut does not restart anybody's account.

Each channel as its own meter

For a system that expects one meter per line, a channel can be read on its own virtual unit id — a read-only single-phase view with voltage, current and power. Energy is read from the module's own id.

How it reaches the system that does the accounting

  • Modbus RTU to an accounting or building system. The module speaks Modbus RTU over its UART lines, with unit id, baud rate and frame set in the configuration registers. ⚠️ There is no RS-485 transceiver on the module — the connector carries UART TTL and a driver-enable line for an external one. That transceiver is part of your build, not of the module.
  • I²C to your own controller. An ESP32 — or any controller on the bus — reads the same counters directly, with the per-channel values and both energy directions.
  • Several modules, one bus. More lines than one module has channels is another module on the same bus, each with its own address.

Modbus transport → · Register map → · I²C transport →

A worked workshop

  1. One STD-U3I3 for the lines you are charging for. Three current channels, each with its own counters, each on its own clamp.
  2. Add the external RS-485 transceiver if the accounting system speaks Modbus; skip it entirely if your own controller reads the bus directly.
  3. Put BASIC on the shared branches — lighting, compressor, the kettle in the corner. Shared consumption measured is shared consumption that can be divided on a rule instead of on an argument.
  4. Read on a schedule, not on a visit. The counters are cumulative and survive restarts, so a monthly figure is a subtraction, not a site trip.

Three-phase in the shop → · BASIC modules → · Per-circuit monitoring →

More than one cabinet

Today each cabinet is its own controller, complete and reporting on its own. A single synchronized view across cabinets is what the RBgrid hub is for, and it is in development.

Read before you buy

One module, a line per party.

Start with the lines you actually charge for; the shared branches can be added once the split is being measured instead of estimated.