MGate 5105-MB-EIP Series User Manual
For master mode, you must identify which Modbus requests need to be sent to Modbus server/slave devices
through a serial interface. The data will be exchanged between server/slave devices and the MGate
gateway’s internal memory. To do this, manually add all Modbus commands that will handle the data
exchange.
The Add, Modify, and Remove buttons support the Modbus command arrangement. When you click on the
Add and Modify buttons, the following dialog box will be displayed.
Change the Modbus command parameters to finish the configuration. You will need to configure each
Modbus command through this dialog box.
Enter a name to help to identify the command, such as the location, function, etc.
Slave ID
The Modbus slave ID that this server/slave module will accept.
0: Broadcasting
1–255: Device specific
Function code
When a message is sent from a Client to a Server device, the function code field
tells the server what kind of action to perform.
We support the following function codes so far:
01: Read coils
02: Read discrete inputs
03: Read holding registers
04: Read input register
05: Write single coil
06: Write single register
15: Write multiple coils
16: Write multiple registers
23: Read/Write multiple registers
Trigger
Disable: The command is never sent
Cyclic: The command is sent cyclically at the interval specified in the Poll
Interval parameter
Data change: The data area is polled for changes at the time interval defined by
Poll Interval. A command is issued when a change in data is detected.
Poll interval
Polling intervals are in milliseconds. Since the module sends all requests in turns,
the actual polling interval also depends on the number of requests in the queue
and their parameters. The range is from 500 to 1,200,000 ms.