I'm a little confused because the XMT and RCV packets you show seem to be Modbus/TCP packets, but I believe the meter supports only Modbus RTU. Are you using a Modbus/TCP to Modbus RTU converter as well?
Regardless, your XMT packet shows you are requesting 4 holding registers starting at register address 5055. The RCV packet you're getting back is an exception response, code 02 ILLEGAL DATA ADDRESS. This means that the registers you're requesting do not exist on the device.
Looking at the device's Modbus table (
https://hager.com/intl-en/products/...le/190724_MODBUS_TABLE_FOR_ENERGY_METERS.XLS/), comparing the Address DEC with Address HEX columns, it looks like you need to request starting at register address 45056, not 5055 (this document seems to use 0-based register addressing since B000 hex is equal to 45056). This document is especially confusing because one would assume that 45056 would be Modbus reference notation indicating Holding Register 5056 (which would be register address 5055 in the packet), but it is not. The 45056 is a 0-based register address.
For additional background, details on the different Modbus register numbering schemes can be found in my post here:
This topic comes up quite often here, so I thought I'd create a new thread that attempts to explain the different numbering schemes used by Modbus vendors and how to recognize each in the documentation. It is important to note that different Modbus vendors use different notation for documenting...
control.com
I'm not sure what method your master/client uses, but I would guess you entered 45056 in your client to get the XMT packet you show there, so you may need to enter 445057 in order for your master/client to actually request register address 45056.