inSCADA
EN
ENTRVersion 2022
EN
ENTRVersion 2022
  • 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 TCP Server

PreviousModbus RTU Over TCPNextModbus RTU Slave Over TCP

Last updated 5 years ago

Modbus TCP Server is a protocol used by the Master/Client that responds to queries received by the device. The ability to use this protocol in the inSCADA side provides a great deal of flexibility. inSCADA now gets a similar role as devices with the help of the protocol.

As shown in Figure 1, inSCADA can now share data with other devices on the network using this protocol.

Let's remember the Value Expression property of inSCADA. With the Modbus TCP Server protocol, you can make a simulator of any device in inSCADA using the value expression.

You do not need to create virtual/internal variables in the inSCADA platform as you would do in any other SCADA software. If this is the case, you simply need to create a device using Modbus TCP Server protocol. It also has a much more powerful structure to hold data in memory in the inSCADA platform. See getGlobalObject and setGlobalObject.

Figure 1 : Modbus TCP Server