inSCADA
EN
EN
  • Introduction
  • Getting started
  • User Interface
    • Home
    • Development
      • Projects
      • Connections
      • Devices
      • Animations
        • Get
        • Color
        • Rotate
        • Move
        • Opacity
        • Bar
        • Click
        • Tooltip
      • Alarm Groups
      • Alarms
      • Scripts
      • Expressions
      • Variables
      • Reports
      • Processes
      • Mail
      • Import/Export
    • Wizards
      • Gas Metering
      • HPP Unit
      • Device Library
    • Visiualisation
    • Processes
    • Control Panel
    • Project Map
    • Variable History
    • Alarm History
    • Alarm Monitor
    • Trend Graphics
    • Reports
    • Logs
    • Auth Logs
    • Jobs
    • Users
    • Help
    • About
    • License
  • Mimic Design
  • Communication Protocols
    • MODBUS
      • Modbus TCP
      • Modbus UDP
      • Modbus RTU Over TCP
      • Modbus TCP Server
      • Modbus RTU Slave Over TCP
    • DNP3
      • DNP3 Master
      • DNP3 Outstation
    • PROFINET
    • IEC-104
    • SNMP
    • OPC
      • OPC UA Client
  • Programing
    • APIs
      • Variable Functions
      • Connection Functions
      • Project Functions
      • Alarm Functions
      • Script Functions
      • In-Memory DB Functions
      • System Functions
      • User Functions
      • Date-Time Functions
      • String Functions
      • Notification Functions
      • Confirmation Functions
      • Database Functions
      • Other Functions
  • Database
  • Usefull Features
  • Update Logs
  • Architectures and Applications
  • Development Roadmap
  • Migration to inSCADA
  • Licensing Policies
  • FAQ
  • Screenshots
  • Auxiliary Tools
  • Installations
    • Requirements
    • Installation on Linux
Powered by GitBook
On this page
  1. Communication Protocols
  2. MODBUS

Modbus RTU Slave Over TCP

PreviousModbus TCP ServerNextDNP3

Last updated 5 years ago

Modbus RTU Slave Over TCP is implemented in a similar way to the Modbus TCP server. It is important restriction that the Modbus RTU protocol is developed for the serial link layer, allowing a single Master query. However, the fact that the methods used in the long-established old systems are supported in the inSCADA platform facilitates migration to the inSCADA platform

As shown in Figure 1, an HMI panel with serial port can act as a master and communicate with the inSCADA platform. The terminal server provides an Ethernet-to-serial conversion and a transparent transition in the link layer. The implementation of Modbus RTU Slave Over TCP is the same as the configuration steps followed in the Modbus TCP protocol. Simply select "Modbus RTU Slave Over TCP" as the protocol. See

Modbus TCP.
Figure 1 : Modbus RTU Slave Over TCP