hi,
I am running in to same issue with the modbus binding related to the underlying serial jar.
Using the below link ot read out data from my inverter
2021-04-05 12:57:54.637 [DEBUG] [rt.modbus.internal.ModbusManagerImpl] - Execution of scheduled (10000ms) poll task BasicPollTask@1cf7a5f9[request=ModbusReadRequestBlueprint@12305817[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=32002,length=1,maxTries=3],endpoint=ModbusSerialSlaveEndpoint@1c3a740c[portName=/dev/ttyUSB0],resultCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@478c573f,failureCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@478c573f] finished at 1617620274637. Was started at millis: 1617620274357 (=duration of 280 millis)
2021-04-05 12:57:54.664 [DEBUG] [rt.modbus.internal.ModbusManagerImpl] - Executing scheduled (10000ms) poll task BasicPollTask@66c98c8d[request=ModbusReadRequestBlueprint@572b709b[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=32114,length=2,maxTries=3],endpoint=ModbusSerialSlaveEndpoint@1c3a740c[portName=/dev/ttyUSB0],resultCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@6abf0bb5,failureCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@6abf0bb5]. Current millis: 1617620274664
2021-04-05 12:57:54.749 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@6baf0db1[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=32008,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 473c51d8-07f7-438c-a4bd-a710851bdeee]
2021-04-05 12:57:55.196 [DEBUG] [rt.modbus.internal.ModbusManagerImpl] - Executing scheduled (10000ms) poll task BasicPollTask@2ad31c77[request=ModbusReadRequestBlueprint@2414e75d[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=32016,length=8,maxTries=3],endpoint=ModbusSerialSlaveEndpoint@1c3a740c[portName=/dev/ttyUSB0],resultCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@21b57a,failureCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@21b57a]. Current millis: 1617620275196
2021-04-05 12:57:57.427 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: undefined
2021-04-05 12:57:58.979 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: undefined
2021-04-05 12:57:59.492 [DEBUG] [rt.modbus.internal.ModbusManagerImpl] - Executing scheduled (10000ms) poll task BasicPollTask@37751fa1[request=ModbusReadRequestBlueprint@39b2f73f[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=32064,length=31,maxTries=3],endpoint=ModbusSerialSlaveEndpoint@1c3a740c[portName=/dev/ttyUSB0],resultCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@263fad78,failureCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@263fad78]. Current millis: 1617620279492
2021-04-05 12:58:04.261 [DEBUG] [rt.modbus.internal.ModbusManagerImpl] - Executing scheduled (10000ms) poll task BasicPollTask@31c0a566[request=ModbusReadRequestBlueprint@799dab92[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=32106,length=2,maxTries=3],endpoint=ModbusSerialSlaveEndpoint@1c3a740c[portName=/dev/ttyUSB0],resultCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@4678b36d,failureCallback=org.openhab.binding.modbus.handler.ModbusPollerThingHandler$ReadCallbackDelegator@4678b36d]. Current millis: 1617620284261
The binding reads out continuously, but stops after ‘Try 1 out of 3 failed when executing request’
Is there a solution on the horizon ? Or is it better to go back to OH2?
I am running a binding depending on openhab-transport-serial, but it runs flawlessly .
So i guess it mus be related the underlying serial library that the modbus binding is using.