```

What Is EOS Modbus Server?

EOS Modbus Server is a communication component that provides data collected or processed by EOS applications to external systems as a Modbus TCP Server.

The server accepts connections from Modbus TCP Client applications through a configured IP address and TCP port.

In response to requests sent by the Modbus TCP Client, data available within EOS can be read from the Modbus register areas.

This architecture is particularly useful in applications where the EOS system needs to be monitored by another automation or control system.

How Does It Work?

EOS Modbus Server periodically transfers data available within EOS to the data area of the Modbus Server.

Current values are stored in Holding Registers.

When a Modbus TCP Client application connects to the server, it can access data from the EOS system by reading the relevant Holding Register areas.

EOS Data

Real-time data available in EOS systems is used as the data source.

Data Refresh

Data is transferred to the Modbus data area according to the configured refresh interval.

Modbus TCP Server

EOS data is provided to external systems through the Modbus TCP Server.

Holding Register Structure

Data provided by EOS Modbus Server is stored in the Holding Register area.

For transferring analog values, a 32-bit Float value is provided using two 16-bit Modbus Holding Registers.

The lower and upper 16-bit portions of the Float value are transferred to separate register areas.

This structure allows analog process values available in EOS to be placed in register areas that can be read by Modbus TCP Client applications.

Selecting Data to Be Provided

EOS Modbus Server does not require all data available in EOS to be provided through Modbus. The data group to be provided can be determined according to the configuration.

All Data

All suitable data can be transferred to the Modbus data area.

Digital Data

Digital / Integer type data can be selected and provided.

Analog Data

Real / analog type data can be selected and provided.

Selected Data

Only the data selected by the user can be transferred to the Modbus data area.

```
```

Modbus TCP Communication

EOS Modbus Server uses TCP/IP-based Modbus TCP communication.

The IP address, TCP port and Slave ID information for the server can be configured.

Parameter Description
IP Address IP address on which the Modbus TCP Server operates
TCP Port TCP port used for Modbus TCP communication
Slave ID Slave ID configured for the Modbus Server
Timeout TCP send and receive timeout settings
```

Server Configuration

The operating parameters of EOS Modbus Server are configured through the EOS SCADA Project Settings. The IP address on which the server will operate, the port used by Modbus clients to connect, and the data update interval can be configured in the project settings.

Parameter Description Default Value
IP Address The IP address on which the EOS Modbus Server listens for client connections. IP_Address (Project Settings dependent)
MODBUS Port The TCP port used by MODBUS clients to connect to the EOS Modbus Server. Default 502
Data Type Defines the scope of EOS SCADA data provided through MODBUS. One of the options: All, Digital, Analog or Selected
Update Interval Defines the interval at which EOS SCADA data is checked by the MODBUS Server and changed values are made available through MODBUS. Default 1 second
Device ID Defines the device identifier used by MODBUS clients when communicating with the data provided by the EOS Modbus Server. Default 1

The default value for the MODBUS Port is 502. This is the standard TCP port used for MODBUS TCP communication and can be changed through the Project Settings when required.

The default Update Interval is 1 second. This interval determines how frequently the EOS SCADA data is checked by the MODBUS Server. Changes in data values become available for reading by MODBUS clients.

When the MODBUS Server is started, it begins accepting MODBUS TCP client connections on the IP address and port defined in the Project Settings.

```

Data Refresh

EOS Modbus Server transfers data available within EOS to the Modbus Server data area according to the configured refresh interval.

This ensures that the Holding Register values read by Modbus TCP Clients represent the current process values in the EOS system.

The refresh operation is performed continuously, keeping the Modbus data area up to date while the server is active.

Monitoring Modbus Requests

EOS Modbus Server can monitor requests received from Modbus TCP Client applications.

The number of incoming Modbus requests can be monitored within the EOS system. This feature can be useful for checking whether communication is active and for monitoring system operation.

Applications

  • SCADA systems
  • PLC systems
  • HMI applications
  • Energy monitoring systems
  • Industrial automation
  • Data acquisition systems
  • Supervisory control systems
  • Energy management systems
  • Industrial data integration
  • Modbus TCP Client applications

EOS Modbus Server makes it easier for real-time data available in EOS systems to be used by different systems supporting Modbus TCP.

Integration with EOS Software

EOS Modbus Server is designed to operate as an integrated component within the EOS software ecosystem.

Data available within EOS is converted by the Modbus TCP Server into Modbus register values that can be transferred to external systems.

This allows access to data collected or processed by EOS through Modbus TCP without the need to develop a separate data transfer application.

Technical Features

Feature EOS Modbus Server
Communication Modbus TCP
Operating model Server / Slave
Network TCP/IP
Data area Holding Registers
Analog value 32-bit Float
Float register usage 2 × 16-bit Registers
Data selection All / Digital / Analog / Selected
Data refresh Configurable
Request monitoring Supported

Summary

EOS Modbus Server is an integrated Modbus Server component that enables real-time industrial data available in EOS systems to be transferred to different systems through Modbus TCP.

EOS data is transferred to Holding Register areas and can be read by Modbus TCP Client applications.

All data, only digital or analog data, or user-selected data can be provided through Modbus.

This architecture enables EOS systems to be easily integrated with PLC, SCADA, HMI and other industrial applications supporting Modbus TCP.

```