Values don't match the analyzer display: current 1000x off, power factor random

[ProcessPilot]

We connected our first three energy analyzers and data is coming in, but the numbers don't match what I see on the analyzer screens in the panel. On one analyzer the phase currents are about 1000 times too high. On another, voltage looks fine but power factor jumps around between strange values like 16000 and 0. The third one looks correct.
All three are the same brand but different models. Where do I start looking?

[Technical Support]

If data is arriving at all, communication is working. What you're seeing is almost always about how the registers are interpreted: address, data type, scaling or unit. Work through one analyzer and one value at a time.
1. Use the analyzer display as the reference
Pick a moment when the load is stable and write down the values from the analyzer screen: L1/L2/L3 current, voltage, active power, power factor. Compare each one with the value in the software.
2. Values off by a factor (10, 100, 1000)
- Unit: many analyzers report current in mA, power in W instead of kW, or energy in Wh instead of kWh.
- Scaling factor: some models send integers that must be divided by 10, 100 or 1000. The factor is listed in the device's register map.
- CT/VT ratio: some analyzers report secondary values and expect the CT ratio to be applied by the reader, others report primary values. Check which one your model does, and check that the CT ratio entered on the analyzer itself is correct.
3. Values that look random (like 16000 and 0)
This usually means the data type or register order is wrong:
- A 32-bit value (or a float) read as a single 16-bit register gives jumping or meaningless numbers.
- 32-bit values are spread over two registers, and the word order differs between manufacturers. If the value looks wrong but changes with the load, try swapping the word order.
- Off-by-one addresses: some register maps start counting at 0, others at 1. If you're reading the neighboring register, you get a "valid looking" but wrong value.
4. Different models, different maps
Even within one brand, register maps often differ between models. Don't copy a configuration from one model to another without checking the map for the second model.
5. Confirm, then copy
Once all values of one analyzer match its display, use that configuration as the template for other analyzers of exactly the same model.
Background on Modbus registers and data types:
- https://greensoft.ai/blog/modbus-tcp...communication/
- https://greensoft.ai/blog/modbus-rtu...communication/
If a value still doesn't match after these checks, send us the analyzer model, the register map page you're using and a photo of the analyzer display together with the value in the software.