Energy & Power MonitoringEvery multi-function meter on one RS-485 line, logged through outages, delivered to your energy dashboard
Daisy-chain your Modbus energy meters and one gateway reads volts, amps, power factor, kW and kWh from up to 64 of them (32 on the LITE series). Every reading is time-stamped, kept through a network drop and delivered to your server or platform over 4G, Ethernet or Wi-Fi.
Step 1 of 5The gateway polls each meter in turn on the RS-485 line — Modbus RTU, one slave ID at a time.
Step 2 of 5Each reading is stamped with the gateway's clock and logged — one packet per meter when you bill per meter, or all meters in one.
Step 3 of 5The packets go to two servers at once: MQTT to the energy dashboard, HTTP to the ERP — each with its own packet format.
Step 4 of 5The motor meter's power factor falls below 0.85. An edge trigger fires once on the crossing and texts the maintenance phone from the gateway's own SIM.
Step 5 of 5If the network drops, readings keep logging. When it returns they go out oldest first, with their original time stamps — the dashboard has no gap.
Field dataTo your serverSMS from the gatewayCommand / write
02
What connects to the gateway
EquipmentHow it connectsWhat the gateway reads
Multi-function energy meterRS-485 · Modbus RTUV, I, PF, kW, kVA, kWh, frequency and harmonics — whatever the meter's register map publishes
CT-based motor or feeder meterRS-485 · Modbus RTUCurrent per phase, power, power factor; the CTs wire to the meter, the meter to the gateway
Modbus TCP power meterEthernet (WT460M, WT600M)The same parameters, polled over the plant LAN on the same port as the uplink
Meter with a pulse output onlyPulse into a gateway inputkWh by pulse count and the present rate — see the pulse & run-hour walkthrough
EB / DG changeover contactDigital inputWhich source is feeding the panel, logged with every reading
03
What the gateway does here
Modbus masterReads any meter with a Modbus register mapThe meter's map is loaded into the gateway's Modbus database, with each register named the way you want it to arrive: kWh, PF_R, I_Y. Up to 3,000 registers on PRO and MAX, 1,800 on LITE.
Event packingOne packet per meter — or all of them in oneCombine every meter into one packet, or send one per slave ID. Per-meter packets carry the slave ID, which is what tenant and per-feeder billing need.
Store & forwardNothing lost in a network dropReadings stay in the gateway's flash log — up to 17,500 per server — and go out oldest first, with their own time stamps, when the link is back.
Two serversDashboard and ERP from the same metersOn PRO and MAX, the same readings go to two servers at once, each with its own protocol (TCP, HTTP or MQTT) and its own format (JSON or CSV).
Edge triggerSet-point alerts with no server involvedA rule on any register — power factor, kW, voltage, current — fires once when the value crosses your limit: an SMS from the gateway's SIM, or the relay.
Time stampsReadings your platform can line upThe clock is set from NTP, HTTP or the mobile network; time stamps go out as standard, ISO 8601 or Unix time.
The meter is the certified instrumentThe gateway reports what the meter's registers hold. Accuracy class and billing approval belong to the meter, not to the gateway.
Every make lays out its registers differentlyTell us the meter make and model and we load and check its register map before the gateway ships — word order and scaling included.
A poll cycle takes timeReading many meters, and many registers from each, on one RS-485 line is not instant. We size the polling and log intervals with you rather than promise a number.
Wiring decides reliabilityRS-485 wants a daisy chain, terminated at both ends. A star or a stub is the commonest reason one meter goes quiet.
06
Questions
How many energy meters can one gateway read?
Up to 64 on the PRO and MAX series and up to 32 on the LITE series, on one RS-485 line. The WT460M and WT600M can poll Modbus TCP meters on the LAN as well, within the same count. The register budget is 3,000 words on PRO and MAX and 1,800 on LITE.
Which energy meter brands are supported?
Any meter that speaks Modbus RTU — or Modbus TCP on the WT460M and WT600M — and publishes its register map. The map is loaded into the gateway's Modbus database during configuration. Tell us the make and model and we will confirm before you order.
Can each tenant be billed from its own meter?
Yes. With event packing set to one packet per slave ID, every meter's readings travel as their own record with the slave ID in it, so your billing system can split them without guessing.
What happens to the readings if the internet drops?
They are kept in the gateway's flash log — up to 17,500 records per server — and sent oldest first, with their original time stamps, once the link returns.
Can it send to our dashboard and our ERP at the same time?
On the PRO and MAX series, yes: two servers at once, each with its own protocol (TCP, HTTP or MQTT) and its own packet format. The LITE series sends to one server.
Can it alert us when the power factor drops?
Yes, on the PRO and MAX series. An edge trigger on the power-factor register fires when the value crosses your set point and can send an SMS (on the 4G models) or switch the relay. It fires once on the crossing, not again and again while the value stays low.
