This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

Modbus TCP bug, SpaceLYnk
#4
The devices are EVLinks from Schneider. All traffic looks normal on Spacelynk and no errors in logs. However, when one EVLink drops out of the network then errors occur on all EVLinks in the network. These are errors in the EVLink logs. We write to a lifebit object on the EVLinks every 8 seconds and if this object is not received then the EVLink goes into safe mode. When 1 or more Evlinks is unreachable then the result is that no EVLink in the network get the Lifebit object from the Spacelynk for some reason (to be clear, all objects behave like this then, we just noticed first on lifebit). This has no effect on the RTU devices, only TCP/IP.

I don’t have access to any EvLinks at the moment, so can’t provide the logs at this time.
Reply


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 FatMax - 28.09.2018, 08:45
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

Forum Jump: