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
#6
(28.09.2018, 09:13)Erwin van der Zwart Wrote: Hi,

The modbus error logs are not showed in the normal error log panel, you can see the modbus error log from the modbus tab and then at the bottom you have another error log button.
Press this button to see the modbus error log(s).

BR,

Erwin

Yes, I know. But there are only errors for unreachable devices (red ones), no errors upon sending object updates to “working” devices.

If I, for instance, send a 1 to the mentioned lifebit address then I’m expected to get a 0 back within 4 seconds as confirmation. If 1 device in my modbus list has connection issues then communication stops
With every device in the list. If I send a 1 to the same address then I never get that 0 back. It’s also stated in the EVLink log that no lifebit was received and that the EVLink has gone into safe mode.
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: