How to Configure

Modbus Server Mode

1
Overview
Modbus protocol is common industrial protocol. When we talk
about how to communicate with Modbus serial data to Ethernet,
the Modbus gateway is good solution to solve this problem.
In Modbus gateway, there are two operation mode.

First, we called Modbus Server Mode, is most popular way to use

this gateway. SCADA send out Modbus/TCP command via gateway
to get end terminal Modbus serial device status/data.

Another one we called Modbus Client Mode. the polling way is

opposite. SCADA send out Modbus RTU/ASCII command via
gateway to get end terminal Modbus TCP device status/data.
 Topology of Modbus Server Mode
Ethernet
SCADA EKI-1222 Modbus Server Serial (RS-232/422/485)
IP 192.168.1.2
Ethernet ADAM-4019+
Modbus TCP

Data Center RS-485

IP 192.168.1.31 Modbus RTU/ASCII
Server ID = 2

SCADA (Data Center) polls data through Modbus TCP. The EKI
translates the data from TCP to RTU, and send to end device. Then
end device responses data to Data center.
Configure Modbus Server Mode(1/4)

TCP Port 502

Server ID = 2

By default, the Listen

Port for Server Mode
for Modbus/TCP is
502.
This parameter is
defined in the page
System.
Users can change it
according to the
requirement.
Configure Modbus Server Mode(2/4)

TCP Port 502

Server ID = 2

Use “Launch Browser” in the 1st.

Utility(Eth1/Eth2) or key in IP
address in the browser 192.168.1.2
to connect to device server.

1st.
Choose the COM Port of “Port
Configuration” to set up the Basic
part first, then “Save” it.
Configure Modbus Server Mode(3/4)
2 : Operation Page Setting
2nd. 2nd.
Mode: Modbus Server Mode;
Protocol: RTU (Modbus/RTU);
Server Timeout: Modbus GW
waiting time for response.

3rd. Peer for Receiving Data

<we support up to 32 peers>
Server ID : Actual ID on device
Mapping ID: Remapped ID
3rd.
4th. Save: Confirm the change

4th.
Configure Modbus Server Mode(4/4)
3. After modified the configuration, EKI need to reboot to
actually apply the new settings.

3. Click “Yes” to reboot the Device

1. Click “Tools”

2. Click “Reboot”
Direct Access Port (EKI-122x-CE v1.07 or Later)
Designated COM port to direct access port which separate each serial port into different
TCP service port, instead of combined all into Port 502.
Default:
Port1: 6000
Port2: 6001
Port3: 6002
Port4: 6003

Set ModScan connection detail to TCP service port from port 6000~6003, according to
the target COM port.
Difference between System Port and
Direct Access Port Modbus Query
ModScan

Modbus/TCP
192.168.1.4/24
502 (Control PC)

Mapped Mapped Mapped Mapped

as 1~3 as 11~13 as 21~23 as 31~33
6000 6001 6002 6003 For Modbus Server Mode,
Node 1~3 Node 1~3 Node 1~3 Node 1~3 when querying Modbus Nodes
with TCP port 502 (default
Modbus COM 1 COM 2 COM 3 COM 4 listen port for Server Mode), it
Gateway is querying the Server IDs that
Or Router were remapped on EKI.

If the TCP Port target is set to

the “Direct Access Port” of
each COM Port, the Modbus
Client is actually querying the
Server ID before mapped.
Since it is only accessing one
of the COM port at a time,
devices on other COM ports
are not accessible.

Node 1~3 Node 1~3 Node 1~3 Node 1~3

Test Tool:

Modscan/
Modsim tool
Why use Modsim and Modscan？
➢ Simulate both side works as Ethernet or COM port, and be able to send out
the Modbus data which is Modbus TCP or Modbus RTU/ASCII
➢ It’s compatible with Windows XP and 7 (Working as Administrator)

SCADA Ethernet ADAM-4019+

RS-485
Modbus RTU/ASCII

Modscan Server ID = 5
Address = 40001 Modsim
Weakness：Modsim only simulate the quantity of COM Ports up to 9
Set-up Modsim tool
If you want to simulate the end device to send out the data
with Modbus RTU/ASCII
1st. Click “File” and “New”
2nd. Click “Connection”, and select the “COM Port” (Up to 9)
3rd. Select the protocol of Modbus “RTU” or “ASCII”

1st.
3rd.

2nd.
 Send out Modbus RTU/ASCII by Modsim
Server ID, Function Code, Address and Data Length as below:

Device ID = Node of End device

Data Type of Modbus、 Address and Data Length

Slave ID=2

Modscan
 Set-up Modscan tool
• If you want to simulate the data center to send out the
polling with Modbus TCP
1st. Click “Connection” and “Connect”
2nd. To select “Remote TCP/IP Server” =>IP Address: Fill in the IP
of Modbus gateway
3rd. Service Port: 502 (Default setting of Modbus Listen Port)
4th. Click “Protocol Selections” to select the protocol of Modbus
1st.

2nd. 4th.

3rd.
Polling Modbus TCP data by Modscan

Device ID = Node of End device

Data Type of Modbus
Query Address and Length

Received Data
How to Test
Modbus Server Mode
 How to Test the Modbus Server Mode

Server ID= 2
2nd. Click “Connection” and “Connect”
3rd. To select “Remote TCP/IP Server” =>IP Address: Fill in the IP of Modbus gateway
4th. Service Port: 502 (Default setting of Modbus)
5th. Click “Protocol Selections” to select the protocol of Modbus
Address length:
Device ID = Node of end device 40001~40008
Function Code, Address and Data Length *The value must be same with end device
Function Code:
The counter for Polling data and valid data
03
 How to Test the Modbus Server
PC EKI-1222 Modbus Server
IP 192.168.1.2
ADAM-4019+
Ethernet
Modbus TCP
RS-485
Data Center
IP 192.168.1.31 Modbus RTU/ASCII
End Device
Modbus RTU/ASCII
Polling the data from Modbus gateway Server Mode success

40001
Address

Modbus Point Type

01: Coil Status =0
02: Input Status =1
03: Holding Register =4
04: Input Register =3
Reference: Modscan/modsim tool

http://www.win-tech.com/html/modbus1.htm