TCP Server Connection Issue

Forum Home Forums Runtime Bugs Communicator Bugs TCP Server Connection Issue

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #14662
    ibrahim eren
    Participant

    Hello, I am setting up SCADA as a TCP server and my 4G modem as a TCP client. There is a Modbus RTU slave behind my 4G modem, and everything works correctly. However, sometimes even if the SCADA side drops the socket connection, it does not inform the 4G modem that the connection has been terminated. As a result, the modem does not terminate the socket connection, causing a communication breakdown. The modem appears to have a TCP connection, but data cannot be exchanged. How can we solve this issue?

    #14667
    Mikhail
    Moderator

    Hello,

    In TCP communication, a connection brakes silently sometimes. If a client cannot poll a server, it must reconnect if there is no reply or connection is idle for a period.

    • This reply was modified 1 year ago by Mikhail.
    #14679
    zzz
    Participant

    However, sometimes even if the SCADA side drops the socket connection, it does not inform the 4G modem that the connection has been terminated.

    If the 4G gateway client lost connection, the server has no way to notify this client. The client must detect this itself by timeout or communication attempts. Maybe dig into the settings of this 4G modem or 4G data gateway.

    #14685
    Mikhail
    Moderator

    As I remember Moxa NPort has such settings, for example.

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