Siemens 7KT1665 (grid)
The Siemens 7KT1665 is a DIN-rail mounted, three-phase SENTRON PAC1600 energy meter rated for direct measurement up to 80 A, used in industrial plants, commercial buildings, and apartment blocks. This template reads the device over Modbus RTU via RS-485, collecting total active power, cumulative grid energy, and per-phase currents on L1, L2, and L3. With these five registers visible in your ModbusCloud portal, you can track grid consumption, detect phase imbalances, and feed accurate meter data into energy reporting workflows without adding external current transformers.
- Protocol
- Modbus RTU
- Connection
- RS485
- Registers
- 5, read only
- Brand
- Siemens
- Last updated
Registers (5)
5 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | Wh | Read | |||
| currents_a | A | Read | |||
| currents_b | A | Read | |||
| currents_c | A | Read |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Monitor total active power at the grid connection point to verify consumption against contracted demand limits.
- Track cumulative grid energy over time to generate accurate monthly consumption reports per site or tenant.
- Compare L1, L2, and L3 currents to detect phase imbalances before they cause equipment overheating.
- Alert on unexpected power spikes during off-hours to identify unauthorised loads or faulty equipment.
- Verify that a newly commissioned load does not exceed the 80 A direct-measurement rating of the 7KT1665.
Installation
Set the Modbus RTU slave address and baud rate on the Siemens 7KT1665 using the front-panel menu under the communication parameters section (P5 for 80 A three-phase devices); note the address and baud rate for later.
Wire the RS-485 A and B terminals of the 7KT1665 to the corresponding RS-485 terminals on the ModbusCloud Gateway, observing polarity, and terminate the bus with a 120-ohm resistor if the meter is at either end of the RS-485 segment.
In the ModbusCloud portal, add your Gateway, then import the Siemens 7KT1665 (grid) template and enter the slave address you configured on the device.
Spot-check the power register (address 57) in the live data view: apply a known load to the metered circuit and confirm the reading changes as expected.
Things to watch for
Why do all register values read zero or max-range garbage?
The 7KT1665 uses 32-bit INT32 and UINT32 values spread across two consecutive 16-bit Modbus registers. If your gateway or polling software reads only one register per address, values will be wrong. Ensure the template is set to read 2 holding registers per data point and that big-endian (high word first) byte order is selected.
The gateway connects but no live values appear in the portal. What now?
Confirm the slave address in the portal matches the address programmed on the meter front panel. Then check baud rate and parity: the PAC1600 supports 300 to 38400 bps and defaults to a specific baud rate set during commissioning. A mismatch in either parameter causes a complete communications blackout. Also verify RS-485 polarity on A/B terminals.
Energy readings look correct but the power register fluctuates wildly. Why?
The power register (address 57) returns signed INT32 data representing instantaneous active power. Short polling intervals combined with load switching can produce rapid swings. Increase the poll interval to 5 to 10 seconds and confirm the portal is not applying an additional scaling factor, as the raw register value already reflects the device's internal scaling.
Phase current readings for L2 and L3 seem identical to L1. What is wrong?
Each phase current occupies its own 32-bit register at distinct addresses (L1 at 7, L2 at 9, L3 at 11). If all three return the same value, check that the template is polling all three addresses independently and that the RS-485 bus is not dropping responses mid-frame, which can cause the gateway to reuse the last valid value for subsequent registers.
Want to see how it works?
