xdwokcn

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • in reply to: 关于ScadaServer进程内存占用率过高的问题 #9753
    xdwokcn
    Participant

    客户端长期开着2个浏览器看数据,SQL是根据文档自己开发的一个转存工具,跟主进程应该没有关系,只是单独读取dat文件。目前来看,到了4.5G左右,就不会继续增长了。

    in reply to: 关于ScadaServer进程内存占用率过高的问题 #9705
    xdwokcn
    Participant

    使用的最新版本5.8版本的,基本没有使用函数,使用函数的大概也就几百个,而且都是简单的函数,没有创建对象。目前来看,全部内存占满大概需要半个月时间,所以,目前采取的办法是通过Windows的计划任务定期重启ScadaServer和ScadaComm服务,现在运行还算正常。

    in reply to: 关于ScadaServer进程内存占用率过高的问题 #9676
    xdwokcn
    Participant

    内存8G,还好,运行一段时间以后增长就会缓慢一点。

    in reply to: 报警里的 Undefined是什么意思 #9423
    xdwokcn
    Participant

    不好意思,好久没有光顾论坛了,是这样,我的项目由于ModBus通信不稳定,经常会有部分设备短时间无法通信,但是过一会又好了,但是这是RapidScada就会报Unreliable错误,而且会大面积报,我的想法是,有没有一种方法就是设备通信有问题的时候不去报警,只是纯粹的当位置变化的时候才报警。

    in reply to: 中文交流分支开启了 #9319
    xdwokcn
    Participant

    占个沙发

    in reply to: Communicator will be stoped after Upload Configurations #9003
    xdwokcn
    Participant

    Can you reproduce this issue using the built in drivers, like Modbus Driver?

    Nearly 90% of devices are using Modbus Driver,and another is OPC UA.

    in reply to: Communicator will be stoped after Upload Configurations #9002
    xdwokcn
    Participant

    @xdwokcn Do you happen to have a record of archived data in your drivers?

    No,it only contains currenty data in drivers

    in reply to: Communicator will be stoped after Upload Configurations #8999
    xdwokcn
    Participant

    Could you check if Communicator already started successfully before you upload the project?

    Yes,the Communicator has already started before my uploading. but it has been work well for serveal days.

    Starting communicator usually cost 10~20 seconds.

    in reply to: Communicator will be stoped after Upload Configurations #8990
    xdwokcn
    Participant

    I have checked the log, I find that during I upload the configuration to the server ,the communicator cannnot connect to the ScadaServer, but the scadaServer service has been started, and the server send “abortd” to stop the communicator. When I open the Manager to start communicator maunally, the commmunicator can start success.
    So I don’t know the reason of this, it only appeared on Windows, and never appeard on Linux.

    2021-05-23 22:56:59 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:56:59 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:56:59 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:56:59 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:56:59 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:56:59 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:56:59 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:57:00 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:57:00 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:57:00 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:57:00 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:57:00 <WIN-CAC7VEJ6UUO><SYSTEM><ERR> Unable to connect to SCADA-Server. Try again.
    2021-05-23 22:57:00 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Connect to SCADA-Server “localhost”
    2021-05-23 22:58:13 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Receiving commands aborted
    2021-05-23 22:58:13 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Stop communication lines
    2021-05-23 22:58:24 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Disconnect from SCADA-Server
    2021-05-23 22:58:24 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> ScadaCommService is stopped
    ——————————————————————————–
    ——————————————————————————–
    2021-05-23 22:59:32 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> ScadaCommService 5.2.1.2 is started
    2021-05-23 22:59:32 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Load device library: KpModbus.dll
    2021-05-23 22:59:33 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Load device library: KpDLT64507.dll
    2021-05-23 22:59:33 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Load device library: KpDLT64597.dll
    2021-05-23 22:59:35 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Load device library: KpIEC104.dll
    2021-05-23 22:59:35 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Load device library: KpOpcUa.dll
    2021-05-23 22:59:35 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Connect to SCADA-Server “localhost”
    2021-05-23 22:59:37 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Start communication lines
    2021-05-23 22:59:37 <WIN-CAC7VEJ6UUO><SYSTEM><ACT> Start receiving commands

    in reply to: Communication is stopped without any infomation #8972
    xdwokcn
    Participant

    I 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.

    in reply to: Communication is stopped without any infomation #8966
    xdwokcn
    Participant

    Thank 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.1

    Today, 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

    in reply to: Communication is stopped without any infomation #8962
    xdwokcn
    Participant

    Communicate log
    Request Queue

    in reply to: Communication is stopped without any infomation #8961
    xdwokcn
    Participant

    OS 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.

    Linux establish a file named core.4370

    in reply to: Communication is stopped without any infomation #8959
    xdwokcn
    Participant

    Thank you for reply ,but I have set the communication line keep connect yet.

    in reply to: Communication is stopped without any infomation #8956
    xdwokcn
    Participant

    a

    the communicator has been stop working without any information.

    • This reply was modified 1 year ago by xdwokcn.
Viewing 15 posts - 1 through 15 (of 15 total)