Modbus data - Configuration error

In the attachment log.

openhab.log (47.0 KB)

This looks important

2019-08-18 17:48:47.937 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model 'modbus.things' has errors, therefore ignoring it: [1,38]: no viable alternative at input '�'
[1,40]: missing ']' at 'dev'
[1,44]: no viable alternative at input 'ttyUSB0'
[1,54]: no viable alternative at input 'baud'
[1,61]: no viable alternative at input '115200'
[1,69]: no viable alternative at input 'id'
[1,74]: no viable alternative at input '3'
[1,77]: no viable alternative at input 'stopBits'
[1,89]: no viable alternative at input '1'
[1,91]: no viable alternative at input '0'
[1,95]: no viable alternative at input 'parity'
[1,105]: no viable alternative at input 'none'
[1,112]: no viable alternative at input 'dataBits'
[1,123]: no viable alternative at input '8'
[1,126]: no viable alternative at input 'encoding'
[1,138]: no viable alternative at input 'rtu'
[3,71]: no viable alternative at input '�'
[3,72]: missing ']' at 'holding'
[5,40]: no viable alternative at input '�'
[5,41]: missing ']' at '8'
[5,45]: no viable alternative at input 'readValueType'
[5,62]: no viable alternative at input 'int16'
[6,38]: no viable alternative at input '�'
[6,39]: missing ']' at '10'
[6,42]: no viable alternative at input '0'
[6,46]: no viable alternative at input 'readValueType'
[6,63]: no viable alternative at input 'bit'
[7,38]: no viable alternative at input '�'
[7,39]: missing ']' at '10'
[7,42]: no viable alternative at input '1'
[7,46]: no viable alternative at input 'readValueType'
[7,63]: no viable alternative at input 'bit'
[8,38]: no viable alternative at input '�'
[8,39]: missing ']' at '10'
[8,42]: no viable alternative at input '2'
[8,46]: no viable alternative at input 'readValueType'
[8,63]: no viable alternative at input 'bit'

Seems like you need to look at your modbus.things file

I thought you had decided to use PaperUI. Perhaps there’s just an old file that needs deleting.

That’s the timeout. One query-response transaction at a time, modbus will not move on to the next until the previous one has worked or failed. If the slave does not respond, a timeout runs until the transaction is declared failed. Default timeout is 1.5S

100mS poll frequency is quite ambitious over a serial bus.

Your log contains multiple errors for both slaves. Simplify and fix one problem at a time. If you are using PaperUI, disable modbus bridge things to leave just one Serial thing and one of its pollers. Make that work.