Modbus and Energy meter

Using PC soft for Modbus I was able to read values.
I used profile: 9600:8:even:1:rtu, so this is good in my config.

I changed registry id to 14 (which is equal to 0E, which should give me Voltage L1):

modbus:serial.Voltage_L1.start=14

This soft read (where write is registry address, read is a value):

19:00:35:994  Write: 01 03 00 0E 00 02 A5 C8 
19:00:36:540  Read: 01 03 04 43 60 B3 33 DA 8C 
19:00:36:883  Over

and program gave me:
224,7 V
binding with same address gave:

> 2017-10-30 19:13:38.640 [ERROR] [i.modbus.io.ModbusRTUTransport] - Last request: 01 03 00 0e 00 02 a5 c8
> 2017-10-30 19:13:38.641 [ERROR] [i.modbus.io.ModbusRTUTransport] - failed to read: Error reading response (EOF)
> 2017-10-30 19:13:38.644 [ERROR] [w.m.io.ModbusSerialTransaction] - execute try 3/3 error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadMultipleRegistersRequest@19de726 (unit id 1 & transaction 3). Serial parameters: SerialParameters@385e25[portName=/dev/ttyUSB0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=even,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
> 2017-10-30 19:13:38.646 [ERROR] [w.m.io.ModbusSerialTransaction] - execute reached max tries 3, throwing last error: I/O exception - failed to read. Request: net.wimpi.modbus.msg.ReadMultipleRegistersRequest@19de726 (unit id 1 & transaction 3). Serial parameters: SerialParameters@385e25[portName=/dev/ttyUSB0,baudRate=9600,flowControlIn=none,flowControlOut=none,databits=8,stopbits=1,parity=even,encoding=rtu,echo=false,receiveTimeoutMillis=1500]
> 2017-10-30 19:14:00.187 [ERROR] [i.modbus.io.ModbusRTUTransport] - Last request: 01 03 00 0e 00 02 a5 c8

so how to understand “01 03 04 43 60 B3 33 DA 8C” (which means 224,7)
Is it a holding with float32 ?