|
Modbus TCP bug, SpaceLYnk
|
28.09.2018, 11:47
For this case you should use scripts instead of modbus mapper. The problem is that all devices on first RTU line and TCP are polled in a single queue. Writing is blocked between reads. And if the device is offline it might time some time for timeout to occur. You can try lowering the timeout value for all TCP devices but it might now solve the issue completely if there are several offline devices at once.
|
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Modbus TCP bug, SpaceLYnk - by FatMax - 28.09.2018, 06:11
RE: Modbus TCP bug, SpaceLYnk - by admin - 28.09.2018, 06:55
RE: Modbus TCP bug, SpaceLYnk - by Erwin van der Zwart - 28.09.2018, 07:32
RE: Modbus TCP bug, SpaceLYnk - by FatMax - 28.09.2018, 08:45
RE: Modbus TCP bug, SpaceLYnk - by Erwin van der Zwart - 28.09.2018, 09:13
RE: Modbus TCP bug, SpaceLYnk - by FatMax - 28.09.2018, 09:17
RE: Modbus TCP bug, SpaceLYnk - by Daniel - 28.09.2018, 10:36
RE: Modbus TCP bug, SpaceLYnk - by FatMax - 28.09.2018, 10:43
RE: Modbus TCP bug, SpaceLYnk - by admin - 28.09.2018, 11:47
RE: Modbus TCP bug, SpaceLYnk - by FatMax - 28.09.2018, 12:11
RE: Modbus TCP bug, SpaceLYnk - by admin - 28.09.2018, 12:33
|
