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 TCP

PreviousMODBUSNextModbus UDP

Last updated 5 years ago

Modbus TCP enables communication with devices with Modbus TCP Server protocol from the inSCADA platform.

To communicate with a device with Modbus TCP Server protocol, we need know following definitions:

  • IP Address,

  • Slave Id/Station Number,

  • Data blocks start and end addresses,

  • Data type of variables within data blocks.

Now let's examine how the Modbus TCP protocol is configured in the inSCADA platform.

Step 1. Create a Connection.

To connect to a device, we must first create a connection.

As shown in Figure 2, the IP address of the device we want to connect to is: 0.0.0.0 Port: 3501. We create a connection based on this information.

Step 2. Create the device connected to the connection.

Now let's create a device to connect to.

As shown in Figure 3, we create a device connected to the connection we created in the previous step. We choose protocol as "Modbus TCP", station address: 1. We set the scanning time to 1000 ms.

Step 3. Create data blocks to be read/written from/to the device.

In this step, we will now define the data blocks that will be read from the device. Data blocks in MODBUS protocol can be maximum 255 bytes/127 Word/63 Double Word. MODBUS protocol has grouped data blocks into 4 different types. They are;

  • Holding Registers,

  • Input Registers,

  • Digital Inputs,

  • Coils,

Holding Registers

Input Registers

Digital Inputs

Coils

As shown in Figure 4, we create a data block of the Holding Register type connected to the device we created in the previous step. We define with the starting address as 1000 and 20 Words.

After completing the steps here, we can now communicate with the device. You need to have information about the configuration settings you edited here, the device you want to communicate with, and the data blocks you want to read/write from.

To begin the communication, you can go to the Control Panel and start the corresponding Connection. If there are no incompatibilities, your connection will appear as Connected on the Control Panel.

Last Step. Create a variable and read/write data

After the communication is established, we can now create our variables, read and write data from the device. To do this, we need to create a variable from the Development-> Variables menu.

As shown in Figure 5, we create a variable that depends on our data block. Now we can go back to our Control Panel, update our connection. and see the variable value.

Holding Registers refers to the writable and readable word memory region. For more information, please visit .

Input Registers refers only to the readable word memory region. For more information, please visit .

Digital Inputs sadece okunabilir bit bellek bölgesini ifade eder. For more information, please visit .

Coils refer to readable and writable bit memory region. For more information, please visit .

modbus.org
modbus.org
modbus.org
modbus.org
Figure 1 : Modbus TCP
Figure 2 : Connection
Figure 3 : Device
Figure 4 : Frame
Figure 5 : Variables
Figure 6 : Modbus TCP Test On Control Panel