06.05.2022, 06:30
Hi,
On a project we have two modbus devices connected to a LM3 Lite (latest firmware), the first one is RTU port 1 and the second one is TCP.
RTU device only allows read/write one register each second, so in the profile has the field "read_delay"=1 (and it works fine). We're reading about 60 registers from this the device.
It seems that, depending on the value of "Poll Interval", the second device (TCP) is not read..
If we set the poll interval to 120s on the RTU device, then TCP is read.
Has something been changed on last firmwares? On older ones we have not seen this behavior...
How are modbus readings/writings processed? Sequentially slave to slave despite if they are on the same port or not?
We've seen that writings to RTU device are done passed some time after they are done on KNX side (sometimes after 1 minute....). How are they done after the actual polling, on the next one?
On a project we have two modbus devices connected to a LM3 Lite (latest firmware), the first one is RTU port 1 and the second one is TCP.
RTU device only allows read/write one register each second, so in the profile has the field "read_delay"=1 (and it works fine). We're reading about 60 registers from this the device.
It seems that, depending on the value of "Poll Interval", the second device (TCP) is not read..
If we set the poll interval to 120s on the RTU device, then TCP is read.
Has something been changed on last firmwares? On older ones we have not seen this behavior...
How are modbus readings/writings processed? Sequentially slave to slave despite if they are on the same port or not?
We've seen that writings to RTU device are done passed some time after they are done on KNX side (sometimes after 1 minute....). How are they done after the actual polling, on the next one?