Communicator will be stoped after Upload Configurations

Forum Home Forums Communicating with Devices Modbus Communicator will be stoped after Upload Configurations

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #8989
    xdwokcn
    Participant

    When I finished my configuration and upload it to the server ,I find that serveral minites later, the communicator has been stopped , I must open the ScadaAdmin to restart the communicator, and after I start the conmmunicator, it works well.

    so, this problem is why the communicator automaticlly stoped after uploading the configuration to server.

    I have update the software to the latest version, and my OS is Windows Server 2016.

    #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

    #8992
    Mikhail
    Moderator

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

    If Communicator is not fully started when you upload again, there may be an issue, because it should be fully started before stop.

    May be starting takes a long time. if so, you should analyze the cause.
    Try starting and stopping Communicator manually and watch how it behaves.

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

    #9000
    manjey73
    Participant

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

    #9001
    Mikhail
    Moderator

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

    #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

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

    #9004
    Mikhail
    Moderator

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

    Good.
    You provided the Communicator log. What is in the Server log at the same moment when a problem occurs?

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.