TCP Client Modbus RTU

Forum Home Forums Understanding the Software TCP Client Modbus RTU

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #10605
    victorlam
    Participant

    Under Administrator, there is settings on Main Parameter for Communication channel. There are many combination behind. I can see TCP client, TCP server, .. etc. For example, after TCP client, there is Master behaviour and Individual Comm mode.

    May I know how the different combination works here? Or I need to remember that TCP client, must be Master and Individual.
    Combination is as follows:-
    TCP Client – Master – Individual
    TCP Client – Slave – Shared
    TCP Client – Slave – Individual
    TCP Client – Master – Shared
    TCP Server – Master- Individual
    TCP Server – Slave – Shared
    TCP Server – Slave – Individual
    TCP Server – Master – Shared

    Or only one combination works only under Administrator mode.

    #10607
    manjey73
    Participant

    TCP Server or Client depends on who initiates the connection. For example, a Moxa server, and a Scada Client is a Scada initiator of connecting to Moxa with a real IP address in an open network or in a VPN network. If the Scada Server is a Moxa Client, then the initiator of the connection is Moxa and it accesses the Scada server at the real IP address.
    Master/Slave everything is as usual in the Modbus protocol, for example. Scada can be in slave mode if you use the ModbusSlave driver.
    Individually or in Shared, this is a way to specify an IP address, it is either taken from the specified settings or from the base of the device – the Call Sign

    • This reply was modified 3 years, 1 month ago by manjey73.
    #10610
    Mikhail
    Moderator

    To reduce the list of combinations, describe what result do you need.

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