Error details: net.wimpi.modbus.ModbusIOException I/O exception: IOException CRC Error in received frame

Hi
I just managed to upgrade the modbus binding from ver.1 to ver.2.
I use the modbus binding to read/control Villavent/Systemair VR 400 DC.
I do get information and I can change parameter so everything works fine.
The only this is when I check the logs I see error/warning described below.
It’s something that I can do to get rid of the error?

16:43:43.639 [WARN ] [ort.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@1774abc[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=100,length=1,maxTries=3]). Will try again soon. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: IOException CRC Error in received frame: 0 bytes:  [operation ID cb0f871c-e6cd-48a8-b2d5-e6ab2b5305f8]
16:43:44.624 [WARN ] [ort.modbus.internal.ModbusManagerImpl] - Try 2 out of 3 failed when executing request (ModbusReadRequestBlueprint@1774abc[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=100,length=1,maxTries=3]). Will try again soon. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: IOException CRC Error in received frame: 5 bytes: 00 03 02 00 02  [operation ID cb0f871c-e6cd-48a8-b2d5-e6ab2b5305f8]
16:43:45.691 [ERROR] [ort.modbus.internal.ModbusManagerImpl] - Last try 3 failed when executing request (ModbusReadRequestBlueprint@1774abc[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=100,length=1,maxTries=3]). Aborting. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: IOException CRC Error in received frame: 0 bytes:  [operation ID cb0f871c-e6cd-48a8-b2d5-e6ab2b5305f8]
16:43:46.000 [DEBUG] [dbus.handler.ModbusPollerThingHandler] - Thing modbus:poller:localSerial:fan received response PollResult(failure=AsyncModbusReadResult(request = ModbusReadRequestBlueprint@1774abc[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=100,length=1,maxTries=3], error = ModbusSlaveIOException(cause=ModbusIOException, EOF=false, message='I/O exception: IOException CRC Error in received frame: 0 bytes: ', cause2=null)))

Things

Bridge modbus:serial:localSerial [port="/dev/ttyUSB0", id=1, baud=9600, stopBits="1", parity="even", dataBits=8, encoding="rtu"]
{  
	Bridge poller fan [ start=100, length=1, refresh=20000, type="holding" ] {
        Thing data VV_FanSpeed [ readStart="100", readValueType="int16", writeStart="100", writeValueType="int16", writeType="holding"]
    }
	Bridge poller temp [ start=206, length=12, refresh=60000, type="holding" ] {
        Thing data VV_TempLevel [ readStart="206", readValueType="int16", writeStart="206", writeValueType="int16", writeType="holding"]
	    Thing data VV_TempSetpoint [ readStart="207", readValueType="int16"]
	    Thing data VV_TempLVL1 [ readStart="208", readValueType="int16"]
        Thing data VV_TempLVL2 [ readStart="209", readValueType="int16"]
	    Thing data VV_TempLVL3 [ readStart="210", readValueType="int16"]
	    Thing data VV_TempLVL4 [ readStart="211", readValueType="int16"]
        Thing data VV_TempLVL5 [ readStart="212", readValueType="int16"]
        Thing data VV_TempSupplyAir [ readStart="213", readValueType="int16"]
        Thing data VV_TempExtractAir [ readStart="214", readValueType="int16"]
        Thing data VV_TempExhaustAir [ readStart="215", readValueType="int16"]
        Thing data VV_ProtectionSensor [ readStart="216", readValueType="int16"]
        Thing data VV_TempOutdoor [ readStart="217", readValueType="int16"]
    }  
}

How frequently does this happen? Do you need to do anything to get over it?

On the face of it, you’ve got bad data on your serial line. It’s not likely to be transient interference, because it sustains over time with the retries.
I would not rule out poor termination or non-twisted pair cabling etc. How long is your cable run?

Latest versions of Modbus v2 binding have some fixes for obscure timing issues and improved reporting, can you identify exactly which version you are using?