Forum Home › Forums › Communicating with Devices › Modbus › Communication is stopped without any infomation
- This topic has 11 replies, 3 voices, and was last updated 2 years, 11 months ago by xdwokcn.
-
AuthorPosts
-
May 17, 2021 at 7:29 am #8955xdwokcnParticipant
My project connect some devices using SerialPort to Ethernet Device by Modbus Protocol, recently I find that the communication line often stopped polling data from devices and without any information until I restart communicator. The project contain s 27 lines, every line contain 10~15 serial port devices.
May 17, 2021 at 7:33 am #8956xdwokcnParticipantthe communicator has been stop working without any information.
- This reply was modified 2 years, 11 months ago by xdwokcn.
May 17, 2021 at 8:29 am #8958manjey73ParticipantTry to remove the check mark – Stay connected in the communication line settings.
May 17, 2021 at 8:32 am #8959xdwokcnParticipantThank you for reply ,but I have set the communication line keep connect yet.
May 17, 2021 at 9:36 am #8960MikhailModeratorHello,
the communicator has been stop working without any information.
What OS do you use?
All lines stopped or only one line?May 17, 2021 at 9:45 am #8961xdwokcnParticipantOS is Linux CentOS 7, RapidScada is running in docker, and it working well for a long time.Recently Nearly 60% lines(Only Serial port devices communicate by Ethernet Gateway, and OPC device is OK all the time) stopped and the log can not record any unusual information.
In this afternoon, I seek my working directroy ,and find that a file named “core.4370” established when the line stopped.
May 17, 2021 at 9:52 am #8962xdwokcnParticipant
May 18, 2021 at 1:07 pm #8964MikhailModeratorWhen some lines are stopped, do other lines continue working?
Are there any error messages in log files?
What Communicator version do you use?May 18, 2021 at 1:36 pm #8966xdwokcnParticipantThank you very much for reply my problem.
When some lines are stopped, do other lines continue working?
Yes,only part of lines stopped, and another lines is working normally.
Are there any error messages in log files?
There are nothing in log files, it looks like that the thread has been blocked.
What Communicator version do you use?
Communicator version is 5.2.1.1Today, I transfer the whole scada system from Linux to Windows, It works well ,no lines stoped. so I guess that the Linux and mono is not very suitable for .net program.
David,from China
May 19, 2021 at 12:47 pm #8967MikhailModeratorYou should try updating Rapid SCADA to the latest 5.8.3.
In Communicator 5.2.1.2 there was a fix may be related to the issue. See the historyMay 19, 2021 at 12:49 pm #8968MikhailModeratorI guess that the Linux and mono is not very suitable for .net program
We will get rid of Mono and will move to .NET5 on Linux.
May 20, 2021 at 7:11 am #8972xdwokcnParticipantI have downloaded the latest version of RapidScada, and transfer to Windows Server Environment, it works well now, I am looking forward your new system using .net5.
Thank you for your software, which has solved many problems for us.
-
AuthorPosts
- You must be logged in to reply to this topic.